grow your wiki
The Scaffold pattern involves giving people a place to start by "framing" the content that should eventually go on a page. People often respond better to a page with a template than one that's completely empty.
Flemming Funch
writes "there is a basic need for "scaffolding" to hold the conceptual and organizational elements in place, especially during the early phases of "imaginative, interdisciplinary" interconnection. It may be argued that it is the lack of this scaffolding feature which prevents many potentially useful initiatives from "getting off the ground" - and staying up."
Anytime you're adding something new to the wiki, make a quick scaffold for people to collaboratively build content. It doesn't have to be anything fancy - in fact it's best with a wiki to use as little structure as necessary. Just as an empty page can deter people, an overly structured page can seem like the author already knows what s/he wants and doesn't need any help.
A simple set of headings is often enough for people to see how information should be organized and "what goes where."
When you post your meeting agendas on the wiki, use a template like this:
Date:
Agenda:
On this Wiki Patterns site, we use the scaffold pattern for all pattern pages:
Summary:
Usage:
Example:
Related Patterns:
Further Reading:
Wikipatterns.com is sponsored by Atlassian Software, creators of JIRA, Confluence, Bamboo and Crowd
Designed by Headshift Ltd
Scaffolding reminds me of the effectiveness of replacing "blank space" or (gasp) "procedures" with templates, as in Work Products that Work
For us newbies to Wiki, it would be helpful if the examples provided real examples of what a page should look like. For example, the Page Pattern example. What do you suggest for the Pattern Name and why not Title of the Page?