28b1cc6e48
- Updated all references, metadata, and templates to reflect the new branding, including layout files, components, and documentation. - Replaced hardcoded color tokens like `green-600` with semantic tokens (`success`, `warning`, etc.) for improved design consistency. - Enhanced `globals.css` with new color tokens for success, warning, and destructive states using the OKLCH color model. - Added comprehensive branding guidelines and updated the design system documentation to align with the new identity. - Updated tests and mocks to reflect the branding changes and ensured all visual/verbal references match "PragmaStack". - Added new `branding/README.md` and `branding` docs for mission, values, and visual identity definition.
672 B
672 B
Branding Guidelines
Welcome to the PragmaStack branding guidelines. This section defines who we are, how we speak, and how we look.
Contents
- 01. Brand Values & Mission - Our core principles and voice.
- 02. Visual Identity - Logo, colors, and typography usage.
Relationship with Design System
While these branding guidelines define the soul and identity of the project, the Design System provides the technical implementation and components to build it.
- Branding: "Why we use this blue."
- Design System: "How to use the
bg-primaryclass."