On Sunday 30 December 2007 04:22:35 Josephblack wrote: > On 29/12/2007, Lourens Veen <[EMAIL PROTECTED]> wrote: > > > It's hard to keep a wiki structured it seems; most wikis are pretty > > hard to navigate. Ours isn't all that bad, but it can still be > > better <snip> > > > > So have a look at > > http://wiki.opengraphics.org/tiki-index.php?page=NewHomePage and > > post your comments. > > Yes, it does look a bit clearer, though I am not sure we had enough > for a marketing page yet (it was the first page I clicked on<g>).
Well, it's a marketing project more than a page. It's separate because it really is separate from the development effort, and if we stick its contents directly on the home page then things get cluttered again. > The > documentation page did help in that we could have pages that were > being worked on, off the front page. Perhaps we could have a link > called drafts or something. Isn't a wiki a perpetual draft? You raise a good point though. For documentation, the wiki is both workspace and reference location, and it should be clear which parts are under construction and which parts are considered "stable" releases. First, I should perhaps explain a bit more what goes where, in my mind. On NewHomePage, there's a Library section (this should be a separate page perhaps). This is where I would like to put all the generic reference documentation about things other than the stuff we make. Verilog tutorials, information about various external standards like VGA, VESA and PCI, and so on. Ideally it would give you all the context you need to understand our stuff and help us build it. Then each project has its own documentation. So the schematics and so on for OGD1 would go on the OGD1 project page, the documentation for HQ would go on the OGA1 page together with all the other OGA1 stuff. Likewise for the other projects. Now the question is what we do with releases. Obviously, the products we deliver through Traversal will come with documentation, but I think we should put this stuff on the OGP wiki as well. At the same time, we need room to work on the documentation. For the tutorials in the Library section, we need a kind of workspace for unfinished ones as well as a part with finished ones. What we could do is add a Releases section at the top of each project page, where you can download a tarball of the code and read the corresponding documentation. The documentation could be on the wiki; we can just copy the work-in-progress page when it's done and add VersionX.Y to the name or something, and then continue updating the original as the code evolves towards the next release. Alternatively, we could make a PDF version of the docs for each release, that might be nice as well. Thinking about the library more, I think it should be a separate page, with different sections for different subjects, and for each section a "Workspace" part where unfinished tutorials and the like live. > > I've also moved things about a bit again in the Development Tools > > section, as the hierarchy got maligned a bit. > > > > I would like to move John Griessen's work with gschem to the OGD1 > > project page, and split up the current OGD1 page into various pages > > since it's got rather large. I haven't got around to that though. > > yes, I had been thinking It may need breaking up/reorganizing. I'm going to give people a chance to respond to this thread for another week or so, and if noone objects then I'll put up the new home page, and look at this as well. I don't want to keep too extensive a set of doubles as that is just confusing and potentially a lot of work keeping things up to date. Lourens
pgpgt1zXQwtcC.pgp
Description: PGP signature
_______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
