docs: add Panda CSS to styling your components guide

[kalisaNkevin]

Adds a Panda CSS setup guide alongside the existing styling options (SASS, LESS, CSS Modules, Macaron, Tailwind, UnoCSS):

• New guide page at /guides/styling-components/panda-css covering installation, PostCSS setup, config, cascade layers, and usage
• Panda CSS card in the CSS-in-JS section of the overview page
• Panda logo asset (official logomark from chakra-ui/panda)

• I have read the Contribution guide
• This PR references an issue (except for typos, broken links, or other minor problems)

Description(required)

Related issues & labels

• Closes #
• Suggested label(s) (optional):

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[netlify]

✅ Deploy Preview for solid-docs ready!

Name	Link
🔨 Latest commit	a866b13
🔍 Latest deploy log	https://app.netlify.com/projects/solid-docs/deploys/6a520b25c66e3800084936bf
😎 Deploy Preview	https://deploy-preview-1583--solid-docs.netlify.app
📱 Preview on mobile	Toggle 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.

[kalisaNkevin]

Let me know your thoughts on this @ryansolid

[amirhhashemi]

I'm not very familiar with Panda, but it doesn't seems to require any configuration specific to Solid. Plus, they already have a guide for solid: https://panda-css.com/docs/installation/solidjs. I'd prefer this to be handled on their side.

Regardless, thank you for your time! If you're planning to work on something new, please open an issue first so we can triage it properly.

[kalisaNkevin]

Thanks for the review, @amirhhashemi!

One correction on the reasoning: Panda CSS does require Solid-specific configuration. panda.config.ts needs this to enable Solid-flavored JSX style props:

export default defineConfig({
  // ...
  jsxFramework: "solid",
});

That's the same kind of framework-specific setup that already justifies dedicated guides for CSS Modules, LESS, Macaron, SASS, Tailwind CSS v3, Tailwind CSS, and UnoCSS under "Styling your components." If that section already covers seven other styling libraries with similarly thin Solid-specific surface area, it's not clear why Panda is the one being asked to live upstream instead.

The Contributing Guide (https://github.com/solidjs/solid-docs/blob/main/CONTRIBUTING.md) also explicitly welcomes this kind of guide addition, which is what I followed in opening this PR.

I also work on the Chakra UI/Panda side (Team Member), so I'm glad to keep this guide current as Panda's API evolves that shouldn't be a maintenance burden solid-docs has to carry alone.

Given that, I'd ask you to reconsider reopening this PR. If you still disagree, I'll respect the call and I'll open an issue first next time either way.

[amirhhashemi]

@kalisaNkevin

Panda CSS does require Solid-specific configuration. panda.config.ts needs this to enable Solid-flavored JSX style props

What I meant was that Solid doesn't require configuration to work with Panda, not the other way around. Though it doesn't make a difference to my decision, as I'll explain.

That's the same kind of framework-specific setup that already justifies dedicated guides for CSS Modules, LESS, Macaron, SASS, Tailwind CSS v3, Tailwind CSS, and UnoCSS under "Styling your components." If that section already covers seven other styling libraries with similarly thin Solid-specific surface area, it's not clear why Panda is the one being asked to live upstream instead.

As you can tell from the commit history, we are short on active contributors. There are a lot of rough edges that have much higher priority than any CSS framework guide, and we still can't keep up. As a result, we are generally cautious about adding any new content. I also think most of the CSS framework guides should be removed, though I haven't discussed this with the team yet.

The Contributing Guide (https://github.com/solidjs/solid-docs/blob/main/CONTRIBUTING.md) also explicitly welcomes this kind of guide addition, which is what I followed in opening this PR.

We haven't updated our CONTRIBUTING.md file in a while, but as I skimmed through it, we generally advise that all PRs be linked to an Issue. If any part of the guide misled you, please tell me so I can fix it.

I also work on the Chakra UI/Panda side (Team Member), so I'm glad to keep this guide current as Panda's API evolves that shouldn't be a maintenance burden solid-docs has to carry alone.

I really appreciate your offer. But at the end of the day, any content on Solid's documentation is the responsibility of Solid's docs team. At this time, I don't feel we can do justice to Panda users. However, we'll probably link to the guide in the Panda documentation once we've figured out what we want to do with this section. You already have a good guide and I don't see a reason to duplicate the work.

That said, please feel free to open an issue so we can discuss it further.