Daniel Carrera <[email protected]> writes: > Eric Kow wrote: >> PS. Meanwhile, we're working on switching our wiki to Gitit, which lets >> us use darcs as a back end. This is waiting on the moin stuff to be >> converted and uploaded, as I understand it. >> http://test.darcs.net > > Making a whole website with text files plus a wiki seems odd. It's > hard to imagine it having good navigation. How would you feel if only > the documentation was made with darcs + markdown + Pandoc?
Our "whole website" currently constitutes - one handwritten, largely static page, the front page; - the wiki; and - the BTS. I think that we're mostly happy with roundup as the BTS and (will be) happy with gitit as the wiki, which means that Drupal would only be in charge of managing the front page page. I'm against adding the complexity of a CMS in order to achieve subjective goals such as making those pages "look nicer" and be "easier to navigate". > In turn, using a CMS will give you a nicer-looking page, with menus > and trees and stuff to help people locate pages quickly. The CMS page > can just link to the manual as an external link. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
