Personally, I've always felt something as large as an OS should be well documented and some approach to _not_ assuming the user knows everything, much as SUSE and Red Hat document their GNU/Linux systems. Additionally, I like how the Debian documentation is put together (non-wiki) and install-able via apt-get in various formats. That leads me to believe something like Texinfo would be a good starting point for an overall gNewSense documentation set; an original and unique set from the wiki, but both something that informs the wiki and is informed by the wiki.
Cheers. - Christian Bryant On Sun, Jun 23, 2013 at 2:15 PM, Sam Geeraerts <[email protected]>wrote: > I've created some new documentation about packaging [1]. We already have > [2] and [3], but I felt that this deserved its own section and that it > would be clearer to split the tutorials for new and modified packages. > On my todo list is the non-native package section, trimming the new > package page and improving the FSDG package page. > > So far we've used nesting to group pages, but that limits pages to one > group. I'm experimenting with categories for these pages. I see > both techiques used in the Debian wiki [4], but I haven't found a > method to that madness, though I don't have much difficulty finding > information there. Maybe it Just Works organically. Opinions? > > [1] http://www.gnewsense.org/Packaging > [2] http://www.gnewsense.org/Building_A_deb_Package > [3] http://www.gnewsense.org/kgoetz/FSDGPackageRebuild > [4] http://wiki.debian.org/ > > _______________________________________________ > gNewSense-dev mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/gnewsense-dev
_______________________________________________ gNewSense-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/gnewsense-dev
