Hi Steve, Agree that the general approach of just injecting most/all of the website HTML into the distro, while suboptimal, is probably workable for ApacheCon. In some ways though, it just pushes the question down a level: how should the docs should be organized on the website?
One of the main concerns I have with the website docs right now is that because we've only recently had a distribution, we've not been describing things from the 2 perspectives we should: that of the Beehive contributor (someone who works on the Beehive project itself), and that of the Beehive user (someone who downloads Beehive and builds apps with it). Everything right now is from the perspective of the contributor, and I think that needs to be fixed for ApacheCon. Currently the nav tree on the website has a single "Documentation" heading. How about separating that into "Contributor Documentation" and "User Documentation" (it might make sense to move "Contributor Documentation" under "Community", but that's probably worth its own thread)?. Stuff like "Building Beehive" should go under "Contributor Documentation", whereas everything under "User Documentation" should be written in terms of a user w/ an installed distribution (as opposed to a developer with a Beehive svn tree). What do you think? > -----Original Message----- > From: Steve Hanson > Sent: Wednesday, October 20, 2004 2:44 PM > To: Beehive Developers > Subject: Changes to docs, now that we have a distribution. > > Hi all: > > Now that we have a distribution, we need some way to get docs into it. > > The easiest way to do this before ApacheCon, is to inject the > HTML web site (trunk\site\build\site\index.html) into the > dist. Any objections, concerns about this? Or better ideas? > > -Steve Hanson > > > >
