evergreen-docs:dig_style_guide
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
evergreen-docs:dig_style_guide [2021/05/28 14:36] – aneiman | evergreen-docs:dig_style_guide [2023/06/01 12:22] (current) – update branch name from master to main gmcharlton | ||
---|---|---|---|
Line 67: | Line 67: | ||
===== General ===== | ===== General ===== | ||
* **Avoid changing section titles**. These are used to auto-generate anchor tags which are often used for links. Change with care, and check for links in other docs. | * **Avoid changing section titles**. These are used to auto-generate anchor tags which are often used for links. Change with care, and check for links in other docs. | ||
- | * Always **review changes** before committing to master | + | * Always **review changes** before committing to main (and check the updated web page the next day to make sure it worked right). |
- | * Always use **spell-check** on new content (including when porting old docs into master). | + | * Always use **spell-check** on new content (including when porting old docs into main). |
* AsciiDoc code lines should be 80 characters long or shorter. (Occasionally, | * AsciiDoc code lines should be 80 characters long or shorter. (Occasionally, | ||
* Screenshots should be smaller than 1050 pixels wide (when possible). | * Screenshots should be smaller than 1050 pixels wide (when possible). | ||
+ | * Rather than recreating documentation text in multiple adoc files, instead link directly to the main adoc for the feature. | ||
===== Formatting ===== | ===== Formatting ===== | ||
==== Headers ==== | ==== Headers ==== | ||
Line 107: | Line 108: | ||
* This allows AsciiDoc to auto-number the items as needed. | * This allows AsciiDoc to auto-number the items as needed. | ||
* **Ampersands** should be left as is (&). Don't use an HTML entity (which ironically causes errors in our HTML generator). | * **Ampersands** should be left as is (&). Don't use an HTML entity (which ironically causes errors in our HTML generator). | ||
+ | * If an ampersand appears in the staff client or OPAC use the ampersand in the documentation. | ||
* Any **code and command line commands** should be marked as +code+ or `code` | * Any **code and command line commands** should be marked as +code+ or `code` | ||
* If the code or command is hard to read when included in the paragraph, consider using a code block: | * If the code or command is hard to read when included in the paragraph, consider using a code block: | ||
Line 185: | Line 187: | ||
* **Don' | * **Don' | ||
* **When replacing a screenshot**, | * **When replacing a screenshot**, | ||
- | * Image syntax: '' | + | * Image syntax: '' |
+ | * Alt text: Please remember to include alt text in the image syntax | ||
* Screen shots can be from any installation of Evergreen, as long as it does not contain any personal identifiable information, | * Screen shots can be from any installation of Evergreen, as long as it does not contain any personal identifiable information, | ||
===== Common Mistakes ===== | ===== Common Mistakes ===== |
evergreen-docs/dig_style_guide.1622226984.txt.gz · Last modified: 2022/02/10 13:34 (external edit)