Use templates

• When starting work on a new bug or request, create a child page under the Bug Documentation or Requested Updates/Development Documentation “parent” pages. In the new page, select the correct template and fill in the table at the top. Continue to add notes and other documentation underneath the table.

  • Both the Request Documentation and Bug Documentation templates have built-in tags and page properties that drive the tables on each “parent” page.

  • Make sure to “publish” the page and don’t leave it as a draft, as it will not appear in the table.

• in order to update a page that was created before 2/22/2024

  1. Open one of the pages that already has the page properties embedded and copy the table

  2. open the page you want to fix in edit mode

  3. at the top (or somewhere, technically doesn't happen to be at the top) type /page properties to get the widget thing

  4. paste the table into the widget [note that depending on what you get when you copy the table, you may be able to paste the page properties widget itself and skip these two steps].

  5. edit the table column with that project's details, but don't change the left-hand column (that's where the headers for the summary macro come from)

  6. save/publish the new version of the page

  7. add a tag to the page for either slate-bug or slate-request

Status codes: (/status)

• green = COMPLETE

• yellow = ON HOLD

• red =  IN PROGRESS

• blue = PENDING

Close project/Archive old pages

• Once the page for a project (either bug or request) is complete, it should be moved to the (Closed) version of the parent page.

  • You can either drag and drop from the side-bar content menu or use the tool within the page to “Move” it.

  • After it is moved so that it is no longer a “child” page of the main “parent” page, it will no longer be listed in the page properties report in the (Closed) “parent” page.