Thanks for addressing this. Getting rid of Hadoop's use of forrest is a good thing.
In terms of content, the documentation links should be sorted by number with only the latest from each minor release line (eg. 3.0, 2.7, 2.6). The download page points to the mirrors for checksums and signatures. It should use the direct links, such as https://dist.apache.org/repos/dist/release/hadoop/common/hadoop-2.7.3/hadoop-2.7.3-src.tar.gz.asc https://dist.apache.org/repos/dist/release/hadoop/common/hadoop-2.7.3/hadoop-2.7.3-src.tar.gz.mds Speaking of which, Hadoop's dist directory is huge and should be heavily pruned. We should probably take it down to just hadoop-2.6.5, hadoop-2.7.3, and hadoop-3.0.0-alpha2. You might also want to move us to git-pubsub so that we can use a branch in our source code git repository to publish the html. Typically this uses the asf-site branch. .. Owen On Mon, Mar 13, 2017 at 7:28 AM, Marton Elek <me...@hortonworks.com> wrote: > > Hi, > > In the previous thread the current forrest based hadoop site is identified > as one of the pain points of the release process. > > I created a new version of the site with exactly the same content. > > As it uses newer site generator (hugo), now: > > 1. It’s enough to create one new markdown file per release, and all the > documentation/download links will be automatically added. > 2. It requires only one single binary to render. > > > A preview version is temporary hosted at > > http://hadoop.anzix.net/ > > to make it easier to review. > > > For more details, you can check my comments on the issue > https://issues.apache.org/jira/browse/HADOOP-14163 > > I would be thankful to get any feedback/review. > > Cheers, > Marton > > >
