Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add topic(s) on DITA features used in docs #50

Closed
4 of 5 tasks
infotexture opened this issue Jan 3, 2016 · 0 comments
Closed
4 of 5 tasks

Add topic(s) on DITA features used in docs #50

infotexture opened this issue Jan 3, 2016 · 0 comments
Assignees
@infotexture
Labels
backlog Issues from legacy project backlog (pre 2.0)
Projects
2.4 Release
Milestone
2.4

Comments

@infotexture
Copy link
Member

infotexture commented Jan 3, 2016 •
edited
Loading

The docs should be extended with a dedicated topic or set of topics that describes how the DITA-OT documentation uses certain DITA and DITA-OT features, such as:

  • profiling and filtering
  • keys and key references
  • subjectScheme classification for controlling available attributes
  • automatic generation of topic files based on the content of installed plug-ins
  • conref push to inject additional descriptions into generated topics for messages, parameters & extension points

Wherever possible, these topics should use <coderef> elements to link directly to live source files rather than copying code (see #49).
@infotexture infotexture added the backlog Issues from legacy project backlog (pre 2.0) label Jan 3, 2016
@infotexture infotexture mentioned this issue Mar 23, 2016
Closed
@infotexture infotexture added this to the 2.4 milestone Sep 13, 2016
@infotexture infotexture self-assigned this Nov 11, 2016
infotexture added a commit that referenced this issue Nov 12, 2016
@infotexture
Merge branch 'release/2.4'
9dce4a7 
* release/2.4: (125 commits)
  Re-use migration info on HTML5 & legacy plug-ins
  Split contribution info between core & docs
  Add topic on migrating to 2.4
  Add keys to migration map
  Link to new topic on DITA features used in docs
  Add topic on DITA features used in docs (Fixes #50)
  Increase stroke width, use $brand-primary color
  Normalize parameter tagging per coding guidelines
  Remove reference to obsolete command line tool
  Use new double-hyphen syntax in parameters intro
  Add “Extension points by plug-in” to docs updates
  List remaining issues resolved in v2.4
  Draft 2.4 Release Highlights
  Add IDs to facilitate re-use
  Update FOP version key & add FOP Release Notes keys
  Archive 2.3 Release Notes for posterity
  Bump 'release' & 'maintenance-version' keys to 2.4
  Omit path to dita command
  Fix line break in code block
  Update links to revised contribution information
  ...
infotexture added a commit that referenced this issue Nov 12, 2016
@infotexture
Merge branch 'release/2.4' into develop
28d2747 
* release/2.4:
  Re-use migration info on HTML5 & legacy plug-ins
  Split contribution info between core & docs
  Add topic on migrating to 2.4
  Add keys to migration map
  Link to new topic on DITA features used in docs
  Add topic on DITA features used in docs (Fixes #50)
  Increase stroke width, use $brand-primary color
  Normalize parameter tagging per coding guidelines
  Remove reference to obsolete command line tool
  Use new double-hyphen syntax in parameters intro
  Add “Extension points by plug-in” to docs updates
  List remaining issues resolved in v2.4
  Draft 2.4 Release Highlights
  Add IDs to facilitate re-use
  Update FOP version key & add FOP Release Notes keys
  Archive 2.3 Release Notes for posterity
  Bump 'release' & 'maintenance-version' keys to 2.4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@infotexture infotexture

Labels
backlog Issues from legacy project backlog (pre 2.0)
Projects
No open projects
2.4 Release
Done
Milestone
2.4
Development

No branches or pull requests
1 participant
@infotexture