RE: Editing existing entries?
"Anton van Straaten" <[email protected]>
| Newsgroups | gmane.lisp.scheme.plt.schematics |
|---|---|
| Message-ID | <[email protected]> |
> I'm new to using a wiki and a little shy about editing. I'd like
> to make some major additions to the string topic, but I'm not
> sure if it should be a comment or if I should just change the
> text Jens wrote. What would the proper etiquette be?
I think that's something we need to work out.
If you want to make lots of changes to text someone else has written, I
think adding a comment makes sense, so it can be discussed, unless the
change seems totally uncontroversial (a judgement call).
OTOH, if you have major additions, i.e. new material as opposed to changes,
I think a separate topic is often a good idea. For example, looking at what
you've done on the StringRecipe page, you could create a StringBasics topic.
After that, you can add it to a higher level page, like StringRecipes.
IMO, on an "index" page like StringRecipes, anyone should just add new
entries as they see fit. (Deleting entries should probably be discussed.)
I'd suggest that index pages like StringRecipes should be created using the
%TOC...% command, e.g. %TOC{"StringBasics"}% or %TOC{"StringBasics"
depth="2"}%, to automatically pull in the headings from the specified topic,
up to the specified depth. That way, changes to headings in the referenced
topics will automatically propagate to any & all parent topics.
This is a little different to what I wrote on the AuthorGuide page - where I
talk about using %INCLUDE..%, but we're still working this out. There may
still be cases where it makes sense to use INCLUDE, if the whole text of a
topic needs to be included inline in the higher-level topic.
Anton
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click