Skip to content
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

[Aging Content] Create an editor-facing KB article for Aging Content Notifications #18006

Open
3 tasks
Tracked by #17975 ...
FranECross opened this issue Apr 30, 2024 · 3 comments
Open
3 tasks
Tracked by #17975 ...
Assignees
Labels
Aging Content Notifications Aging Content notifications & archiving Drupal engineering CMS team practice area Public Websites Scrum team in the Sitewide crew

Comments

@FranECross
Copy link

FranECross commented Apr 30, 2024

Description

As part of the Aging Content launch plan, we need to have a KB article written that is editor-facing explaining to them what they should expect when it gets close to their content's expiration date.

User story

AS AN editor who publishes content (e.g. full-width alerts/banners, blocks, etc.),
I WANT to be able to reference a KB article to learn how aging content notifications work
SO THAT I'm not confused when I start receiving aging content notifications about my published content.

Engineering notes / background

Analytics considerations

Quality / testing notes

Acceptance criteria

  • KB article written (possibly by Fran in collaboration with Daniel)
  • Reviewed by Daniel/Fran
  • Collaboration with Laura on KB article things

Noting here that Erika has approved the KB article being reviewed at the team level at this time. She would like us to consult the CMS Content Style Guide and VA Style Guide as references for how you choose to write and update. Although each of these resources are not specific to KB articles, the CMS team will be using them to create our KB template and guidance down the road. They are revamping KB article publication processes, and CMS review/approval is not needed in this particular instance. Slack thread here. cc @jilladams @dsasser

@FranECross FranECross added Aging Content Notifications Aging Content notifications & archiving Needs refining Issue status Public Websites Scrum team in the Sitewide crew labels Apr 30, 2024
@FranECross FranECross added the Drupal engineering CMS team practice area label Apr 30, 2024
@dsasser
Copy link
Contributor

dsasser commented May 1, 2024

@FranECross I'm going to point high here, since I think there will be some collab needed here in order to knowledge transfer.

@FranECross
Copy link
Author

@FranECross Connect with Erika and ask that the support team reviews before we publish.

@dsasser dsasser self-assigned this May 16, 2024
@dsasser
Copy link
Contributor

dsasser commented May 24, 2024

Update 5/24/24

Work has not yet begun due to sprint priority work taking priority. This may roll over as we have a holiday Monday, but not quite in the 🔴 status just yet.

@FranECross FranECross self-assigned this May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Aging Content Notifications Aging Content notifications & archiving Drupal engineering CMS team practice area Public Websites Scrum team in the Sitewide crew
Projects
None yet
Development

No branches or pull requests

2 participants