solidjs / solidjs/solid-docs

[Request]:Consolidate "Styling your components" guides into an external resources directory

Aperta
#1,593 4 commenti 2 reazioni 1 assegnatario Vedi su GitHub

@LadyBluenotes ci sta già lavorando.

Dal 24/7/2026.

help wanted
Lingua principale
MDX
Stelle
292
Fork
361
Merge medio
7h 51m
PR unite (30g)
1

Descrizione

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

  1. Reduces Maintenance Burden: The Solid team no longer has to maintain and test configuration steps for third-party styling tools.
  2. 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.
  3. 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

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.