Paul Bolger wrote: > I don't mind having a go, but I'm not sure where that doc is.
At the moment we have these docs. Not sure which doc it should go in. You can decide. Don't worry too much if it doesn't quite fit. Just add a new section, we can move that section later if we decide to restructure the docs.. cd forrest-trunk/site-author/content/xdocs docs_0_80/howto/howto-structurer-install.html docs_0_80/howto/howto-structurer-dsl.html docs_0_80/howto/howto-structurer-contracts.html > I gave > it a try and yes, common.fv seems to work. I haven't checked the > others yet, and won't write it up until I've tested it. > > Re. the SVN: I > have it installed and it seems to work (I'm using the tortoise > extensions). Command-line svn is sufficient, but whatever. > I'm more unclear about protocols, if I edit one of the > Howtos how do I submit it? If I'm unsure about whether something is > correct how do I pass it on for a second opinion? Just do ... cd docs_0_80/howto Edit the doc (retain existing whitespace or your patch will be unreadable). View the changed doc with 'forrest run'. svn diff > mypatch.txt Then go to Jira and add a new Issue, attach the patch. That enables anyone to apply it to their local system. http://forrest.apache.org/issues.html Look at the work that Addi did recently with the tools/forrestbot.xml She added <fixme> notes for bits that needed attention or that she was unsure about. One of the committers applied that patch and addressed some of the fixmes. The other fixmes can be gradually addressed on the dev mailing list. Most times we will apply the patch and then talk about fixing anything. Don't try to do too much in one go. -David > Ross Gardler wrote: > > David Crossley wrote: > > > Ross Gardler wrote: > > >>Diwaker Gupta wrote: > > >>>Paul Bolger wrote: > > >>> > > >>>>[views: .fv files] Is there a way to specify one .fv file for multiple > > >>>>input files, or does every page need an individual file? > > >>> > > >>>Yes. If you search through the archives, you'll find several emails from > > >>>Thorsten covering the resolving mechanism. I believe its something like > > >>>this (this is not authoritative, but indicative): > > >>> > > >>>o for pagename.html, first check if pagename.fv exists > > >> > > >>if not, look for one in the directory of the source file with the same > > >>name as the default *.fv (as defined in forrest.properties) > > >> > > >>if not, look for themename.fv in the PROJECT_HOME/resources/themes > > >>directory > > >> > > >> > > >>>o if not, look for themename.fv in the resources/themes directory > > >> > > >>(in the themer plugin) > > >> > > >>>o if not, use default.fv that ships with Forrest. > > > > > > Someone should document that. > > > > It's documented in the structurer locationmap ;-) > > > > (just a hint for anyone who may have the time to work on such documentation) > > > > Ross
