Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
The Internet

Building Online Communities 112

chromatic writes "I've published an essay about building online communities on the O'Reilly Network. It pulls together several thoughts gathered from observing sites like Slashdot, Everything2, and Perl Monks."
This discussion has been archived. No new comments can be posted.

Building Online Communities

Comments Filter:
  • by limekiller4 ( 451497 ) on Thursday October 24, 2002 @08:55AM (#4521160) Homepage
    For anyone interested, this months Linux Journal has an article on OpenACS (page 12) which reads, in part:

    "It's easy to say that OpenACS is a toolkit for creating on-line communities. But what does that mean? For starters, it means that OpenACS comes with working versions of most of the applications you're likely to want on a community web site. It handles user registration and administration, forums, FAQs, group (including a rich permission scheme), news updates, file storage and distribution, personal home pages, surveys and a we-based calendar. As you might expect from a modern system, administration of the application is done almost completely through the Web, with only a few configuration files."

    From OpenACS' [openacs.org] frontpage:

    WHAT is OpenACS?
    OpenACS (Open Architecture Community System) is an advanced toolkit for building scalable, community-oriented web applications. If you're thinking of building an enterprise-level web application, OpenACS is a solid, proven foundation that will give you a 3-6 month headstart.
  • Nice article. (Score:5, Informative)

    by krs-one ( 470715 ) <(vic) (at) (openglforums.com)> on Thursday October 24, 2002 @09:42AM (#4521518) Homepage Journal
    If you notice my sig, you'll see that I run an online community dedicated to OpenGL programming (and the many facets thereof). I started the community back in March 2002, and I love it to no end. It's relatively small (especially compared to Slashdot), but its an awesome place to hang out and talk with other people interested in OpenGL, game programming, and Linux. Now, enough about my community, here are my ideas about the article.

    Regular users will develop a sense of community ownership. As a whole, their content contributions probably outweigh yours...

    This could not be more true. Running my site is a full time job (along with school). I rarely get to answer the questions that my members have. Luckily, I've recruited some top notch moderators who answer questions and keep the forums inline. If it weren't for them, members wouldn't come back. Adding to that, I must say also: a lot of your members will know more than you do! Get over it, learn from it. I'm only 18, and have had a limited time using OpenGL, whereas I have many professional programmers in my community. Most people love to help.

    Besides letting community leaders and members perform administrative work (content production, content moderation, software development, content rating, the donation of hardware or bandwidth fees)...

    This is crucial for a site to survive. At my site, we have tutorials. So far, I've written all but 3 of the tutorials. Tutorials, especially ones as long as mine, take a long time to write. One idea I thought up was to ask members to write tutorials. You'd be surprised how many members want to write tutorials and get work displayed, and on somebody elses website no less! If you need help paying for the site, set up a donation link (PayPal is easy, even with all of the warnings). Many members are willing to contribute something to the site, especially if they see it become something tangible (like prizes to a contest).

    Encourage community archives. Provide a way to address individual bits of history (messages, chat logs, event histories) in finely-grained units.

    This is a must. New members will want to research to see how the site came about, and things that occured during the sites lifetime. I think that people are very interested in history. They want to know about the past. Keeping archives is not very hard, especially if you can set up an automated system.

    You will never please some users. A few will stick around only to see your next mistake. They tend to be vocal. Their pessimism doesn't make them wrong, but it can be grating.

    Again, this is where moderators and other regulars to the site come in. When someone on the forums posts something degrading or offensive (yeah, sue me for censoring people, there are some things that are not appropriate for an OpenGL forum. I don't want my forum to be full of SPAM), the moderators immediately step in and either edit the post or delete it entirely. If a user is being particularly harsh, and I am not there to quell them, a moderator will say, "Hey, listen, Vic works his hardest on the site. He's not perfect, and he'll take care of you. Just have some patients." It's a very rewarding feeling when people want to help you with your site without pay. Occasionally, when I make a news post, I'll thank my moderators for their hard work so they know their work is appreciated.

    Simplicity may appeal to some users. The lack of sophistication (reply notification, searching, revisions, and access controls) may put off some users, and an ugly or awkward user interface may get in the way sometimes, but a community can grow in spite of the mess.

    This is very true. Thus, I approach my community two ways. There is the main news page, the main page of the site, and then there are the forums (similar to any message board you see now). The main page (and subsequent sub pages), are very simple. A DIV in the middle of the page is all that is needed for news. I use style sheets to control the data in there, and all in all, it comes out very nice. I am currently redesigning the main page to add a few more visual controls, but its still very basic. However, when you click on the Forums link, you go to the much more "complicated" forums. There, you can post messages, be alerted of replies, send private messages and email, search for past posts, etc. It doesn't hurt that my forums looks particularly nice. :)

    Finally (I promise, this is my last point), you need something to keep repeat visitors. There must be a way for visitors to interact with the site. No one wants to just read news posts and view a few tutorials. When they are done, they won't come back (I feel this was an underlying assumption in the article, though). Two more ways to keep visitors: Contests! Yes, they cost money, but yes, people love them. Especially when they can get a free Radeon 9000 or 256MB of Crucial RAM (hint hint) from entering it. Even better: use the donations other members made for this. The second way is to give visitors free stuff without you having to pay for it. For example, anyone who is a member of the forums, have more than 10 posts, and contribute well to the community can have their own subdomain on the site (and an email address and a free MySQL database/PHP support). This is better than a lot of hosting plans. Members can use the subdomain to show off their work or write tutorials on a different facet of OpenGL. I require NO ads, but I casually suggest that if they want to link to me, I'd appreciate it.

    Well, thats all about me and my online community experience. I wouldn't trade it for the world.

    -Vic
  • by duckHole ( 562897 ) on Thursday October 24, 2002 @12:23PM (#4522902)

    which would make your 2-pager much wittier than Derek Powazek's "Design for Community [designforcommunity.com]",which i also liked. he covers much the same territory and reaches similar conclusions...

    A strong community can overcome technical limitations. It's possible to write a Wiki or a weblog in under a hundred lines of code. Simplicity may appeal to some users. The lack of sophistication (reply notification, searching, revisions, and access controls) may put off some users, and an ugly or awkward user interface may get in the way sometimes, but a community can grow in spite of the mess.

    & th thing i have to remember is that different users have different perceptions of what's complex or not... so that the user interface becomes a filter for the type of user a site will draw. black pages, obscure icons and no text labels will appeal to certain folks--among other things, it lets members know they're cool because they're web-savy enough to figure it out. so the techne carries content just like the wording on the homepage...

If all else fails, lower your standards.

Working...