Instructions and memory jogs for how the SAPAA site is managed. Includes technical notes as well as a general style guide. This is broken into 3 sections: Protected Area Pages, other web pages (this guide), and other including blogs and images.
- Style Guide and Instructions
- Headers, Anchors and Page Length
- Subsequent Updates
- Punctuation and Writing Conventions
- System Administration
- General style guide
- Editing, Review and Silence Procedure
Style Guide and Instructions
This page is intended for SAPAA members who have access to the site to contribute content. Anyone can comment on a post or a page but you need to be logged in to write a post, update a page or contribute photos.
To log in, you must have a wordpress.com account and be invited to contribute to the site. To be invited, email: firstname.lastname@example.org.
SAPAA tries to keep non-core-content pages to a minimum. The following list of pages describes their purpose and who owns them. Pages contain stable content. Conversational or time sensitive content should go into the Newsletter or a blog.
Final editing is currently provided by Secretary.
- CSS and Font: The Standard Font size is Normal and black.
- URL Slug: Kept to about 25 characters or less, word press does not allow spaces (hyphens, etc.).
- Feature Image: not used.
- Excerpt: a short (<100 word) summary of the page; what is the page and be read.
- Comments: Visitors and subscribers can comment on all pages except for Home, Contact Us, Newsletters.
- Parent Page: set by the webmaster.
Use of Headings, Anchors and Page Length
- Headers should be used if the text is more than about half a printed page in length.
- A table of contents at the top of the page and anchors throughout are used if the page is more than about one printed page in length.
- Ideally web pages should be no more than about two total printed pages in length.
- A protected area page is the exception to the above length limit; see the protected area style guide for reference.
Unlike a printed page, web pages are meant to evolve over time as standards and content changes. The following guidance is provided to understand how changes are typically identified, whom makes the changes and what approvals are required.
Updating of ‘passed’ pages
- Changes Made by a Committee Member with no Notice
- WHO: Any web committee member makes changes and approves it.
- Corrections of errors that do not change the substance of page
- Spelling, grammar, style, changes to standards
- Minor technical changes
- Additions to further reading (e.g. newsletter, partner organizations).
- Content published in the SAPAA Newsletter.
- Changes Made by Members with Notice to the Committee
- WHO: Any web committee member and it is endorsed by the web committee without references or approval by the board.
- Articles published in relevant partner and peer organizations relating to a protected area.
- Unsolicited content from members, stewards and official sources (e.g. government).
- Changes in photos, significant changes in formats or standards.
- Changes made by the Committee, Re-Approval by the Board
- WHO: Web committee makes a change and seeks re-approval of the page from the board.
- WHAT: Changes that are contentious or create risk for the Association.
Provides an overview of SAPAA; owned by the President with suggestions from the executive.
Current executive of SAPAA; owned by the President with suggestions from the executive.
Historical listing of SAPAA newsletters. This page is owned by the Newsletter editor with changes acknowledged by the President and Webmaster.
Detailed descriptions of protected areas of interest to SAPAA; owned by the President with suggestions from the executive. As this content is central to SAPAA, it has its own specific style guide.
- Links within the site (e.g., page to page) should open in the same tab.
- External links (i.e., outside of the SAPAA site) should open in a new tab.
- Anchors, Page table of contents and “Return to Top” are used for lengthy pages (e.g., Protected Areas landing page).
SAPAA has 5 levels of system access:
- Public: anyone can access the public pages. Comments are allowed on select pages but are held for moderation (approval or deletion if deemed spam).
- Contributor: (not currently used), a SAPAA member. Able to write blog posts, upload photos but may not publish any content. An editor must approve/publish the content. Not able to edit pages. Must have minimum WordPress skills.
- Author: (not currently used), having contributor privileges but able to post their own content. Unable to change another user’s content. Not able to edit pages. Must possess basic WordPress skills.
- Editor: Has access to all posts and pages. Must possess good WordPress skills.
- Current Editors: Chris, Krystin, Patsy and Hubert.
- System Administrator: Full power over the site: can invite people, modify the site settings, etc. Must possess very good WordPress skills. Administrator: Frank
- Theme: Twenty Twelve.
- Default: All theme settings use the default settings.
- Blog Post Page: Home Page.
General Style Guide
- Use “and” instead of the ampersands (&) unless used as part of a title or name.
- Change “web site” to “website”
- Change “sub-region” to “subregion”
- Change by-law to bylaw
- Put a space between the number and km
- Are we going to capitalize the names of animals? Use lower case for plant names.
- Italicize all Latin names
- Capitalize “Natural Area”
- Place a period after the end of each reference.
- Include reference no. in square brackets within the sentence and follow by a period. Check that reference no. is included in the text.
- To represent plant communities, separate plants of different habit with a slash, thus white spruce/Pleurozium schreberi (moss) or white spruce/wild sarsaparilla, or white spruce/willow, but plants of the same habit are separated by a hyphen, e.g. aspen-balsam poplar.
- Make sure references are in numerical order in the text.
- In Further Reading, add newsletter references in reverse chronological order, i.e., latest first. In References, place newsletter in order in which refs appear in text.
Editing, Review and Silence Procedure
- FRANK: Publish page
- All components completed
- Validate statistics against sources
- Update order in page setting
- Change status in the Master spreadsheet to built.
- HUBERT/PATSY: Assign page for editing by update tbd in the Title
- Review for readability and alignment to SAPAA organizational reputation.
- Best available image
- Review for accuracy including:
- Correct map and site statistics
- Area size is correct
- Standards (e.g. use of hyphens, spelling, etc.)
- References are accessible and and notes match
- Review for formatting, e.g.: Centered captions, No empty blocks
- HUBERT/PATSY: Last walk through
- Any final discussion or notes
- Remove [name] from title
- HUBERT/PATSY: Send silence procedure email
- Natural Area spreadsheet
- Change the link from the file to the page
- Change the type designation from File to Page
- Master Spreadsheet
- Change status and insert date of silence procedure.
- Natural Area spreadsheet