[
https://issues.apache.org/jira/browse/CONNECTORS-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17796715#comment-17796715
]
Piergiorgio Lucidi commented on CONNECTORS-1495:
------------------------------------------------
Unfortunately our website is broken now, I'm so sorry for that.
[~kwri...@metacarta.com] I think that currently I need your help to republish
our website.
What we could do is to generate all the content in the old way and publishing
in the new GitHub project until the Pelican procedure will work on staging.
> 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
>
> Attachments: ManifoldCF-FluidoSkin.png, PDF-Rendition-1.png,
> PDF-Rendition-2.png, Website - status - 20180510-2.png, Website - status -
> 20180510.png
>
> 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
(v8.20.10#820010)
