Our approach to CSS and how we chose it

Tines recently decided to overhaul its CSS approach due to the previous lack of a cohesive strategy, which included a mix of Tailwind, SASS, CSS modules, and inline styles, causing inefficiencies and hindering the implementation of features like dark mode. The team evaluated various CSS methodologies and ultimately chose the CSS-in-JS approach, specifically Linaria, for its build-time dependency feature, which minimizes run-time risks and complexity. This decision was based on the need for a more unified styling strategy that enhances readability and maintainability, while also aligning with Tines' existing investment in TypeScript and the desire for type safety in styling. As a result, the team has begun migrating their codebase away from Tailwind and CSS modules, finding the new approach more intuitive and conducive to future developments, such as dark mode, while also celebrating progress through a dedicated Notion page tracking ongoing migrations.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.