docs: add 'Thinking in Panda' page for the v2 engine - #3679
Open
Adebesin-Cell wants to merge 2 commits into
Open
docs: add 'Thinking in Panda' page for the v2 engine#3679Adebesin-Cell wants to merge 2 commits into
Adebesin-Cell wants to merge 2 commits into
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@Adebesin-Cell is attempting to deploy a commit to the Chakra UI Team on Vercel. A member of the Team first needs to authorize it. |
Adebesin-Cell
force-pushed
the
docs/how-panda-works-page
branch
from
July 23, 2026 15:30
a7fc14d to
d2e7b05
Compare
Adebesin-Cell
changed the title
Adebesin-Cell
force-pushed
the
docs/how-panda-works-page
branch
2 times, most recently
from
July 23, 2026 15:38
18d60fa to
c98ab3a
Compare
Adebesin-Cell
force-pushed
the
docs/how-panda-works-page
branch
from
July 23, 2026 15:40
c98ab3a to
7b5d4be
Compare
Adebesin-Cell
force-pushed
the
docs/how-panda-works-page
branch
from
July 23, 2026 15:56
f7c604b to
112edf3
Compare
Explain the mental model — build-time extraction, atomic shared classes, keeping styles static, tokens as vocabulary, and predictable overrides via cascade layers — with a compact under-the-hood note on the Rust/Oxc pipeline. Point why-panda, styled-system, and the FAQ at it instead of each re-describing the v1 PostCSS pipeline.
Adebesin-Cell
force-pushed
the
docs/how-panda-works-page
branch
from
July 23, 2026 16:03
112edf3 to
109357c
Compare
…page # Conflicts: # website/content/docs/overview/why-panda.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 Description
Adds a "Thinking in Panda" page — the mental model behind the v2 engine — and points the pages that still described the v1 pipeline at it.
⛳️ Current behavior (updates)
overview/why-panda,concepts/styled-system, andoverview/faqstill describe the v1 pipeline — "static analysis + PostCSS plugins", "parse each file, run the postcss plugin". That's wrong in v2: extraction is Rust/Oxc, CSS is emitted natively, and PostCSS isn't in the hot path.🚀 New behavior
A new page,
overview/thinking-in-panda.mdx, framed as a mental model rather than a pipeline walkthrough:token(), ternaries) and what it can't (runtime values), with a ❌/✅ pattern. This is the part that matters most when a tool or an AI agent writes the code.@media (width >= 48rem).The three pages above now link to it instead of each re-explaining the pipeline. Added to the sidebar under Overview.
💣 Is this a breaking change (Yes/No):
No. Docs only.
📝 Additional Information
Shape follows StyleX's "Thinking in StyleX" page.
concepts/cascade-layersalready documents the native polyfill, so it's untouched.npx velite --cleanbuilds green; the internal links and the in-page anchor resolve.