* Handbook: Marketing page edits
* Marketing pass first iteration
* Handbook: adding community support to engineering
1st iteration
* Handbook:removing community support from marketing
1st iteration
* Handbook: new section for community support
* Handbook: Marketing second pass
Added sections with section links per team.
Ask @chris-mcgillicuddy if he wants to remove the style guide sections and editing sections on this page
Updating digital experience to brand - ask @eashaw for help with link redirects
TODO: Charlie: need to check the handbook links before merging.
* Consolidating style guide
Several sections of the handbook have their own styles guides with redundant content. I'm consolidating that content into one central location.
* Update README.md
* Update README.md
* Update README.md
* Merging Quality section with Engineering
I merged content from the Quality section of the handbook with Engineering. I added the ritual and slack channel DRIs from Quality to the Engineering tables.
* Delete README.md
- Changed the "Use workflow from" instructions per advice from @zwinnerman-fleetdm
- Added note that "main" is not a valid image name and the commit hash must be used instead.
* Codeowners: Reduce # of pings for reviews of docs
To avoid duplicative pings in Slack, reduce the number of folks who get automatically pinged about review requests when documentation, handbook, and website routes are changed.
I left Mike T and Chris both on the digital experience handbook so that PRs can be merged quickly there in many cases, regardless of timezone.
Also @chris-mcgillicuddy I made you responsible for either (a) approving and merging or (b) if there changes to meaning or code samples, requesting review from the on-call engineer.
* Update to reflect routing doc changes through Chris, and add sub-headings
* Pull the most relevant sentences to the top of each responsibility
* Use more peaceful language
* Website: add support for excludePageFromSectionIndex meta tag in Markdown content
* revert articles and docs changes
* move handbook pages into subfolders, rename brand to digital experience, update links
* update page script, add pages in same section to generated index
* remove newline
* add redirect for renamed handbook page (/handbook/brand -> /handbook/digital-experience)
* handbook: update relative page links
* update comment
* Update basic-handbook.page.js
* Revert .sailsrc change
* Update basic-handbook.ejs
* Update basic-handbook.page.js
* Update basic-handbook.page.js
* Update security.md
I added an example of how second-level sections could be introduced (linked to).
* update links on security.md, remove related pages
* change top level files filenames to README.md
* remove handbookSection
* Update basic-handbook.page.js
* only include top level pages in handbook index
* update relative links
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
