|
Date: 9/11/2008 6:32 pm · Subject: Re: How to improve marketing / public awareness · Rating: 0
Speaking as someone new and getting started (in both webgui and web development of any kind)...
The demo for a day thing is what has so far sold me. I was able to test a lot of the functionality. Since my end users will be very non-technical, we were very impressed with the ease of use and the WYSIWYG model of creating content.
That said, if I were creating the site for myself, I'd probably have used another CMS just because... well, they're pretty easy to fire up. I've slapped together an Etomite site from nothing in a couple of hours. Same with a PHPBB based site.
Don't get me wrong, I'm hoping to learn my way around webGui just because it's so slick when it's running, hence why I'm still here, and I'm quite happy with the community involvement to answer my questions thus far. I might even buy a book if we make a go of this. But the ability to have something up and running really quick without having to ask questions and wait for a response would totally cement someone in.
I can try to detail my gripes with the documentation.
First, increase the font size on this site and in the wiki. Just a point or two. The tiny text on this site gets hard to read as I go through all the steps. The font as I write this post looks ideal, actually. (I use both Opera and Firefox as my browsers, so can't speak for how it looks in IE.)
Second, make sure there are no typo's in commands, and maybe use a different font or just separate the commands you want someone to enter. ("Preformatted" paragraph/font style might be ideal, given it's use in displaying code in other venues.) A visual indicator like that makes me think "okay, I need to type this in". It's sort of done right now with the indent, but this convention is broken in places.
Third, put a link to the platform specific notes at the top, mentioning that it might be a good idea to read ahead of time, in case the error in question pops up. Maybe flesh out the differences between distros a bit too, (for example, when do I use sudo? Is it assumed that root is needed everywhere? Etc.)
Fourth, the wiki appears to have user comments and "I did this and that" kind of bits. Comments are not a bad thing, but come up with a convention so that it doesn't just look like an instruction. Keep it clear. Something like this.
(I did this and that. - SteveD)
Keeps it clear, ya know?
Fifth, seperate long error messages from instructions. For example:
If you continue to get the following error, "make[1]: Entering directory `/data/wrebuild/source/perl-5.8.8/x2p' \n You haven't done a "make depend" yet!", remove the .depending directory as follows: rm source/perl-5.8.8/x2p/.depending
Would be much more readable as:
If you continue to get the following error:
make[1]: Entering directory `/data/wrebuild/source/perl-5.8.8/x2p' \n You haven't done a "make depend" yet!"
remove the .depending directory as follows: rm source/perl-5.8.8/x2p/.depending
(Except, here, instead of the bold, use the preformatted format available in the wiki. Also, the spacing is kind of fubarred in the forum here. It doesn't need the double spacing.)
Finally, the best advice I can give is to think of a really good manual or textbook you've read and try to emulate the style and tone it was written in. :)
--- (Edited on 9/11/2008 4:32 pm [GMT-0700] by SteveD) ---
|