Audit Product PAL assets Components vs Patterns

[oliviaflory]

Audit the PAL assets against the definition of Component and Pattern that we established in the pre-work for the workshop.

• [x] Revisit the Schema and how we define things there
• [x] Revisit the component vs pattern qualifiers from the workshop pre-work
• [x] Create a quick write up of component vs pattern qualifiers
• [x] Create audit in Airtable: duplicate and work off of existing airtable and Product site audit.
• [ ] After the audit we need to refine our opinion of what needs to change. We will keep components and patterns separate in our IA but need to reduce the number of patterns.

[aubrey-oneal]

Note that we can consider this for a future workstream: Discuss the idea of having example code for patterns (showing several permutations of filter pattern). How would this impact IA in website and Storybook? How feasible is this?

[oliviaflory]

Review Notes May 15

Met with: Linda, Jeannie, Carrie, Elysia, Scott, Taylor, Tracey, Aubrey, Olivia

Reviewed Olivia's progress on Component and Pattern definition and audit, see Figma file

Feedback

• Component definition is most clear
• The challenge has now shifted from component vs pattern to pattern vs flow or template
• Need to get crisp on the definition of pattern, flow and templates
• Split between Option 1 (two categories) and Option 2 (4 categories) – see figma for details

Next steps

• Iterate on the definitions
• Iterate on the list of patterns/flows again to see if we can move any more
• Answer: how would we handle flows or templates that are not PLG
• Explore if a recipe checklist on the overview pages would help
• Do some testing with our community