Systems
CivicTheme has several unique architectural approaches for developing themes that promote component-centric development and maintainability. Understanding these systems is essential for building sites that work effectively within the CivicTheme ecosystem.
Overview
CivicTheme's development approach is built around these core systems:
- Component-centric architecture - Organised folders for styles, JavaScript, and templates 
- Template separation - Component Twig templates separated from Drupal - *.html.twigfiles
- Preprocess functions - Custom functions to populate component template properties 
- Color system - Custom color overrides and theming capabilities 
- Build system - Custom asset compilation and development workflow 
System Documentation
Each system has detailed documentation that explains implementation patterns and best practices:
Learn about CivicTheme's custom build system, including asset compilation, configuration, and development workflows.
Explore the color override system and how to customise CivicTheme's design tokens.
Understand the component-centric approach, including template separation, preprocess functions, and how to map Drupal data to component properties.
Discover how Drupal entities are mapped to component templates and properties.
Related Documentation
Component Development
- Templates - How to use CivicTheme UI Kit components in Drupal 
- Namespaces - Component namespace system and organisation 
- Assets - Asset management and component structure 
Learning Path
To effectively work with CivicTheme systems:
- Start with the basics: Read Templates to understand component separation 
- Understand the build system: Review Build System for development workflow 
- Learn component mapping: Study Components for data flow patterns 
- Customise appearance: Explore Colors for theming 
Key Benefits
Learning these systems enables you to:
- Build component-centric sites that are maintainable and scalable 
- Create reusable patterns that work across different projects 
- Leverage CivicTheme's ecosystem effectively 
- Maintain consistent design and development standards 
- Extend functionality without breaking existing patterns 
Getting Help
- Getting Help - Community resources and support 
- Contribution Model - How to contribute to the ecosystem 
- GitHub Organisation - Source code and issues 
Last updated
Was this helpful?
