8fdbc2b359
- Standardized Markdown formatting across documentation files. - Fixed inconsistent usage of inline code blocks and improved syntax clarity. - Updated tests and JSX for cleaner formatting and better readability. - Adjusted E2E test navigation handlers for multiline code consistency. - Simplified TypeScript configuration and organized JSON structure for better maintainability.
16 lines
673 B
Markdown
16 lines
673 B
Markdown
# 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](./01-brand-values.md)** - Our core principles and voice.
|
|
- **[02. Visual Identity](./02-visual-identity.md)** - Logo, colors, and typography usage.
|
|
|
|
## Relationship with Design System
|
|
|
|
While these branding guidelines define the _soul_ and _identity_ of the project, the **[Design System](../design-system/README.md)** provides the _technical implementation_ and _components_ to build it.
|
|
|
|
- **Branding**: "Why we use this blue."
|
|
- **Design System**: "How to use the `bg-primary` class."
|