[docs-infra] Custom font styles breaks the custom tailwind config
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
I noticed that when the custom font family is added in sandbox it breaks the custom tailwind config, however, it works perfectly fine in the docs (broken sandbox - https://codesandbox.io/s/ymys9l?file=/public/index.html:1549-1575 fonts are not working, but also none of the custom tailwind config). It's likely related to the whole sandbox + create react app + CDN tailwind CSS setup. I am removing it for now, but it may be interesting to consider moving the sandbox and stackblitz demos to use vite instead of create-react-app. cc @mui/docs-infra
Originally posted by @mnajdova in https://github.com/mui/material-ui/issues/38464#issuecomment-1677115622
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The linked CodeSandbox's public/index.html at lines 1549-1575 is the concrete starting point; compare its sandbox, Create React App, and CDN Tailwind CSS setup with the working docs example. Done means custom fonts and custom Tailwind configuration both work in the sandbox demos, with any Vite or StackBlitz change assessed against that result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, tailwindcss, vite
- Domain
- build-system, documentation, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100