Bug 1088056 - [RFE] Support the ability to create topic groups
Summary: [RFE] Support the ability to create topic groups
Keywords:
Status: CLOSED DUPLICATE of bug 752710
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CCMS-Core
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: pressgang-ccms-dev
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-16 00:00 UTC by Don Domingo
Modified: 2014-04-16 00:50 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-16 00:50:52 UTC
Embargoed:


Attachments (Terms of Use)

Description Don Domingo 2014-04-16 00:00:09 UTC
Description of problem:

In many cases, some groups of topics work well together to form a cohesive narrative. For example, a chapter on "SSL setup" can be composed of several topics:

* overview of SSL
* creating the SSL database
* choosing a certificate type
  * using a self-signed certificate
  * using a certificate signed by a CA

This chapter can be shared between multiple Content Specs, but only by adding the individual topics that make up the chapter. Most Config Refs and Admin Guides that require encryption instructions will likely need such a chapter.

However, as the number of Content Specs that use this group of chapters grow, editing the structure of the chapter (e.g. adding a topic, deleting  a topic) becomes more difficult. If changing the narrative of "SSL setup" requires the addition of a topic, say "using an unsigned certificate", that topic has to be added to ALL the other Content Specs where the "SSL setup" narrative is used.

To address this dilemma, other CMSs use "Topic Groups". This allows you to specify multiple topics as a unit, which can then be plugged into multiple TOCs or Content Specs. As a result, any fundamental changes to the structure of the group can be single-sourced.

I'd imagine that such a group can be created as a mini-Content Spec in PressGang, and then specified into a Content Spec later on?

Comment 1 Lee Newson 2014-04-16 00:50:52 UTC

*** This bug has been marked as a duplicate of bug 752710 ***


Note You need to log in before you can comment on or make changes to this bug.