> That seems sensible. Are there any limits that should be followed so that
> you can recreate the FAQ as a single document for a release?
Just make sure it is some sensible format and categorized
accordingly. I'll see if I can break it into multiple pages without having
to flip back and forth between browser tabs when comparing/editing multiple
sections at once (like cut-n-paste between sections, or moving parts
around).
> updated in the wiki (which is now accepting updates; if you had trouble
> before, please try again). If the FAQ can be autogenerated, it will be in
> the next FAQ version as well.
Thank you.
Also, a small note.. I just updated the "SiteScooperStepByStep"
section to properly wiki'ize it, and noticed a few things there that I
should point out:
When you want a literal [Foo] to appear in the wiki, use ~[Foo],
otherwise it will get linked as a sub-page.
The same goes for SomeWord, like PyPlucker, in C:\Python\PyPlucker,
for example, would be ~SomeWord and C:\Python\~PyPlucker, respectively.
When you want to make a link, use [Name|http://url].
I abhor CamelCaps in wikis, and prefer to use [Camel Caps] instead,
because it is much more natural to read, than smashing the words together
and AutoCappingEachNewWordInThePhrase. I've done that for the SiteScooper
HOWTO on the Helpful Hints section, and moved the content into there.
It takes a bit of time (and previewing is important, because you'll
see these issues almost immediately), but once you get the hang of the tags
and sections, it'll be as easy as writing HTML... er.. scratch that ;)
I'll figure out the authentication bit at some point. I might have
to hand-roll an account-signup piece. Maybe tying it into the same usernames
that Mantis uses can help, or sticking both of those into LDAP. Not sure
yet.
Let's keep it going, and keep updating what we can.
d.
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
