Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 8 Sep 2017 08:20:00 +0000 (UTC)
From: "Elek, Marton (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13049378.1489002006000.58802.1504858800342@Atlassian.JIRA>
In-Reply-To: <JIRA.13049378.1489002006000@Atlassian.JIRA>
References: <JIRA.13049378.1489002006000@Atlassian.JIRA> <JIRA.13049378.1489002006436@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HADOOP-14163) Refactor existing hadoop site to
 use more usable static website generator
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 08 Sep 2017 08:20:09 -0000


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

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

The patch is applicable with `git apply HADOOP-14163.007.patch`. Not sure what is the problem on yetus side.

As 2.8.3 and 3.0.0-beta is comming it would be great to merge it before these releases. I am ready to update the link on the releaseing wiki pages to the new tutorial after the merge.

> 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-14163.004.patch, HADOOP-14163.005.patch, HADOOP-14163.006.patch, HADOOP-14163.007.patch, 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org