manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piergiorgio Lucidi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONNECTORS-1495) Brand new website
Date Thu, 01 Mar 2018 08:58:00 GMT

    [ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381695#comment-16381695
] 

Piergiorgio Lucidi commented on CONNECTORS-1495:
------------------------------------------------

Hi [~kwright@metacarta.com],

WHOOOPS :D

I have removed the wrong branch but I'm wondering why we have two separated folders for the
trunk of our site:
 * manifoldcf/site/trunk
 * manifoldcf/trunk/site

Taking a look at the README.txt file it seems not the same for both the folders, if you see
the following it seems old to me:

[https://svn.apache.org/repos/asf/manifoldcf/site/trunk/README.txt]

I want to be sure to create the branch with the right content, I have typically worked on
the manifoldcf/trunk/site folder.

 

> Brand new website
> -----------------
>
>                 Key: CONNECTORS-1495
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1495
>             Project: ManifoldCF
>          Issue Type: New Feature
>          Components: Site
>    Affects Versions: ManifoldCF 2.9.1
>            Reporter: Piergiorgio Lucidi
>            Assignee: Piergiorgio Lucidi
>            Priority: Major
>             Fix For: ManifoldCF next
>
>   Original Estimate: 480h
>  Remaining Estimate: 480h
>
> The community decided to work on a brand new website:
> [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CCAHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E]
> The proposed technology is Jekyll but we have also to decide the website template to
use.
> [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/] template.
> [~molgun] proposed this approach:
>  # Find a modern new static site generator like Jekyll [1]
>  # Create a template
>  # Start to use it in a specific path like [https://manifoldcf.apache.org/*new*]
>  # Migrate our Forrest xml's to Markdown (we can automate this somehow)
>  # Start to serve our new site on root path
> [1] [https://jekyllrb.com/docs/home/]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message