On Feb 10, 10:31 pm, vfclists <[email protected]> wrote: > I don't think it is a smart idea to build a documentation website with > Drupal. Drupal doesn't do very well in that respect. Drupal's own book > module has more than its fair share of issues and complaints, and is > one of the reasons why there are so many complaints about Drupal > documentation. You CAN if you are willing to install and test the necessary > combination of modules, customised templating, and perhaps some CCK >
Hi vcflists, No, a basic WYSIWYG is sufficient to start with . We can always add modules as the need evolves. I don't want to jump into CCK etc now, and doom the project right from the start > I suggest using a well established wiki or using Drupal with some text > format that makes it easy to translate the documentation into a pdf or > chm format, like markdown or something along those line. > > As Massimo has said - if you create the docs he will link to it. Just > agree on what format the docs will be built in, mostly which structure > focused tags are to be used. It is much easier to create a wiki with a > book chapter outline which contains "only" links to contributors pages > on the topic which have the right structure. With the passage of time > it will be easier for the editors to decide what should go into an > 'official' manual > > @anand > I have looked at site, and I see no signs of > http://drupal.org/project/geshifilter. > You could probably add betterformats and a few content related > modules. Stay away from any kind WYSIWYG, and > considerhttp://drupal.org/project/bueditorandhttp://drupal.org/project/wmyeditor > I am very clear that we will not build the core documentation with Drupal, The text that goes into Massimo's book, is in Latex and probably could move to RST+Sphinx. The expectations of high quality, authentic info is a given. If anyone wants to contribute a chapter or a section to the core doc (s)he must be willing to wrangle Latex or RST. I am suggesting Drupal for non-core, user generated docs. This will probably be in a state of flux with users updating docs themselves. Massimo could pull some text from here , reformat and include in his book. I hope the disctinction is clear. Given that the target audience (for Drupal or MoinMoin) is any random user, including new comers, or non-coders (eg: graphics artist / CSS experts), we can't dump a cryptic format on them. One of the reasons for low contributions is offering difficult processes to such a person. Whereas HTML with ckeditor is as easy as it gets. > My advice is to use bueditor or wymeditor to create a set of buttons > and tags based on a small subset of DocBook format and ensure all the > content is entered in that format. Documentation should go in > structured first time around. You really don't want any kind of > wysiwyg in there > It might be tedious initially but such an approach will pay of in the > long term > The short term goal is to unify and get going otherwise, as a community we will be "famous" for "all talk and no walk" Regards Anand > my 2 cents > > On Feb 4, 11:00 pm, mdipierro <[email protected]> wrote: > > >http://webtopy.org/community/tips-examples -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
