Presentation
Tailwind CSS
Tailwind CSS is how we style the stack we ship. It is running on this website. Next.js and React sit beside it. It is not a plugin we add after the audit. It ships in the repo.
What it actually does
Style classes in the page code. Not a page builder, not a Figma export, not a rented theme.
The look is named in the theme. This site uses names like `bg-surface` and `text-heading`. On a client build, that CSS lives in git, and it is theirs.
This website runs Tailwind CSS v4. A client build uses the version named in the proposal.
Where it is strong
Styles live next to the components. There is no parallel stylesheet to drift after handoff.
Locales and RTL use the same classes. There is not a second stylesheet for right-to-left.
There is no Tailwind account to create or transfer. Handoff is the repository.
Their site, not ours
Tailwind's docs and releases live on their site. There is no agency Tailwind invoice to mark up.
When we would name it
- Every build we ship. Next.js, React, and Tailwind go in with GitHub, Railway, and the ownership docs.
- A custom App Router site, not a locked builder.
- The look belongs in git, not in a hosted theme kit.
When we would not
- You already have Chakra, MUI, or CSS-in-JS and it has to stay. We name that system in the proposal. We do not list Tailwind as if it were in the build.
- You want Webflow, Framer, or a locked template. That is not this stack.
- You only want a static brochure with no App Router. We are not the fit.
- If Tailwind cannot be used, that is not a defect. There is no vendor account to rename. We record the exception in the proposal.
In a WebeWorx build
There is no Tailwind account to create. It is application code in the private GitHub repo.
This site runs it. Client sites get the same shape, with their tokens, not our brand palette copied over.
At handoff the CSS is theirs. Any developer can keep shipping.