[
https://issues.apache.org/jira/browse/HADOOP-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244662#comment-16244662
]
Elek, Marton commented on HADOOP-14163:
---------------------------------------
about a) and b)
Until know we used mvn site for generating the docs and apache forrest to
generate the site. This patch just replaces the forrest part with hugo. Hugo is
a static website generator, mvn site is for generating project documentation.
For mvn site the reflow theme is almost the only one which could be used to do
some modern reponsive site, with hugo there are hundred of more powerful
themes. And the content usage of hugo is more natural. The final goal was (as I
wrote on hadoop mailing list at 03/24/2017 where I also proposed to use hugo)
to simplify the release process. With hugo it's very simple and easy to
automatize thx to the flexible content handling and dynamic menu generation. I
can imagine that it could be done with mvn site, but not in such an easy way.
My suggestion was to use the mvn site based documentation as before (but agree,
that long term we can switch to a reflow based better skin there as well)
c.) I think only the docs/downloads are using external links which are fine.
All the other links could be adjusted by the baseurl parameter of hugo (-b)
{code}
grep -r "https://hadoop"; .
./config.toml:baseurl = "https://hadoop.apache.org";
./layouts/partials/navbar.html: <li><a
href="https://hadoop.apache.org/docs/r{{.BaseFileName}}/";>{{.BaseFileName}}</a></li>
./layouts/release/single.html: <p><a
href="https://hadoop.apache.org/docs/r{{.BaseFileName }}" class="btn
btn-primary">Documentation</a></p>
{code}
> 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-14163.004.patch, HADOOP-14163.005.patch,
> HADOOP-14163.006.patch, HADOOP-14163.007.patch, HADOOP-14163.008.tar.gz,
> 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]
