How SAPAA finalizes a web page and maintains them.
Overview
Birth of a Web Page
Web pages move through a defined life cycle and are tracked via the SAPAA-MasterArea Spreadsheet. Within this file are the following status which have the indicated actions and responsibilities.
| Web-Status | Description | Who Is Responsible |
| a.File | Legacy PDF File | Frank |
| b.Next-Page | Next Page to create | Frank |
| c.In-Progress | Page in progressed, not WP published; can be found in the Drafts. The title should include [tbd]. | Frank |
| o.Built-Page | WP Publ. and in editing. The title should be updated from [tbd] to [name], e.g. [Hubert]. | Patsy/Hubert |
| p.Published | WP Publ. page linked and file unlinked. Patsy and Hubert sets the status in the Google Sheet in p.Published. Patsy and Hubert remove the [Name] reference. Frank updates the page’s Order value. | Frank, initially Patsy and Hubert |
| y.Issue | Issue with the site (see comments in the Google Sheet) | All |
| zOther | Other | Frank |
A note on the term ‘published’. In WordPress, published means the page has moved from a drafting state to being accessible on the website. In SAPAA, a published page has two requirements. Firstly, it is published in WordPress and secondly it is linked to the List of Protected Areas. By doing this, SAPAA is able to share ‘final-draft’ web pages without disconnecting the legacy pdf file.
Responsibilities for a Web Page
The webmaster is accountable for all web pages. The person will ensure consistency and adherence to general guidelines such as the Style Guides. The webmaster is also responsible for the initial ‘rough and ready’ build of new web pages. The web project team (currently Patsy and Hubert) are responsible for the final editing of a page and the approval via a silence procedure.
Webpage Ordering
By default, all new protected area web pages have an order number of ‘999’. This is the sequence they are displayed under the protected area listing (in ascending order). When published, 999 is replaced with the order found in List of Protected Areas. The Webmaster performs these activities.
Silence Procedure
The silence procedure provides the final check of a web page. It is meant as both an approval process but also a final peer review by the SAPAA board. The board has delegated authority to the web project team and so unless an objection, question or comment is raised, approval is assumed.
Email Draft
Sent to the core board members. Currently Hubert, Patsy, Frank, Judith, Krystin, Chris and Linda.
Subject: [AREA] – Approval via Silence Procedure – [DATE (Today + 7 days)] 4pm
Body:
Dear SAPAA board,
The web committee endorses the following Natural Area be promoted from a pdf file to web page. If you agree, do nothing. If you have comments, thoughts or suggestions feel free to reply all or contact [names] directly. This page will be linked to the List of Protected Areas next Friday ([DATE (Today + 7 days), 4pm) notwithstanding any comments.
[LINK to the Natural Area Webpage]
[Link is available from from the Pages-page: ellipse, copy link]
Web Page Updates
Comments and suggestions to improve a web page are welcome. The following provides a list of possible corrections and urgency in correction or how modified.
| Change | Urgency and How |
| Significant Error | Corrected as soon as possible particularly errors that increase the risk to SAPAA or members of the public. Correction done by web project team. |
| Blog or Newsletter Article | Added as time permits, typically in the further reading or references section of the page. |
| Comment on the Page | The comment is evaluated by the web project team and the update made based on the nature, urgency or relevance of the comment. |
SAPAA 