Rethink approach to VAMC Featured Stories

dsinla commented 1 year ago

Value to Veterans

As a Veteran, I have access to important stories and announcements about my VA health care system/facility As a PAO, I need an intuitive interface for sharing important stories and announcements to the Veteran population my health care system serves.

Headlines

Business stakeholders: VHA OCTO owner: Michelle Middaugh

Is request tracked to an event or Congressional deadline? No

Description

The original VAMC system homepage page design included 2 featured stories (and 2 events). An editor working in CMS sees no evidence to the contrary. The UX allows editors to pick the order of featured stories but their selection seemingly has no effect on the FE. Currently, only one story can be featured and marking more than one to be featured may result in no featured story.

User stories

As a VAMC CMS Content Editor, I would like to be able to mark two Stories as Features (1st and 2nd) so that the stories appear in the specified order (1st and 2nd) at the top of the page.

Background

In May 2023, it was determined that the existing mechanism for featuring Stories and Events will be deprecated: #1318. Facilities will envision alternatives, for Stories only.
See additional information in Improve the logic and functionality used by the "featured" fields on Stories #1317
- Ethan Teague wrote / merged front-end code in department-of-veterans-affairs/content-build#680 to partially address this issue.
- CMS code to make changes was written & is in closed PR #6766.

Considerations

Options are well documented in [CONSIDER] New possibilities for Featured Stories #13695
If we're going to support 2 featured stories
- When you create a 2nd featured story, what should happen to first featured story?
- If we do intend to support 2 features. then if you already have two featured stories, and create a new featured story, how do we decide which of the first two to eliminate? How to expose to editor and have them decide?
This is similar to events, but events expire and if there's no featured event, we display the next chronological event

Deprecate "featured" UX and combined workflow for stories and events #1318
Feature function for Story content types only allows one Featured story #11221
- see comprehensive history from @jilladams in comment
Remove Featured field order from featured fieldset #13688
Editorial experience: URL creation for Stories/News Releases #13905
VAMC event, story, and news release pagination is not announced properly #12089

Tasks

Discovery for editorial experience framed in [DISCOVERY] Editorial process: Story content #13914

dsinla commented 1 year ago

Suggest tackling this in Q1 2023 Get more data, link to support tickets? what is this impact?

kmariepat-cityfriends commented 1 year ago

Some context:

[ ] ??? should we fix this approach overall for stories... the 1 and 2 in CMS don't do anything, disconnect bet
[ ] Featured should be on the place you want to feature it, that lets you select what story you want to feature. Having featured be part of the event is backwards from where the decision is (leadership list is an example of right relationship with items on the list and how it is set)
[ ] Entity queue is one solution that was proposed

kmariepat-cityfriends commented 1 year ago

Some context:

[ ] ??? should we fix this approach overall for stories... the 1 and 2 in CMS don't do anything, disconnect bet
[ ] Featured should be on the place you want to feature it, that lets you select what story you want to feature. Having featured be part of the event is backwards from where the decision is (leadership list is an example of right relationship with items on the list and how it is set)
[ ] Entity queue is one solution that was proposed

mmiddaugh commented 11 months ago

As mentioned above, the leadership list may be a good model for this reboot...essentially, the story could be created in a separate workflow from the one in which they are featured and ordered. In this way, the editor would have context and visibility into which and how many stories were selected to be featured and in what order.

mmiddaugh commented 7 months ago

Update 3.9.2024

This is still high value work which we have not been able to prioritize due to team capacity and other competing priorities, including legislative requirements. May revisit in 2Q or 3Q 2024

mmiddaugh commented 5 months ago

Given the need to devote capacity to aligning with USWDS Design system and other competing priorities, I'm deprioritizing this work. We'll revisit in Q324

mmiddaugh commented 4 months ago

Update 6.7.2024

Still on hold

mmiddaugh commented 2 months ago

Update 8.8.2024

KB articles have been updated to reflect existing functionality
Adjust misleading Featured stories help text #18819 will be prioritized in the short term
All other work on hold

mmiddaugh commented 1 month ago

Update 9.3.2024

Adjust misleading Featured stories help text https://github.com/department-of-veterans-affairs/va.gov-cms/issues/18819 will be prioritized in the short term
All other work on hold

department-of-veterans-affairs / va.gov-cms