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

Akira Ajisaka edited comment on HADOOP-14163 at 4/4/17 10:38 AM:
-----------------------------------------------------------------

Thanks! Now I'm trying to publish the page to my GitHub pages.
https://aajisaka.github.io/HADOOP-14163/
(FYI: The size of published page is limited to 1GB in GitHub pages, so I had to 
remove some documents)

Some links related to relative path are broken, would you fix this? I'm 
thinking adding the following setting to config.toml can resolve this.
{code}
relativeURLs = true
{code}


was (Author: ajisakaa):
Thanks! Now I'm trying to publish the page to my GitHub pages.
https://aajisaka.github.io/HADOOP-14163/
(FYI: The size of published page is limited to 1GB in GitHub pages, so I had to 
removed some documents)

Some links related to relative path are broken, would you fix this? I'm 
thinking adding the following setting to config.toml can resolve this.
{code}
relativeURLs = true
{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-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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to