You now have a fresh out of the box wiki/cms to play in and build up.
Here are some ideas for the first steps you can do to make it grow.
1. Create an interaction planWikis are interactive community oriented sites - of course it is not exactly an "if you build it they will come" situation. You need to plan how (and think why) people would want to participate in your site. Basically there are three reasons why people participate voluntarily in online communities.
- They can demonstrate their talent or knowledge. (Gain Status)
- They can get help or learn something. (Gain Experience)
- They can make new friends. (Gain Affection)
Sure there are lots of unselfish reasons that people participate too, but if people keep coming back there is something in it for them. How do you think people will interact in the site - what kind of collaboration or communication needs to happen. How can we deploy the tools Tiki provides to make this work: Choose which features to enable: Wiki, Blogs, Forums, Articles, Comments, Surveys, Trackers, User_Features, HTML_pages, the Shoutbox, etc.
2.Plan a Site Map and Use Structures to Create it.
What do i mean? Suppose we were doing a site for a family. Lets imagine they wanted a site tree like this one on the right => Note that each level in the hierarchy is indented one space (not one underscore - that's just for show).
When you cut and paste something like this into the window of the Wiki>Structure>Create a structure page, it will create all of those pages (if they don't already exist) and link them in a navigation structure. You can remove or disable the structure navigation later if you want - it won't affect the pages.
The Family Site Tree:
__Sleigh Ride Photos
_Grandparents 50'th Anniversary
_Todos for Dad
_Sams Stupid Chores
3. Make it BeautifulNever underestimate the power that the visual appearance of your site has on people. People are overwhelmingly sensory, and when there is no sound, taste or smell to your website (um, and i think there are ways of doing that now if you really want to) people will be very focused on the visual appearance - so don't skimp on this dept. Things to remember:
- Not everybody is an artist - the reason for 95% of the bad web design out there is that everybody thinks they are an artist and know what good design is. If only they knew. This is funny, because most people who can't sing know it and steer well clear of public singing performances. Think of it that way - your site is you on stage 24/7/365, and if you aren't sure you are a singer, you probably aren't and getting some help from somebody is a good idea.
- Everyone's taste is different - while there are a small number of tried and true principles in web design, they don't always apply for everyone. The difference between a good design and a bad design is that
- good designs will look really good to some people and won't bother others much.
- bad designs look ugly to everyone. (except the person who made it)
- Bad design drives away traffic. Plain and simple.
- At the moment, most (almost all) of Tiki native themes are bad designs. We're working on that - but theme design for complex CMS takes time. If you do develop a custom theme - consider sharing some or all of it with the community.
4. Get a spell checker in your browserHaving a spell checker in your browser is essential if you are doing live-to-web stuff. *Google Toolbar has a good spell checker in it that underlines missspelled words as you type. If you know of anything better, let us know.
5. Get the legal stuff right.
Note: Disclaiming all responsibility will not work - it is still your site in the eyes of the law.
Really, what you need to do to operate a public wiki or forum is relatively simple.
- run a clean site - it's your reputation after all.
- keep an eye on the recent change in your site to ensure nothing really bad stays up there for weeks.
- If someone complains about content on your site, take their concerns seriously and if you can not or will not satisfy their concerns - talk to a lawyer before you blow them off.
See also The Wiki Managers Startup Guide for more technical stuff.