Bug 812701 - RFE: Inject pre-reqs into <procedure> rather than <section>
Summary: RFE: Inject pre-reqs into <procedure> rather than <section>
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.x
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Lee Newson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-16 02:26 UTC by Joshua Wulf
Modified: 2014-10-19 23:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-29 02:15:57 UTC


Attachments (Terms of Use)

Description Joshua Wulf 2012-04-16 02:26:33 UTC
Ideally Task prerequisites should be injected into the task before the first step, rather than at the top of the topic.

For example - instead of this (current output):

-----------begin current output of topic 7677-------------------

Prerequisites:

    Chapter 3, Install the Content Spec Processor Client
    Chapter 4, Configure the Content Spec Processor Client 

If you are reading a published version of this guide, you may not be reading the very latest content. You can get the very latest build of this Guide by installing and configuring the Content Spec Processor client, and then building this guide from its content specification with all the latest topic content.

Procedure 1.1. Obtain the latest copy of this book

  1.  Install and configure the Content Spec Processor client.
  2.  Check out the Content Spec for this book with the command:

    csprocessor checkout 7210

  3.  Change into the newly created project directory for this book.
  4.  Build and open in a browser:

    csprocessor preview

-----------being current output of topic 7677-------------------

What makes more sense is this:

-----------begin current output of topic 7677-------------------

If you are reading a published version of this guide, you may not be reading the very latest content. You can get the very latest build of this Guide by installing and configuring the Content Spec Processor client, and then building this guide from its content specification with all the latest topic content.

Procedure 1.1. Obtain the latest copy of this book

  Prerequisites:

    Chapter 3, Install the Content Spec Processor Client
    Chapter 4, Configure the Content Spec Processor Client 

  1.  Install and configure the Content Spec Processor client.
  2.  Check out the Content Spec for this book with the command:

    csprocessor checkout 7210

  3.  Change into the newly created project directory for this book.
  4.  Build and open in a browser:

    csprocessor preview

-----------being current output of topic 7677-------------------

So prerequisites would inject into procedure, after the <title> (if one is present):

<procedure>
 <title>Some title</title>
 
 [inject Pre-reqs here]

 <step>
  ....
</procedure>

The procedure <title> is optional, so it may not be present.

Comment 1 Misty Stanley-Jones 2013-05-29 02:15:57 UTC
This is up for debate and not actually a CCMS issue. I actually don't think this should be the default behavior. Let's discuss it and reopen this if necessary.


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