Telligent Community does an awesome job of providing you with blogs, discussion forums, media galleries, and wikis. But it has limited support for letting you enter your own content that doesn't fit within those paradigms. Historically, Telligent Community has provided content parts, but the content within those controls could never be searched or versioned.
Wikis go a long way towards letting you enter custom content into your community, but they have several limitations. There's no workflow built around wikis and you cannot control the layout, from a widget point of view, for individual wiki pages. You're also limited in your ability to construct custom URLs.
Scribus addresses the limitations of content parts and wikis.
Scribus has CMS Sections, which are analagous to weblogs and discussion forums. You can create any number of CMS sections. You add CMS sections to groups just like you do weblogs and other standard Telligent Community applications.
Within a CMS section, you can create one or more CMS pages. For any given CMS page, you can set the page layout and add widgets to the page, just like you would any other Telligent Community page.
You can add CMS widgets such as a CMS content area or comment widget, as well as any of the widgets included with Telligent Community. You may also add your own custom widgets to any region of the page.
You enter your customer content into CMS content widgets. A CMS page may have one or more content widgets.
Scribus extends the Telligent Community search provider, indexing every content widget on every CMS page. When you search for keywords, the standard search results page will include CMS pages containing content that matches your search keywords.
You may also add tags to CMS pages. The tags are inserted into the meta tags of the rendered page. The tags may also be included in tag clouds within the community.
Scribus participates in the Telligent Evolution security model. You may identify staff members as content editors, content publishers, and content administrators. Content editors create content but cannot publish it for consumption. Content publishers review and edit the work of content publishers, publishing the CMS pages to the front end of the website once they are ready. Content administrators may do the work of editors and publishers, but they also have administrative rights and capabilities for CMS sections and pages.
As your team constructs content pages, Scribus tracks what happens to the pages. It maintains an audit log of each action taken by your staff and maintains a version history of each page.
Read more about Content Roles or Permissions
You may set a custom URL for any CMS page. The URL is relative to the group containing the CMS section. You may change the URL from version to version as you see fit. For example, version 1 of the About page could be at [site root]\aboutus.aspx. In version 2, you could change it to [site root]\about.aspx.
You can construct CMS pages that contain a mix of static and dynamic content. It's easy enough to deliver dynamic content through the use of standard or custom widgets. However, if you need to insert dynamic content into your static content (e.g., hours of operation for a restaurant) then you can make use of Scribus code blocks. If you're an ASP.NET developer, think of code blocks as ASP.NET user controls. Any user control that you write can be turned into a code block and embedded into the content area of a CMS page.
Read more about Code Blocks
Scribus lets you set a start date and/or end date for each CMS page. For example, if you have seasonal content then you can schedule the page to appear at the start of the season and disappear at the end of the season.
These features fill a gap in the Telligent Community platform, giving you the flexibility to include content as you see fit.