[ 
https://issues.apache.org/jira/browse/HADOOP-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940042#comment-15940042
 ] 

Elek, Marton commented on HADOOP-14163:
---------------------------------------

[~andrew.wang] thanks the comments, I addressed all of them

* Home removed
* bylaws, and community menus has been moved. ASF is no longer a menu but I 
leave it as a link to the ASF home page. (Also added the logo to the footer). 
Privacy policy is moved to the footer
* Pagination on separated archive page has been added.
* Documentation link has been fixed
* Sponsorship was under the Help, the "Who uses Hadoop" section has been added 
back to the homepage.

* Regarding the news: I think we have not enogh content to fill up the main 
page. So at least for now: I prefer to keep all the lists (Modules, related 
projects) on the home page. As a first step I would like to convert the 
existing site without too much content modification. But I understand your 
concern, and reorganized the news section. With using separated panels and 
display the full content of the latest news, it could be more visible now.

( + I totally agree about the getiting started: it could be refreshed, 
simplified, or even extend with a docker based simplified version)



> 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]

Reply via email to