How Content Types function in Drupal Commons
The short, bullet-point version of this information can be found here.
What follows on this page is a bit more verbose explanation of the same info.
Drupal Commons provides many different content types. The function of most of them is self-apparent. However, there are some differences. Here is how they vary. An example is provided in each section below; assume that these examples are found on a Drupal Commons community site for owners of boats built by the SeaWorthy Boat Corporation (fictional), and the pages listed are being posted in a group on that site called Wooden boats.
Note that with all content types, a user must be a member of a group before they can create any of these types of content within a group. Note also that other users may, or may not be able to add comments to a given page of content depending on the comment settings set by the original page creator.
Blog
- Blog posts are something for people - or group administrators - to use to express content that has temporary value. They capture updates in the life of a person, or in the activity of a group. An example title of a personal blog post might be "What I learned when I took my first wooden boat out for a test;" in the same community/group, an example title of a blog post by the community manager might be "Reflections on the September 2010 group meet-up at the dock."
- Note that only the original blog post creator can edit the original "body" of the blog post.
Document
- Document pages basically exist as a container for attached files. For example, assume a SeaWorthy customer modified the wiring harness of their navigation console to add a third-party GPS device, and wanted to share the wiring diagram of the rewired console. The user would create a page called "Wiring harness diagram for adding a (brand) GPS to the Model-123 wooden boat console". This person would add some text to the body of the page, then upload a PDF (or JPG, ..) of the wiring diagram.
- Note that only the original document page creator can edit the original "body" of the document page.
Discussion
- Discussion pages provide a sensible way for users to have discussions with each other. A member of the group starts a discussion by creating the initial page for the discussion, then other users post new comments, or replies to existing comments (to create a threaded discussion.)
- Note that only the original document page creator can edit the "body" of the discussion page.
Wiki
Wikis are different from Blogs, Documents, Discussions & Events in several ways:
- Any member of the group can edit the "body" of the discussion page. This permits all the group members to keep the content of the page up-to-date and correct simply by editing the page and creating / modifying content. (Much the same way Wikipedia works.) Our fictitious boat company/group might have a wiki page titled "Comprehensive list of boat maintenance tasks for model ABC-123", where every ABC-123 boat owner adds items he/she think are important.
- User can enter content using special techniques to simplify links (called Wiki syntax).
- If users use Wiki syntax to create links to pages that do not previously-exist, users who click the link (and who have permission to create pages) will be automatically presented with a new page for creating the content of that page (a typical Wiki feature).
- Every time a Wiki page is saved, a new version of that page is created. Users can compare versions to see the differences between pages.
Events
- These can be used to announce upcoming events, such as meet-ups of the group members. This is often most useful for community sites made up of people who are not in the same organization, since (in that case) the group members are unlikely to be using a single organizational calendaring system.
Page
Pages are the normal Drupal Page content type. This is the main defined content type that need not belong to a Group when being created. It is preserved so that site owners can create content that is of general use for the site, e.g. informational pages, marketing pages, etc. Commons works in the normal Drupal way with these pages, such that it expects the user to create a menu entry for the page, or link to it from somewhere else.
Notes:
- Breadcrumbs are not created for these pages, since the breadcrumb system is driven off the Groups architecture (not the menu architecture) in Release 1.
- By default only users with the Community Manager role can create Pages.


Comments
Thanks Jay. This is very
Thanks Jay. This is very helpful basic information and should perhaps be featured for this group, even for Commons. I think people installing/considering installing Commons want to know:
1) what content types are automatically created
2) what user roles are automatically created
3) what features and modules are included in this profile, and what kind of functionality are they organized into
4) what templates are included
If these four items could be featured documents for this group, it would be very helpful for new users exploring the Commons profile.
page type?
What about creating pages with content? As I understand it, in vanilla drupal, the "Create Page" interface gives you a "body" field to work with (http://www.drupalace.com/EDAM/create_page). When I try to create a page in Drupal Commons, all I can do is modify the layout -- there's no way to enter page-specific text. am I misunderstnading the role of pages in drupal ocmmmons? Thanks,
Matt
I just added a description of Page contents
Note the Notes. Does this address your issue in creating the page body?
This will trigger an email
Notification to Jay
I'm starting to get it...
... But I'm still confused
I understand the idea behind the difference between Blog posts, Discussions, and Documents as explained in Jay's post, but at first I couldn't see any difference at all in the actual implementation of those concepts in Drupal Commons. I gather Wiki posts can use Wiki syntax.
I just installed DC this morning (BTW was very impressed by the installation process; really felt I was taken by the hand to walk around the pitfalls!).
I created a few documents, wiki posts, and discussions and as I switched from one to another I must say they all looked the same to me. (as I look again I see the columns aren't the same, but the tables look very much the same). I understand I am supposed to write blog posts that have a short time-span, etc, but that seems to be entirely up to the author. I could see nothing to stop me writing the Founding Principles of the Company in a blog post, or indeed anything to encourage me to use the form most adapted to the situation. I see no cast iron difference between the types of objects; it seems to be "well blog posts are sort of more like so and so", but basically everything has a date, you comment on anything, everything has attached files, in the list of items every item has the photo of the person
The drawback of all those the tabs is that you have to click on a tab to see if there's anything inside, or if there's anything new inside.
Shouts get a different treatment, are displayed differently, so it's easy to see the difference. Maybe different types of object could be better differenciated if the layout of their editors and viewers were different. And my candid impression (as a newbie) is that there are too many concepts side by side.
Another comment on shouts is that I see no Delete button. I think that's more important than Edit, particularly as they are supposed to be short and spontaneous. I think it's more a matter of "oops i shouldn't have said that" than "i want to phrase that a little differently".
og_autogroups and og_mandatory_group modules
I found a bit annoying that to post anything the user must (a) register, (b) join a group.
So I created a default group and installed og_autogroups and og_mandatory_group modules.
Now new users are joined the default group automatically and all posts go to this group, so users don't even need to know anything about the group.
Only if user wants to create a group - he can do so.
HobbyBlob.com
Suggest these modules are included in dc
I think these modules should be included as part of the normal dc install. I would have thought that most sites would want to have a group that all users would belong to and where information relevant to all site users could be presented.
Discussion vs Forum
Jay, any reason inventing 'Discussion' content type instead of using 'Forum' familiar to everybody?
It's the drupal way
Alex -
Most of drupal.org functions using discussion pages (instead of Forums), so it's kind of the drupal way...
Our assumption is that Groups - especially when we can provide a hierarchy of them - serves the same role as topic groups in Forums. Plus, Forums are big mounds of additional software, and we're trying to keep Commons on a diet (to make sure it remains downloadable in a reasonable size).
I think there's enough community evidence suggesting that Forums would be nice to have, though I'm not sure Acquia's motivated to do the integration. There have been several people in the community who have tried different versions of Drupal Forums, with varying success. I think once one settles down, somebody somewhere will create a Feature out of it, and make it available to Commons users. I'm guessing, anyway...
Thanks Jay for the
Thanks Jay for the explanation.
Excellent!
Thanks for providing this Jay! Very helpful!
It should be a sticky on the front page.