You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The technical writing handbook is our go-to for everything from our style guide to our processes. However, as it's grown it's become unwieldy in terms of structure.
What we need is fresh eyes on the handbook, which is here and feedback about:
How the content is organized
Whether the content is readable and accessible to multiple audiences
What's missing from the content
What's extraneous in the content
Whether there's duplicate content
Any and all feedback is welcome and you're encouraged to make whatever changes you see fit. Once the PR is open, you'll have full access to the docs team for support and assistance.
Questions? You can find us at the DWG channel on our community server.
The text was updated successfully, but these errors were encountered:
The technical writing handbook is our go-to for everything from our style guide to our processes. However, as it's grown it's become unwieldy in terms of structure.
What we need is fresh eyes on the handbook, which is here and feedback about:
Any and all feedback is welcome and you're encouraged to make whatever changes you see fit. Once the PR is open, you'll have full access to the docs team for support and assistance.
Questions? You can find us at the DWG channel on our community server.
The text was updated successfully, but these errors were encountered: