For the docs, we indeed need to generate the documentation pages, and I can't see the reconfiguration page there. The zookeeperReconfig.xml file is there, but not the html. We typically update it upon a release, but since this page didn't go through during the last release, it sounds right that we need to update it now.
In general, it sounds like a good idea to have a "how to contribute to the docs" page. You may want to create a jira for that so that we can put our thoughts together. -Flavio On 26 Oct 2014, at 17:58, Wendy Smoak <[email protected]> wrote: > You're using the CMS? For all the documentation, or just for the > top-level site? > > What I see is per-version documentation in > http://svn.apache.org/repos/asf/zookeeper/trunk/src/docs/ > that gets built with "ant docs -Dforrest.home=..." > which generates content in /path/to/svn/checkout/zookeeper/docs > which gets committed to > http://svn.apache.org/repos/asf/zookeeper/trunk/docs/ > > So that looks more like svnpubsub -- at least, based on > ZOOKEEPER-1660, the new page did not get published, so it looks like > it depends on a committer to check in new files. > > And then the top level site looks like it comes from > http://svn.apache.org/repos/asf/zookeeper/site/trunk/ . > How do you build that locally to preview changes? > > The main thing I want to fix is the trademark/branding issues, but I'm > somewhat blocked by the lack of "how to contribute to the docs" > instructions. Let me know if it's hiding somewhere and I'm just > missing it. > > -- > Wendy
