-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedback on Writing/Content Guidelines #364
Comments
did we ever give you feedback on this? |
Not yet! But I would love feedback from Design on this. Actually, I'd be glad to meet with Design soon to talk about this and the Questions for some feedback and input if possible. Maybe in 2 weeks or so? |
@Andan-Eddy is going to make new issues for each person who has not provided feedback and then link to those issues in the top of this issue, so that we can track progress. |
I assigned this is issue to just daisy @daisyyiudesign can you also share this with Cherry to get her feedback |
Checking with Sam to see if feedback is needed from Design |
Never received feedback from design. Closing this issue because it's super old now and we've moved passed this. Assigned the label back to Design as it was an issue for Design, not for Content. |
Overview
The Content team has created writing, tone, voice, and style guidelines for writing on the Expunge Assist app. This is so that anyone who writes copy for the app have resources to keep the copy consistent for the user.
We are looking for any feedback, thoughts, and discussion you may have before we finalize them (they will be updated periodically).
Action Items
Resources/Instructions
Guidelines
The text was updated successfully, but these errors were encountered: