Skip to content

docs: rewrite css and styling section for start v2#1585

Open
katywings wants to merge 3 commits into
mainfrom
docs/start-v2-css
Open

docs: rewrite css and styling section for start v2#1585
katywings wants to merge 3 commits into
mainfrom
docs/start-v2-css

Conversation

@katywings

Copy link
Copy Markdown
Collaborator

Description

This adds back the CSS and styling to the new SolidStart 2.0 docs. It is almost completely reworked and reworded and has a new list of SolidStart v2 changes related to the CSS handling and new sections:

  • Route-specific global styles
  • Lazy loading

Related issues & labels

@bolt-new-by-stackblitz

Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@netlify

netlify Bot commented Jul 11, 2026

Copy link
Copy Markdown

Deploy Preview for solid-docs ready!

Name Link
🔨 Latest commit 85f0d74
🔍 Latest deploy log https://app.netlify.com/projects/solid-docs/deploys/6a54cfcb901d4b0007c5892d
😎 Deploy Preview https://deploy-preview-1585--solid-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@katywings katywings self-assigned this Jul 11, 2026
@katywings
katywings requested a review from LadyBluenotes July 11, 2026 16:35

@jer3m01 jer3m01 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice guide, hadn't thought of <Link> & ?url.

Comment thread src/routes/solid-start/v2/(0)building-your-application/(2)css-and-styling.mdx Outdated
Comment on lines +19 to +26
SolidStart 2.0 introduces a completely revamped CSS rendering mechanism:

- CSS deduplication during server-side rendering works more consistently across the board.
- Hot module replacement (HMR) of route CSS is now directly managed by Vite instead of SolidStart.
- CSS in `lazy`-loaded components is now properly server-side rendered and does not result in flashes of unstyled content.
- Client-side navigation now mounts new CSS directly via Vite instead of SolidStart.
- Server HTML responses no longer have to include the whole assets manifest.
- Client-side navigation no longer unmounts old CSS, more closely following Vite's native behaviour.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this section should be moved to a migration guide. Ideally, we don't want to confuse new users by comparing v1 and v2 in the core docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants