[
https://issues.apache.org/jira/browse/HADOOP-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194359#comment-16194359
]
Elek, Marton commented on HADOOP-14163:
---------------------------------------
Hi, I updated the patch according to the latest modification on the svn site
(new commiters/pmc members + 3.0.0-beta1). Now it is up date date and can be
merged.
I suggested to commit the source of the site to a separated branch (eg.
asf-site-author) instead of trunk. We need one and only one version from the
site source at every time, and it would be more confusing the get different
versions on the different branches.
As we discussed the rendered site also could be committed to the hadoop
repository but using a different branch (usually the convention is to use the
asf-site branch) and we can ask INFRA to switch to use the git repo
(https://blogs.apache.org/infra/entry/git_based_websites_available)
I created a more detailed plan, how can we go forward:
{code}
1. Migrate the rendered/published site from git to svn
git checkout --orphan asf-site
git reset --hard
git clean -dfx
#where the publish dir is a checkout of the
https://svn.apache.org/repos/asf/hadoop/common/site/main/publish svn repository
cp -r /home/elek/hadoop-common-site/publish/* ./
#it takes a lot of time as it contains a lot of files
git add .
#also takes time
git commit -m "HADOOP-14163. Import existing published site from SVN"
git push
#Not that about 82MiB will be uploaded. The current size of my .git directory
is 3.2Gb in case of haddop, so most probably it's not a big change.
2. Open an INFRA ticket to switch from SVN to git
3. Commit the _source_ of the new site to an other branch
git checkout --orphan asf-site-author
git reset --hard
git clean -dfx
wget
https://issues.apache.org/jira/secure/attachment/12890692/HADOOP-14163.008.tar.gz
tar zvxf HADOOP-14163.008.tar.gz
mv hadoop-site-proposal/* ./
rm -rf hadoop-site-proposal
git add .
git commit -m "HADOOP-14163. Source of the new, hugo based hadoop site"
git push
4. Switch to the new site (until this point everything should be the same as
before on https://hadoop.apache.org):
For this, you need to have both the asf-site-author and asf-site author
branches checked out locally. It could be two different clone, or you can add
additional workdirs to your existing haddop checkout:
Assuming, you are on the asf-site branch:
git worktree add ../hadoop-asf-site asf-site
#remove old site:
#Please not that the first rm has no '-rf', the docs folder should NOT be
deleted.
rm ../hadoop-asf-site/*
rm -rf ../hadoop-asf-site/images
rm -rf ../hadoop-asf-site/skins
#install hugo binaries
#generate the new site according to the manual:
https://gohugo.io/getting-started/installing/
#generate the new site
hugo -d ../hadoop-asf-site
cd ../hadoop-asf-site
git commit -m "HADOOP-14163. Switch to a hugo based, generated site"
git push
+1. I will update the wiki pages about releaseing/updating the site
+1. We can setup an automatic jenkins jobs to generate the site in case of
changes on the asf-site-author branch
{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-14163-002.zip,
> HADOOP-14163-003.zip, HADOOP-14163.004.patch, HADOOP-14163.005.patch,
> HADOOP-14163.006.patch, HADOOP-14163.007.patch, HADOOP-14163.008.tar.gz,
> 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]
