[
https://issues.apache.org/jira/browse/HADOOP-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518730#comment-16518730
]
Vinod Kumar Vavilapalli commented on HADOOP-14163:
--------------------------------------------------
Got pinged about this offline.
Thanks for keeping at it, [~elek]!
I think there are two road-blocks here
(1) Is the mechanism using which the website is built good enough - mvn-site /
hugo etc?
(2) Is the new website good enough?
For (1), I just think we need more committer attention and get feedback rapidly
on this Jira and get it in.
For (2), how about we do it in a different way in the interest of progress?
- We create a hadoop.apache.org/new-site/ where this new site goes.
- We then modify the existing web-site to say that there is a new
site/experience that folks can click on a link and navigate to
- As this new website matures and gets feedback & fixes, we finally pull the
plug at a later point of time when we think we are good to go.
Thoughts?
> 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
> Priority: Major
> 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-14163.009.patch, HADOOP-14163.009.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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
