-
Notifications
You must be signed in to change notification settings - Fork 18
Workflow: Questions and Tasks
Amanda Costello edited this page May 24, 2019
·
3 revisions
Follow this workflow to answer questions about and do work on site content. You might be able to skip some of the questions based on the nature of the content and scope of change, but all of them are worth a run-through!
Plan → Create → Revise → Approve → Test → Publish
- Does this content already exist, and in what format?
- How does adding/changing this content solve a problem for the users?
- How does adding/changing this content fit in with OIRA/OMB goals?
- Is pra.digital.gov the best place for this content to live?
- Does this connect to other content? Some places to check with:
- OMB Comms & OGC
- Digital.gov team
- WH Digital Strategy
- Create GitHub issue to track conversation around the content.
- Conduct research/review to further define the problem. Interview users and subject matter experts.
- How does this content fit into the information architecture (IA, or organization/navigation) of the site?
- What can the user do with the content?
- Review the IA and determine where the content will go.
- Outline the content based on the call to action/user outcome.
- Write in plain language, using short sentences and frequent headers to improve readability
- Who can edit this for subject matter accuracy and clarity?
- Who can edit this for plain language, usable structure, and accessibility?
- Who can edit this for legal accuracy?
- Set revision schedule, including deadline.
- Track revision history and dates in GitHub issue.
- Put final content into GitHub.
- Who approves this content to go into production (GitHub)
- Who needs to be informed that it’s moving forward?
- Determine content approver.
- Set approval timeline and deadlines.
- Assign GitHub pull request to OIRA approver and digital.gov staff
- Does this content solve the user’s problem?
- Are new issues present now that this content is part of pra.digital.gov
- Usability testing appropriate to the content.
- Document issues in GitHub, including creating new ones for observed issues or questions.
- Assign GitHub issues after they’re entered.
- Who will work with the digital.gov team for publication?
- Do other groups need to know about publication, or does it need to sync to other content?
- Close OIRA workflow and tag digital.gov team for squash and merge.
- Follow up with groups outside of OIRA as necessary, including:
- OMB Comms & OGC
- Digital.gov team
- WH Digital Strategy