[
https://issues.apache.org/jira/browse/HADOOP-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907529#comment-15907529
]
Elek, Marton commented on HADOOP-14163:
---------------------------------------
I created a proposed version of the hadoop.apache.org site:
1. Instead of the patch I packaged all the contents as the whole content under
https://svn.apache.org/repos/asf/hadoop/common/site/main/author could be
replaced with the content of the hadoop-site.tar.gz.
2. hadoop-site-rendered.tar.gz contains the rendered html files.
3. I used hugo site generator (https://gohugo.io). It's not as popular as for
example jekyll, but it requires only one single binary for rendering. Jekyll
needs installed ruby environment, and the right version of gems.
4. The theme is just plain bootstrap.
5. The content just converted (with pandoc) from html to markdown. Except
http://hadoop.apache.org/version_control.html, which seems to be outdated so I
updated to use the git repository urls.
6. I uploaded a preview version to http://hadoop.anzix.net, to make it easier
to review. It will be removed later.
7. The big advantages of this structure that it's much more easier to add new
releases automatically/with scripts. For a new scripts just a new file should
be created (see this one as an example:
https://raw.githubusercontent.com/elek/hadoop-site-proposal/master/content/release/2.7.3.md).
With the hugo command the new site will be generated under the public
directory.
> 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-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: [email protected]
For additional commands, e-mail: [email protected]
