Masterview devel - Jun 2006 - Time to start a docs subdirectory?

> > I agree about mentioning something about the locking problem you encou
n
tered in the docs somewhere.
 
 Starting to think about breaking up the monolothic index.html into some
useful chunks and adding more stuff.
 
Maybe something along the lines of:
 
   masterview
      index.html - overview, goals, history, index of avialable docs...
      docs
         ?api - subdir to generated plugin docs at some point???
         installation.html - supported platforms, prereqs, installation (gem
or standalone)
         userguide.html - usage
         reference.html - directives reference (builtin directives)
         troubleshooting.html - common problems people might run into, etc
 
~ Deb
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060603/7f7078b5/attachment.htm

I was just about to open a doc sub-directory and get a couple placeholders
dropped in for stuff I want to start writing (troubleshooting.html;
configuration.html to go with the config rework pass I''m doing today),
but
now I can''t find the message where I think you explained why you just
put
that into svn:ignore on the trunk dir.
 
I''d like to back out the ignore on the trunk and install doc, add a
couple
files, and change the rakefile rdoc generation task to generate into
doc/rdoc (?doc/api?) rather than directly into the main doc directory, which
then gets svn:ignore="rdoc"
 
Am I missing something here?!
 
~ Deb
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060603/03689b6b/attachment-0001.htm