Replace "FastNext" branding with "PragmaStack" across the project

- 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.
This commit is contained in:
Felipe Cardoso
2025-11-20 12:55:30 +01:00
parent 5a21847382
commit 28b1cc6e48
34 changed files with 191 additions and 62 deletions

View File

@@ -0,0 +1,37 @@
# Visual Identity
## Logo & Iconography
*Pending logo design.*
For now, we use the **Lucide React** icon set for all iconography. Icons should be used sparingly and meaningfully to enhance understanding, not just for decoration.
## Color Palette
Our color palette is derived from the **Modern Minimal** theme using the **OKLCH** color space for perceptual uniformity.
### Primary Colors
- **Primary Blue**: `oklch(0.6231 0.188 259.8145)` - Used for main actions, branding elements, and active states.
- **Background**: `oklch(1 0 0)` (Light) / `oklch(0.2046 0 0)` (Dark) - Clean, neutral backgrounds.
### Usage Guidelines
- **Dominant**: Neutral backgrounds and text (Foreground, Card, Muted).
- **Accent**: Primary Blue for calls to action.
- **Functional**: Destructive Red for errors, Success Green (custom) for success states.
> [!NOTE]
> For the full technical specification of color tokens, refer to the [Design System Foundations](../design-system/01-foundations.md#color-system-oklch).
## Typography
We use **Geist Sans** for headings and body text, and **Geist Mono** for code.
### Type Hierarchy
- **Headings**: Bold, tight tracking.
- **Body**: Regular weight, comfortable reading line height.
- **Code**: Monospaced, slightly smaller than body text.
> [!NOTE]
> For the full typography scale and usage, refer to the [Design System Foundations](../design-system/01-foundations.md#typography).
## Imagery & Graphics
- **Style**: Clean, modern, minimal.
- **Screenshots**: Use consistent padding and shadows (refer to `shadow-lg` or `shadow-xl`).
- **Illustrations**: Avoid generic stock photos. Use abstract geometric shapes or high-quality interface representations.