Updates to grouped FAQs - #410
Conversation
🦋 Changeset detectedLatest commit: 63b7545 The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
🔍 Design token changes foundView CSS variable changes- --brand-FAQ-maxWidth: 51rem;
+ --brand-FAQ-maxWidth-list: 51rem;- --brand-FAQ-heading-color: var(--brand-color-text-default);
+ --brand-FAQ-color-heading: var(--brand-color-text-default);- --brand-FAQ-heading-color: var(--brand-color-text-default);
+ --brand-FAQ-color-heading: var(--brand-color-text-default);- --brand-FAQ-heading-color: var(--brand-color-text-default);
+ --brand-FAQ-color-tabBg-selected: var(--base-color-scale-blue-0); |
🟢 No visual differences foundOur visual comparison tests did not find any differences in the UI. |
|
looking good @rezrah. minor comments:
other than that. looks great. thank you for putting this together! ❤️ |
There was a problem hiding this comment.
Lgtm!
Some comments around color usage and styles based on the Figma designs @jesussandreas
- Should the space between the heading and the navigation+question be 112 in large viewports and 64px in mobile? Right now is a fixed 64px value
- Are the
+icons supposed to be blue by default?
- Dividers/borders in the mobile version are black/default color. Should we change them?
- In the figma files, the FAQ group doesn't have the subheading repeated in the right list, did that change or is the figma outdated?
| }, | ||
| "tabBg": { | ||
| "selected": { | ||
| "value": "hsl(var(--base-color-scale-blue-5-hsl) / 08%)", |
There was a problem hiding this comment.
In pro of using solid colors, could this be --base-color-scale-blue-0? cc @jesussandreas
Using transparency over that shade of blue causes the color to be a bit more greyish than the normal saturated blue
| Blue 5 with transparency | Solid blue 0 |
|---|---|
|
|
| "tabBg": { | ||
| "selected": { | ||
| "value": "hsl(var(--base-color-scale-blue-5-hsl) / 08%)", | ||
| "dark": "hsl(var(--base-color-scale-blue-4-hsl) / 08%)" |
There was a problem hiding this comment.
Same here, we could use blue 9 instead
There was a problem hiding this comment.
@jesussandreas @josepmartins -- I'm confused. In our Enterprise comp, we're not using a blue highlight at all. Can we make sure that we're following the patterns outlined in our Landing Pages so there's no discrepancies?

There was a problem hiding this comment.
i think it's because initially the blue, it was thought to act as the accent color (ex: our default pink) that can change depending on the brand theme. but i can double check on this and perhaps we blue as our set color.
There was a problem hiding this comment.
@jesussandreas im mostly referring to the left hand groups, not the accordion icons. I worry about using brand themes to impact active states. The blue makes sense here, but I'd love to have a gray default set here in case we want to reduce the volume.
There was a problem hiding this comment.
I added that to the tracking issue https://github.com/github/primer/issues/2510, as this PR was merged last week so we need to update Figma and React libraries.
|
@josepmartins - thanks for creating the Figma version of this pattern. Addressing a few points before I merge this:
These are from the enterprise designs, which are supposedly the latest representations of each components.
I've kept those as
FWIW on Enterprise designs i'm seeing 80 in larger viewports so 🤷 I think this is fairly easy to fix later, so going to proceed with the initial release of this pattern for now. cc. @jesussandreas @ajashams |
|
@rezrah @josepmartins -- Apologies on our delay. Just confirming here for posterity:
|





Summary
Updates appearance for displaying grouped FAQ content, to match recommendations from Site Refactor designs.
🔗 Storybook examples
🔗 Documentation
Part of https://github.com/github/primer/issues/2510
List of notable changes:
FAQGroupcomponent to wrap individualFAQchildren.ButtonGroupAccordionto support newvariantprop, which now supports:defaultandemphasisformats that have unique visualsreversedTogglespropWhat should reviewers focus on?
Steps to test:
Supporting resources (related issues, external links, etc):
Contributor checklist:
Reviewer checklist:
Screenshots:
Narrow viewport presentation:
