"Before you start" (aka eligibility filter) for KB articles, featured content component

[kevwalsh]

User Story or Problem Statement

As a KB article, i know if the article is for me or not.

KB design (ignore the white box, just the blue box here)  VA.gov benefits page 

Acceptance Criteria

• [ ] Copy config from page content type (Benefits Hub page) for field_featured, a pretty flexible paragraphs field.
• [ ] Theme the field like on va.gov (alert background only component)

Implementation steps

## Design principles Which [CMS design principle](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/cms/cms-product-design-principles.md) is at play? - [ ] Purpose-driven: Creates an opportunity to involve the editor community in VA’s mission and content strategy goals. - [ ] Efficient: Removes distractions and create clear, straightforward paths to get the job done. - [ ] Approachable: Offers friendly guidance over authoritative instruction. - [ ] Consistent: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks. - [ ] Empowering: Provide clear information to help editors make decisions about their work. ### CMS Team Please leave only the team that will do this work selected. If you're not sure, it's fine to leave both selected. - [x] `Core Application Team` - [x] `Product Support Team`

[EWashb]

This may be a bit too advanced of a solution for now. Enhancements for KB could start with landing pages by product.

[EWashb]

Per the KB research completed on 2/13/24, the indication of who an article applies to in the above mockup could provide a useful mental model for users. I will keep this open only as a reference for redesign @gracekretschmer-metrostar. However, pieces of this may no longer apply to our path forward and we might consider creating new tickets with proper references.