Midpoint Review - Content Feedback - Education Data Migration, Yellow Ribbon Tool

[KKitagawa-Bosch]

Next Steps for the VFS team

How did this touchpoint go? Give feedback on the Collaboration Cycle at any time.

• Assign this ticket to the team member(s) responsible for addressing feedback provided by Platform.
• Comment on this ticket:
  • If the Platform reviewer has any Thoughts/Questions that require responses.
  • When Must feedback has been incorporated. As appropriate, link to any other GitHub issues or PRs related to this feedback.
  • When Should/Consider feedback has been incorporated, or if any feedback will not be addressed. As appropriate, link to any other GitHub issues or PRs related to this feedback.
• Questions? For the most timely response, comment on Slack in your team channel tagging @platform-governance-team-members.
• Close the ticket when all feedback has been addressed.

Thoughts/questions

Feedback

Practice areas will document their feedback on the VFS-provided artifacts following the Must, Should, and Consider Framework. Platform Governance reviewers may also provide additional notes that don’t comment on the artifacts themselves but are important for implementation (eg. engineering/coding notes).

• Must: always use active voice. Currently the first sentence ("the yellow ribbon program can be paid towards...") is in passive voice
• Must: follow AP Stylebook guidance on capitalization after colons. The first word after a colon should only be capitalized if it is a proper noun or the beginning of a complete sentence.
• Should: under "what to know about the content displayed below" I would recommend bolding the labels for clarity. These are functionally label/value pairs so they fall under the bold text guidance in VADS in my opinion
• Consider: rephrasing "number of students remaining to receive funding." It's not fully clear what the subject/object relationship is in this phrasing.
• Consider: doing one more pass for plain language. I know this is complex information and mostly being read by folks who are already a bit "inside baseball" so to speak, but anything you can do to shorten sentences and simplify language is valuable!

Governance team actions

• Format feedback as individual tasks (check boxes)
• Assign this ticket to the VFS team member that opened the Slack request
• Add the VFS team product label
• Add the VFS team the feature label (if applicable)
• Add the touchpoint labels
• Add the practice area labels
• Add the Collaboration Cycle initiative milestone