----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/5765/#review8908 -----------------------------------------------------------
Thanks for taking this on. I have some initial suggestions / questions: 1. Since the documentation will change release-to-release, we need a place to permanently archive docs for individual releases in at least HTML format (providing and option for PDF is great too). How do we do that in this case? Remember we had talked previously about continuing to include the docs inside each binary release tarball as we do now. 2. There is a navigation bar (stripe) at the top that makes it look more like documentation than a web site. Plus it says Documentation there. Kinda strange. Maybe we should remove it. 3. Is there any way we can make the colors less like http://docs.python.org/ and more like http://www.python.org/ ? :) 4. Is there any way to get the links to indicate when you are on the page they point to? I find the left-hand navigation to be very awkward for a web site (when you click, it's unpredictable what will appear and disappear as you click down the LHS) 5. Quick search, Previous Topic, and Next Topic don't seem to be appropriate here (unless Search can be wired to work somehow) Finally, how would this integrate with Apache CMS? Will it be automatically deployed via the Maven plugin? I don't see that in the pom yet. - Mike Percy On July 5, 2012, 6:56 a.m., Ralph Goers wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/5765/ > ----------------------------------------------------------- > > (Updated July 5, 2012, 6:56 a.m.) > > > Review request for Flume. > > > Description > ------- > > This contains the source to build the initial version of the web site using > the CMS, Maven and Sphinx. To test the build just run mvn site and the > output of the site will be in target/site. "mvn -P pdf package" is supposed > to package the users and developers guides as pdf's to be deployed to the > site as part of a release but that isn't quite working yet. > > A few notes: > 1. The site will be committed to > https://svn.apache.org/repos/asf/flume/site/trunk. > 2. The site is incomplete in that it is missing release information. This > will be directly added once the site is published to the production svn > location. > > > This addresses bug FLUME-813. > https://issues.apache.org/jira/browse/FLUME-813 > > > Diffs > ----- > > > Diff: https://reviews.apache.org/r/5765/diff/ > > > Testing > ------- > > > Thanks, > > Ralph Goers > >
