[
https://issues.apache.org/jira/browse/HADOOP-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980786#comment-15980786
]
Akira Ajisaka commented on HADOOP-14163:
----------------------------------------
Thanks [~elek] for the update.
bq. But do we need it for the merge?
Now we don't need it, but I'm thinking it would be better to support relative
path because it makes testing easier.
One comment: Would you update the links for each project (such as Cassandra,
HBase, etc.) in
https://github.com/elek/hadoop-site-proposal/blob/master/content/related.md?
Now I'm thinking how to integrate the work. I'd like to
1. Create a doc branch and push the hadoop-site-proposal directory into the
branch.
2. Create a script (such as .travis.yml) to deploy web pages and push them into
gh-pages branch, and add the script in the doc branch.
That way when the doc branch is updated, the web pages will be updated
automatically. What do you think?
> 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: [email protected]
For additional commands, e-mail: [email protected]
