Wiki Patterns
grow your wiki
EditThe WikiPatterns Pattern Language
The pattern language for WikiPatterns has yet to be finalised. This template represents our starting-point, but we suspect that it is likely to be refined as we open the site to more contributors.
- Name - all patterns must have a memorable name
- Summary - after the name, sum up the intent of the pattern in one or two short paragraphs
- Usage - describe in what circumstances this pattern arises, and how it is implemented
- Example - relate the pattern back to some concrete example
- Related Patterns - list other patterns that are influenced by, or influence the application of this pattern
- Further Reading - list external sites, wikis, blogs that discuss the pattern
Adoption Patterns
Adoption Anti-Patterns
Wikipatterns.com is sponsored by Atlassian Software, creators of JIRA, Confluence, Bamboo and Crowd
Designed by Headshift Ltd
We might see the label as another attribute of a pattern, i.e. the categorisation of the pattern as 'People Pattern', 'People Antipattern', etc. So would it be worth adding Categories (Labels) to the above list?
We might consider adding tags to help those searching outside the wiki to find content within a wiki.
Those attributes have some useful metadata, but why not, for the core description, follow Alexander's "Context, Problem, Solution"? Those are pretty clear: what's my requirement (problem), what assumptions are being made about the environment (context), and what do I do (solution).
Currently all that information seems to be lumped under either "summary" or "usage." Not only is the Alexander structure not there, but it's tough for me to tell how those two are supposed to be different.
I recognize I'm being a bit of an emulatorReplicator in posting this as a comment rather than just editing, but I haven't been in here long enough to have a good feel for the impact to what's already here.
Hmm; now that I look, the page hasn't been touched in 8 months. Is anyone watching?