[
https://issues.apache.org/jira/browse/HADOOP-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953599#comment-15953599
]
Elek, Marton commented on HADOOP-14163:
---------------------------------------
I uploaded the final proposed version. For the sake of the simplicity I
uploaded as a ZIP file instead of a patch. The whole author directory
(https:////svn.apache.org/repos/asf/hadoop/common/site/main/author) should be
replaced the files from the zip.
I suggested the following order:
1. git svn clone https://svn.apache.org/repos/asf/hadoop/common/site/main
2. Delete the content the author file and extract the content from the
HADOOP-14163-001.zip. (Commit)
{code}
cd author
rm -rf *
wget
https://issues.apache.org/jira/secure/attachment/12861716/HADOOP-14163-001.zip
unzip HADOOP-14163-001.zip
mv hadoop-site-proposal-master/* ./
rm -rf hadoop-site-proposal-master
{code}
3. Delete the old site and generate the new site. (Don't use the attached
rendered site. It's an older version. I didn't upload a rendered site, because
I think It should work for at least one committers, not just for me ;-)
{code}
cd publish
\ls -1 | grep -v docs | xargs -n1 rm -rf
cd ../author
hugo --destination ../publish
{code}
(Hugo should be installed with brew/apt-get or with downloading the single
binary)
4. git push the improved version to a new asf-site branch of the apache git
repository
5. File an INFRA issue according to the
https://blogs.apache.org/infra/entry/git_based_websites_available
> 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: [email protected]
For additional commands, e-mail: [email protected]
