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

Elek, Marton commented on HADOOP-14163:
---------------------------------------

For me everything is acceptable. I would like to get it merged anyway... 
Separated repo could be more cleaner.

But I think it's important that we are speaking about two repositories. One for 
the source of the site and one for the rendered site. Spark uses git 
(apache/spark-website) as the source but don't know where is the generated site 
(was here 1 year ago: https://svn.apache.org/repos/asf/spark)

IMHO for hadoop both part should be migrated to git (to the same or different 
repositories) to avoid using different SCM just for releasing...

BTW, I refreshed the proposed branch at 
https://github.com/elek/hadoop-site-proposal with 2.8.1, 3.0.0-alpha4 and the 
new PMC/commiters. So it's ready to move to somewhere...

> Refactor existing hadoop site to use more usable static website generator
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-14163
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14163
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: site
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>         Attachments: HADOOP-14163-001.zip, HADOOP-14163-002.zip, 
> HADOOP-14163-003.zip, hadoop-site.tar.gz, hadop-site-rendered.tar.gz
>
>
> From the dev mailing list:
> "Publishing can be attacked via a mix of scripting and revamping the darned 
> website. Forrest is pretty bad compared to the newer static site generators 
> out there (e.g. need to write XML instead of markdown, it's hard to review a 
> staging site because of all the absolute links, hard to customize, did I 
> mention XML?), and the look and feel of the site is from the 00s. We don't 
> actually have that much site content, so it should be possible to migrate to 
> a new system."
> This issue is find a solution to migrate the old site to a new modern static 
> site generator using a more contemprary theme.
> Goals: 
>  * existing links should work (or at least redirected)
>  * It should be easy to add more content required by a release automatically 
> (most probably with creating separated markdown files)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to