You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

A page to demonstration what JOC's documentation might look like if within CU Confluence using specific conventions particular to Confluence.

See also

  • Add a link to A&S JAMF Pro change log, if not here.
    • Perhaps in A&S IT's SharePoint instance?

Conventions used here or proposed

  • Every page has a brief page description. These are visible to any page above.
  • Pages are created (and possibly moved around) to ensure a rationale hierarchy.
  • Pages higher in the hierarchy dedicate more space to describing sub-pages via "Children Display" code (think "branches"). And pages lower in the hierarchy have more detailed info (think "leaves").
  • A search box can quickly find any content, assuming we have a dedicated Confluence space.
  • Shared URLs within the site use Confluence's linking.
  • URLS shared outside of Confluence are always the smaller ones, not the ones from the Address bar.

Sub-pages

The following is a list of automagically generated list of pages under this top-level page, along with brief content descriptions.

 

  • No labels