hepabolu wrote: > > Once that process is done, I want to figure out how to get the info from > Daisy onto the website (preferably through an easier route/procedure > than the current one). If that works, I'm planning on updating the > website once every one or two months, depending on the number of updates > I've done in Daisy. > > OTOH: there are definitely docs missing from the website at the moment > (e.g. FAQs, already Bugzilla entry). I could focus first on getting all > the docs in Daisy, i.e. recreate the original website, and start the > Daisy-to-website update ASAP. Then there will be hardly new > documentation on the website, but at least all the "old" info will be > there again. > > WDYT? > Fine. For the navigation structure - I don't know if this has been discussed already, but I think the structure should follow the blocks structure, meaning one directory for each block with block specific documentation.
> >>>I'll add all documents that seem relevant to the portal to the >>>navigation tree to get an overview. >>> >>>BTW are there docs in TRUNK about the portal that should be added here? >>>My first impression is that they are identical. >>> >>> >>> >> >>Trunk and 2.1.x should be identical - apart from my latest additions. >> >> >> >> >>>I would also appreciate it if you could do future updates of the >>>documentation straight into Daisy (you do have a username and >>>doc-committer rights there). >>> >>> >>> >> >>Sure, if I don't forget about... :) >> >> > > If you don't mind I just remove the docs I worked on from SVN, so you're > required to update Daisy. ;-) > Yepp, +1 Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
