feat (#71): component status view and documentation updates#337
Conversation
✅ Deploy Preview for abgov-ui-component-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
ed7a686 to
246b5f0
Compare
|
@twjeffery Just a few things I noticed when looking at the deploy preview: List view of all components Issue count |
Thanks @Spark450 I updated to add those images, they are there now. For the issue count: it was an access issue with the Github API, we needed to add our Github token. Chris just added it to Netlify so now the deploy preview works as expected. But when we deploy it to production we will need to store the Github token for use on our public site. New story created for storing tokens: GovAlta/ui-components#2581 Update: I should be able to use the VITE_AUTH_TOKEN for Github authorization. |
- https://github.com/GovAlta/ui-components-design/issues/71 - added list view of components in separate tab - updated images and image styling - reordered component side menu to sort under component categories - added badges to both views of components based on status
- updated token snippet design - added space on top for consistency on content side menu - broke the colour design tokens into separate tables for a better responsive design of the tables - added all new tokens to token documentation - changed name in main nav from Styles to Tokens - updated naming throughout documentation - changed styling of Get support in main nav - other small content changes
- update to all component documentation pages to split content into tabs - moved properties out of accordion into table - wrapped component properties in accordion, set to open on load - updated componentHeader to include link to Github, Figma, and styling update - moved code examples to their own tab - added links to design documentation in Figma on design tab - added links to accessibility documentation in Figma on accessibility tab
- added link to Figma and copy heading link to clipboard to all relevant examples - fixed external link icon size - updated some component examples to align with design
246b5f0 to
579283f
Compare
@twjeffery Changes look great, thanks for creating that issue to make the issue count work in production. |
bdfranck
left a comment
There was a problem hiding this comment.
Looking good! I found a couple minor issues and potential improvements. I'll switch to testing for now since a more experienced dev can give better specific feedback.
Test resultsComponents side menu
All Components: Card view
All Components: List view
Component page
Component examples
Tokens pages
|
|
@twjeffery Looks good! I only notice one small accessibility issue during testing in Microsoft Edge v135.0.3179.54. When navigating the cards by keyboard, it's hard to notice that the image link is in focus. I can only see the bottom border of the default focus outline. You could address this issue in one of two ways:
|
1c3216d to
265e04b
Compare
I updated the component card to only show a visual focus around the whole card. The Component name and the image remain clickable.
|
|
Thanks for the thorough review @bdfranck I've pushed my changes, it's ready to review again |
There was a problem hiding this comment.
Copilot reviewed 146 out of 155 changed files in this pull request and generated 2 comments.
Files not reviewed (9)
- src/components/code-snippet/CodeSnippet.css: Language not supported
- src/components/component-card/ComponentCard.css: Language not supported
- src/components/component-header/ComponentHeader.css: Language not supported
- src/components/icon-snippet/IconSnippet.css: Language not supported
- src/components/sandbox/Sandbox.css: Language not supported
- src/components/sandbox/sandbox-header/sandboxHeader.css: Language not supported
- src/components/support-info/SupportInfo.css: Language not supported
- src/components/table-of-contents/toc.module.css: Language not supported
- src/components/token-snippet/TokenSnippet.css: Language not supported
Comments suppressed due to low confidence (1)
src/components/component-card/ComponentCard.tsx:32
- If 'props.name' may change during the component's lifecycle, consider including it in the dependency array of the effect that validates the image URL to ensure the image updates accordingly.
const [imageUrl, setImageUrl] = useState(`/images/${dasherize(props.name)}.png`);
bdfranck
left a comment
There was a problem hiding this comment.
All the issues that I mentioned in my previous review have been addressed. Looks good to me! 👍
|
I forgot to test the fixes for GovAlta/ui-components#2313 and GovAlta/ui-components#2313. I tested the AC on both:
|
265e04b to
1b321d6
Compare






Summary
Issues completed:
This also fixes these issues:
Added list view of all components:
Split component documentation into tabs:
Added sandboxHeader component to all code examples:
sandboxHeader.tsxAdded new design tokens to tokens documentation pages
Figma design for reference