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

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

Yes, I also checked other projects, for example 
https://github.com/apache/incubator-openwhisk-website uses the same pattern: 
asf-site is the rendered, master is the source.

I think it's a good pattern, even if it needs multiple checkout during the 
release process (the master should be checked out to add the announcement 
entry, the asf-site should be checked out to add the raw javadocs).

I think we need 2 INFRA requests:

1. to create the hadoop-site repository
2. to create a configuration to refresh the https://hadoop.apache.org with the 
content of the asf-site branch of the hadoop-site repository.  
(+1. later: to create a job which automatically commits the new rendered site 
from master -> asf-site, as you wrote).

I am not sure if I can open these tickets as a simple contributor, but let me 
know if I can do anything to achive this. 

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

Reply via email to