I’m thankful for a lot of things that resulted from creating Sueetie. One of the things I’m thankful for is the opportunity to build a library of documents and “think wiki.” Having the opportunity to gain a proficiency with ScrewTurn Wiki in the process has been a double bonus.
The Sueetie Wiki currently has 88 documents I wrote over the last year and a half, mostly technical documents with screenshots and code excerpts describing the intimacies of the Sueetie Community Framework. One thing I’ve learned is that managing a wiki and getting the most value out of it is not only about the quality or volume of documents, but how that library of documents is arranged and given meaning. How easy it is to find stuff, in other words.
As for organizing the Sueetie Wiki, there are five main pages that users need to see at all times. 1) The Main “About Sueetie” page which serves as a jumping off point to other content areas, 2) The full list of Sueetie Features, 3) Information about the Atomo Package for Developers, 4) Information about the Gummy Bear Website Package, and 5) a Changelog that is constantly updated with the new Sueetie Features and Fixes coming online.
To restructure the wiki around those five primary areas I revamped the existing ScrewTurn header links control. It formerly had “Random Page” and “Navigation Paths” links which I never used. And we’re talking about precious real estate at the top of each and every wiki page. That area is now Sueetie Content-focused and highlighted for better visibility. The wiki dropdown in the Site Menu mirrors those content areas.
One essential quality of websites for me is that they have to be pretty. I have to enjoy looking at them while I work. Somehow I forgot about that on the Sueetie Wiki, but am making up for it by adding Creative Common photos throughout the site as shown on the “About Sueetie” Main Page and Sueetie Manifesto below. (Attribution at bottom left.)
One of the ways I was muddying the Sueetie Wiki Structure was providing essentially four separate features listings. 1) Features Snapshot, 2) a Feature Rich page broken out by framework and each application, 3) Developer Resources, and 4) a Gummy Bear Updates page listing new features coming online.
I consolidated those four listings into a single Features Index page which serves as a main table of contents to the wiki itself along with a ChangeLog page displaying new features and fixes, both of which are in the wiki’s main navigation structure.
A wiki is a living, breathing thing and there are always improvements to be made, but with some TLC and cool things to write about we might get there.