What is this request related to?
Request
📋 Suggested
https://docs.solidjs.com/guides/styling-components/css-modules
📋 General description or bullet points
Context
Following up on the discussion in PR #1583, it's clear that the docs team is currently stretched thin. Maintaining dedicated setup guides for external CSS frameworks (Tailwind, UnoCSS, Macaron, LESS, etc.) introduces a continuous maintenance burden, especially as those external APIs evolve.
The Problem
Currently, the "Styling your components" section hosts extensive configuration guides for various tools. Keeping these up-to-date pulls focus away from documenting core SolidJS features. Additionally, it creates friction when trying to add new tools (like Panda CSS) because adding them means adding more maintenance weight to the solid-docs team.
The Proposal
Instead of hosting full installation and configuration guides for external styling libraries, I propose we consolidate this section into a single "Styling Ecosystem" or "External Styling Resources" page.
This page would:
Briefly explain the different approaches to styling in Solid (e.g., CSS Modules, CSS-in-JS, Utility-first).
Provide a directory listing of popular community-adopted tools (Tailwind, Panda CSS, UnoCSS, Macaron, etc.).
Link directly to each tool's official SolidJS installation guide on their respective documentation sites.
Benefits
- Reduces Maintenance Burden: The Solid team no longer has to maintain and test configuration steps for third-party styling tools.
- Always Up-to-Date: Users are routed to the source of truth, ensuring they always get the latest configuration steps directly from the framework authors.
- Easier Ecosystem Expansion: Adding a new tool to the docs becomes a simple one-line link addition rather than a multi-page guide review.
🖥️ Reproduction of code samples in StackBlitz
N/A
What is this request related to?
Request
📋 Suggested
https://docs.solidjs.com/guides/styling-components/css-modules
📋 General description or bullet points
Context
Following up on the discussion in PR #1583, it's clear that the docs team is currently stretched thin. Maintaining dedicated setup guides for external CSS frameworks (Tailwind, UnoCSS, Macaron, LESS, etc.) introduces a continuous maintenance burden, especially as those external APIs evolve.
The Problem
Currently, the "Styling your components" section hosts extensive configuration guides for various tools. Keeping these up-to-date pulls focus away from documenting core SolidJS features. Additionally, it creates friction when trying to add new tools (like Panda CSS) because adding them means adding more maintenance weight to the solid-docs team.
The Proposal
Instead of hosting full installation and configuration guides for external styling libraries, I propose we consolidate this section into a single "Styling Ecosystem" or "External Styling Resources" page.
This page would:
Briefly explain the different approaches to styling in Solid (e.g., CSS Modules, CSS-in-JS, Utility-first).
Provide a directory listing of popular community-adopted tools (Tailwind, Panda CSS, UnoCSS, Macaron, etc.).
Link directly to each tool's official SolidJS installation guide on their respective documentation sites.
Benefits
🖥️ Reproduction of code samples in StackBlitz
N/A