-
Notifications
You must be signed in to change notification settings - Fork 154
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
What's New: Add new recent content items to updated page #2989
Comments
This can be a one-time task to get information published. We will have a more consistent cadence with What's new content going forward. Note: I indicated this is as part of monthly call for Dec., but not sure if that's needed. |
Updated the draft. This is ready for review and edits to add to the What's New page. @annepetersen , tagging you to review. |
suggestions/changes in |
Discussed with Dan today. I'm going to create PR to add the items from the doc. He and Anne will review this round to make sure everything's making sense. We'll likely change process going forward. |
Created branch but need to work with Amy L on how to update. Will do on 1/8. https://github.com/uswds/uswds-site/tree/kf-WhatsNew-24updates/pages/whats-new |
Amy and I collaborated on corrections to filenames, how to add colons to titles, etc. Amy L going to work on fixing issue with title linking to its own page when there is no link. This is still in progress but she's going to work on it tonight. |
Problem
Once What's New is updated and live, it will still have outdated content from two years ago and older. It needs refreshed information.
Solution
Use information from the last two monthly calls and newsletters (November and October) to create new posts for the page.
Since the content already exists in monthly call transcripts and newsletters, this will not need intensive FFR, just a standard review and merge by one fed approver.
Reference:
November items drafted here
December items drafted here 1/6 - will also need review
Will be closed by #3056
The text was updated successfully, but these errors were encountered: