community

You have set up a website where multilanguage content submission and display was a requirement? What was the workflow specified by the customer? How were relations between different languages defined? Did you have all content translated? Was translation into specific languages a requirement for publication? Did you translate all navigation and even site level images? What was special about that project?

An internationalization use case consists of the requirements you faced, the user workflow you needed to support, and the interface you provided to the user. We are not interested in dirty implementation details (modules, PHP code, CSS) at this stage, only higher level information about how you built up multilingual content, interface, navigation and site design. You don't even need to talk about Drupal projects. If you have any other use cases to share, which you experienced out of Drupal, we are interested. The goal of the above questions are only to start you up, don't let them stop you from sharing your story in greater detail.

You can either post a new story to this group or comment on this story with your use case. Thanks for sharing!

As part of our voyage to build up a solid base for Drupal core i18n, it is important to see, how other systems approach this problem. Maybe you have used some other system which has incredible i18n capabilities, or you have heard of one? Tell us the story, or just post a link to this system (as a comment), which we should learn from. I plan on setting up some of those you suggest (those that seem like the most valuable in this field), and write up my experiences, as well as the workflows, capabilities, features we can learn from.

For those of you who weren't able to attend this week's Drupal User Group Event, the main topic of discussion was community building.

I came across this article while reading over my blogroll today and felt it was on-topic enough to share with this group. It ventures a little bit into the area of users versus customers, but I believe many of the ideas are the same. An online community is a group of "browsers" and "members". To encourage movement from the "browser" to the "member" level, you much create a sense of belonging in the "browser".

Read on below:

http://37signals.com/svn/archives2/a_transaction_makes_a_customer.php

In Drupal out-of-the-box, there are four available ways to lay out comments:

• Flat, expanded
• Flat, collapsed (titles only)
• Threaded, expanded
• Threaded, collapsed

To add another wrinkle, there's the option of having the most recent comments at the top vs. new comments added at the bottom. In my experience, on blogs, the most common practice is to have flat expanded comments in chronological order, while on community sites that are not old-style bulletin boards (phpBB, FUD, vB, etc.) the practice is to have threaded, expanded comments posted in chronological order (sub-threads in chron order, comments within threads in chron order).

Okay, so I created this group partly because I'm interested in the topic and partly because I wanted to try out OG. I probably won't be back unless someone else also takes an interest in this group.

I am the volunteer web developer running the web site for New Hope Church. I've just updated to Drupal 4.7 and now am working hard on the site to make it nifty. Our church is in a college-town in Kansas and we've got a good group for using online collaboration to help facilitate our small-group Bible studies, called LIFE groups.

Hey all,

I'm completely new to Drupal, so I'm not sure if this is the right way to put out a request, but I am part of a group called Friends Without Borders which is bringing about a new approach to world peace through inviting children into the democratic process. It's as simple as writing a letter. Check out our current site: http://www.FriendsWithoutBorders.org

To understand the depth of this project, also check out this 5-minute video: http://video.google.com/videoplay?docid=-8921932280014622466&q=Friends+W...

We are heading back to India and Pakistan soon to move forward with Round 2 of this campaign. After that, who knows where it might lead...

Hey all, just thought I'd throw my hat in the ring so Laura doesn't feel too lonely up there on the front page.. ;)

What I would love to see come out of this group is some "best practices" documents for people building community sites. Especially sites geared towards online communities where the end user has special needs.

By special needs, I am not only referring to accessability issues, (although that is certainly one concern) I also mean things like ;

• How do you build sites for youth that give them adequate privacy, security and priveleges(spelling?) so they can feel like they own the space, while keeping parents satisfied that their children are safe from online harrassment and stalking?

• How do you provide a granulated set of user roles for a semi-closed group of low-level technophobes without overcomplicating the means to contribute to the site? [not like I've ever had to deal with that or anything ;)]

• How do you explain copyright and copyleft to inexperienced webpublishers and transmit the importance of the issue adequately? Is it even necesary? What are we leaving out if we don't talk about copyright before giving a community a site they can publish to?

• How does a web developer/social marketer do knowledge transmission for community-building online to end-users/ site editors who mostly use analogue technologies to communicate with their constituents.

• When is a community website the solution and when is it overkill? How do you help your client develop a project/product that really fits their needs.

...whatever this group ends up being. This is a group to talk about -- well, the description above tells it all.

So why not kick of things here by sharing your thoughts? What should we talk about? What makes for a good online community?

Possible starter: The Netsquared conference has been abuzz on community building. Did anyone attend? What was your take?