CSS architecture for evolving product interfaces
We build maintainable styling for product teams, defining where rules and design tokens live and who can change them. We review layouts against real content and evolve existing stylesheets in controlled steps.
01Overview
CSS is the language; architecture organizes its rules
CSS lays out and styles HTML elements. CSS architecture defines how those rules are named, scoped and maintained as the product changes. Toolkits and component libraries such as Bootstrap and Material UI supply existing styling conventions.
02Capabilities
Layout, shared tokens and incremental stylesheet cleanup
We agree which CSS rules are shared across the interface and which belong to individual components.
- Layout
Layouts tested against real content
We use grid, flexbox and container queries to build layouts around long names, missing images and eleven-item menus. We review the agreed viewports and content variations before treating a layout as complete.
- Theming
Tokens with clear design and code ownership
Custom properties give colour, spacing and type scale shared definitions across components. We connect those tokens through design systems and UX design, including customer-specific themes in the hospitality platforms we build.
- Cleanup
Measure before changing the stylesheet
We inspect which rules are loaded, matched and relied on by the product. That informs changes to selector scope, specificity and accumulated overrides. We review affected screens as rules are retired or reorganized.
03Fit
Match the styling approach to the product
Choose conventions and ownership around the people maintaining the interface and the changes it needs.
| Your situation | What we recommend |
|---|---|
| A small site, one or two developers, and a design that rarely changes | Plain CSSUse readable file organization, scoped selectors and a consistent naming convention such as BEM. Keep the approach proportionate to how the site is maintained. |
| Several teams building against one shared set of components | Shared design systemA design system connects shared tokens and components with agreed ownership and change review. Treat the library and its token definitions as one maintained product. |
| An internal admin screen where speed to a usable page is what matters | Evaluate framework defaultsConsider Bootstrap when its existing components and styling fit the task. Review branding, interaction and maintenance requirements before adopting or extending those defaults. |
| A distinct brand with several themes, or white-label customers | Custom propertiesDefine shared colour, spacing and type values, then map them to each theme. Agree how design and engineering update those tokens and review the rendered result. |
| A stylesheet with unpredictable overrides | Set precedenceInventory existing styles and move legacy or third-party rules into an earlier layer where feasible. Control later and unlayered overrides. New layered normal author rules cannot outrank existing unlayered normal author rules; later layers win for normal declarations. !important reverses layer priority, with layered important rules above unlayered important rules. Retire old rules incrementally with visual review. |
| A design handoff with no token names and no spacing scale | Agree tokens in designUse Figma to agree token names and the spacing scale with design before implementing them. Engineering then defines how those decisions reach the components. |
| A control cannot be used with a keyboard | Semantics + behaviorReview HTML semantics and the component's keyboard interaction. Keep element choice and behavior in the component contract alongside its styling. |
Scope
We own where styling decisions live, how changes are reviewed and who maintains them. We scope cleanup to the affected rules and components. unicrew has been building browser interfaces since 2012. Our wider engineering practice includes 100+ senior in-house engineers across six countries, with an ISO 27001:2022 certified information-security management system. For ownership of the whole interface, see our front-end development service.
04Stack
Tools around CSS architecture
Markup, component libraries and design tooling meet at the stylesheet's boundaries.
05Questions
Questions about maintaining styles and themes
Clarify tooling, design ownership and the boundary between cleanup and redesign.
We work with the convention the maintenance team can use consistently, including an existing project standard.
BEM naming, CSS Modules and Tailwind utilities serve different organizational needs. We agree selector scope, file structure and token ownership before introducing another approach.
Yes. We scope stylesheet cleanup separately from a visual redesign.
We measure shipped CSS and override behavior and review affected screens against the agreed appearance. A redesign changes the appearance and needs design involvement; we track that work separately.
We agree the roles: design defines token names and values; engineering owns how they reach the browser.
A shared design system connects the design source, CSS custom properties and component usage. We define how new tokens are approved and how changes are checked across themes.
We implement dark mode and multiple themes through shared tokens for colour, spacing and typography.
For an existing stylesheet, we map hard-coded values to the intended tokens, agree theme-specific values and review the rendered components in each theme. That work is scoped against the existing styles and design requirements.
We quote CSS work against the affected stylesheets, components and design decisions.
- Time and materials is billed hourly and quoted per project for evolving scope.
- Fixed price is outcome based and quoted per project after the initial stylesheet review.
- Team extension is billed monthly per team member, quoted based on the seniority mix the work needs.
Most engagements start within two to four weeks.
Plan the next styling changes
Share the front end and the changes your product needs. We assess rule organization, tokens and design handoff, then define the stylesheet work or broader web development scope.