[
https://issues.apache.org/jira/browse/HADOOP-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981335#comment-15981335
]
Elek, Marton commented on HADOOP-14163:
---------------------------------------
Yes, we are speaking about two branches:
* One contains the source of the hadoop site
* One contains the rendered hadoop site and the generated javadocs
Currently both are in SVN
(https://svn.apache.org/repos/asf/hadoop/common/site/main/author and
https://svn.apache.org/repos/asf/hadoop/common/site/main/publish)
There are two options:
1. Move only the author part to a dedicated branch, and create a jenkins job to
generate the site and commit it to the svn
2. Move both to git. They could be on the same branch or in two different
branch. But an automatic site generation jenkins job could also be useful in
this case as well.
PS: I fixed the links of the related projects:
https://github.com/elek/hadoop-site-proposal/archive/master.zip
> 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-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.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
