Slide 1

Slide 1 text

Cynthia Ng @arty-chan May 8, 2023 Write the Docs Portland Docs as Code: Automation the Developer way

Slide 2

Slide 2 text

File:Tanuki in Higashiyama Zoo - 2.jpg. (2022, November 29). Wikimedia Commons. Retrieved 22:49, April 14, 2023 from https://commons.wikimedia.org/w/index.php?title=File:Tanuki_in_Higashiyama_Zoo_-_2.jpg CC-BY-SA 4.0 International

Slide 3

Slide 3 text

For more about making your ideas stick with others, check out our book! Docs as Code

Slide 4

Slide 4 text

“Documentation as Code (Docs as Code) refers to a philosophy that you should be writing documentation with the same tools as code [and using] the same workflows as development teams”. - Write the Docs https://www.writethedocs.org/guide/docs-as-code/

Slide 5

Slide 5 text

The Flow Docs with Development Part of the “definition of done”. New content for features and updates for bugs. Automated Checks Metadata Formatting: markdownlint Style guide: Vale Accessibility Reading level Repository + Changes Get a copy. Make changes to Markdown files. Commit changes. Issue Feature or bug. Code, docs, or both. Review Include Technical Writer. Merge Publish

Slide 6

Slide 6 text

For more about making your ideas stick with others, check out our book! Automated Checks

Slide 7

Slide 7 text

Docs Pipeline

Slide 8

Slide 8 text

The Pipeline Jobs (Part 1) UI Links Checks for broken links to docs from the product. Links Checks for broken internal links and anchors. Danger review Checks for adherence to review process. Such as: - Add Technical Writer for docs. https://docs.gitlab.com/ee/development/documentation/testing.html

Slide 9

Slide 9 text

The Pipeline Jobs (Part 2) markdownlint + Vale Checks adherence to style guide. Fails on rule violation or “error”. Such as: - Lists - Future tense “Code” Quality Report on content that triggered a “warning”. Such as: - Word choice - Spelling Accessibility Integrated into other jobs. Such as: - Heading structure - Reading level https://docs.gitlab.com/ee/development/documentation/testing.html

Slide 10

Slide 10 text

Example Report

Slide 11

Slide 11 text

Example Warning

Slide 12

Slide 12 text

Benefits ● Consistency ● Less human errors ● Efficiency ● Increased self-service ● Improved feedback cycle ● Familiarity ● Reusability with other projects ● and all the other benefits from automated testing!

Slide 13

Slide 13 text

For more about making your ideas stick with others, check out our book! Thank you Cynthia Ng Arty-chan@Slack TheRealArty@Twitter [email protected]