Closed markhigham closed 4 weeks ago
Name | Link |
---|---|
Latest commit | 45b90fc81f4257de7692b6da5a3aa503d2a6bded |
Latest deploy log | https://app.netlify.com/sites/storybook-navy-digital-mod-uk/deploys/6620d0d55aa1d6000856bc60 |
Deploy Preview | https://deploy-preview-3746--storybook-navy-digital-mod-uk.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Can we change these commit message types from feat
and fix
to docs
where they are Storybook related.
The font used in the SVG graphics appears to be incorrect - it should be using the one from the fonts package.
The font used in the SVG graphics appears to be incorrect - it should be using the one from the fonts package.
The Lato font stack isn't readily available in the mdx files. I used the system stack as an interim measure. We can take a look at how to make this consistent in a subsequent release.
It's better than the current site which is times new roman
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
Related issue
Closes #3750
Overview
Add guidance for component and token usage to the storybook. Token examples are based on the actual design tokens.
Reason
We wanted to reduce the cost / overhead of maintaining a separate DS website and the storybook. It was important to generate the tokens docs from the actual code
Work carried out
Components
folder