metodologia-design-system

To generate branded HTML deliverables, you apply a token-driven design system using a brand-config.json file at the repository root. This automates the application of consistent branding, typography, and layout across proposals, reports, and documentation.

Yes, a brand-config.json file at the repository root is required to configure brand colors, typography, spacing, and layout. This file serves as the foundation for generating CSS custom properties and ensuring consistent branding.

Yes, you can use a ready-to-use component library including cards, headers, callouts, tables, and diagrams. These patterns are aligned with the design system to produce scalable and consistent client proposals and reports.

The best way to ensure WCAG AA accessibility is to use a design system with a defined accessibility baseline. This automatically applies compliant color contrast, typography, and structural standards to your generated HTML deliverables.

Design tokens work by defining brand colors, typography, and spacing as CSS custom properties derived from a brand-config.json file. These tokens are automatically applied across a component library to generate consistent HTML deliverables.

Yes, CSS custom properties are required to map the configured brand tokens from the brand-config.json file. They enable the automated application of your design system's styling rules across all generated HTML deliverables.