Decide and document how technical writers can contribute to Pajamas
How technical writers can contribute to Pajamas:
Ongoing
- Review all MRs impacting the Content section
- Raise MRs impacting the Content section
- During product development when consulted by Product Designer
- Rename #docs-style to #content-style, to be used for both Documentation Style Guide and Pajamas > Content discussion; perhaps also for https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#blog-style-guide
One-off initiatives
- Comparison of Pajamas Content section with Documentation Style Guide (in progress gitlab-org/gitlab-services/design.gitlab.com#472 (closed))
- For conflicting styles, clarify whether there should be a difference in the UI vs docs, or they should be aligned.
- Determine and implement a format for the style guides to cross-link or otherwise reflect ongoing alignment.
- Audits of UI text, documenting decisions in Pajamas.
- Add review of Pajamas Content section to Technical Writer onboarding.
Edited by Mike Lewis