What happens when you have the ultimate open-source application, used by thousands, with tasks simple and complex. Everyone contributes to a wiki or some other collaborative tool -- and the result is a giant mess where no one can find anything except by keyword searches.
This is the predicament of the WordPress Codex. Initially it may have included only one section, but it grew, and grew, and grew. And WordPress is still new.
Let's say you're just starting out with WordPress. Would you be intimidated by ... "The Codex"? Here's the home page of the Codex.
I had to actually use the Snagit scrolling window capture to grab that. It's immense.
What is the solution to organizing massive amounts of user-contributed information? As Web 2.0, open-source applications, and user communities proliferate, these questions will become more pressing. This is essentially WordPress's own wikipedia. I think that ultimately such large databases of information will only be searched by keywords. So each post/entry should have ample keywords. (Microsoft Word seems to offer its help documentation by keyword as the default.)
However, there's another technique -- one that hasn't been explored. WordPress allows you to do some single-sourcing in ways that might prove to be very useful. Each post or page has a unique ID. Similar to server-side includes, you can call and compile the content from a post/page ID onto a different page -- essentially single-sourcing your documentation.
Perhaps help administrators can select sets of documentation appropriate for different types of users -- beginner vs. advanced, developer, designer, etc.
I will be exploring this more later.
I'm actually not sure what the Codex runs with. I assumed it was WordPress, but it functions similar to a wiki. I've never actually contributed to it, though I've used it dozens of times.
Get new posts delivered straight to your inbox.
I'm a technical writer based in the California San Francisco Bay area. Topics I write about on this blog include the following technical communication topics: Swagger, agile, trends, learning, plain language, quick reference guides, tech comm careers, and certificate programs. I'm interested in information design, API documentation, visual communication, information architecture and findability, and more. If you're a professional or aspiring technical writer, be sure to subscribe to email updates using the form above. You can learn more about me here. You can also contact me with questions.