How aziontech/azion-theme works
Project type and purpose
• azion-theme is an open-source style kit/theme library for styling Azion’s front-end applications.
• It publishes SCSS/CSS and JavaScript “theme” artifacts via npm, to be imported by consumer projects (e.g., Azion Console Kit, landing pages, etc.).
File structure
• Top-level files & folders
• package.json, default.js, widget.js – entry points and package configuration
• src/azion – all SCSS source modules grouped by concerns
• doc – documentation and cover image
• .github/workflows/release.yml – CI/CD pipeline for versioning and npm publishing
• src/azion breakdown
• theme-base – low-level mixins, component styles organized by category
• extended-components – custom overrides on top of PrimeVue components
• custom – project-specific style modifiers (scroll behavior, focus, code blocks)
• fonts, widgets, variables-widget – entry for widget-specific styling
• theme.scss, theme-widget.scss – top-level SCSS that pulls everything together
• Build & release
• default.js & widget.js import the SCSS bundles and export CSS for npm consumers
• GitHub Actions workflow automates release to npm registry
Insights from README
• Primary use: install via npm/yarn, then import ‘azion-theme/light’ or ‘azion-theme/dark’
• Local development uses npm link + hot-reload when paired with a front-end project
• Built on PrimeVue Sass Theme
• Source Layer (SCSS modules)
– Variables (tokens)
– Theme-base (mixins + base components)
– Extended-components (component overrides)
– Custom styles (UI tweaks)
– Widgets (widget specific styles)
• Build Layer
– SCSS Compiler (node-sass or dart-sass)
– JavaScript Bundler (default.js, widget.js)
• Distribution Layer
– CI/CD (GitHub Actions)
– npm Registry (azion-theme package)
• Consumer Layer
– Front-end projects (import theme, apply light/dark)
– Local dev with npm link & hot reload
• Documentation
– doc folder, README, CHANGELOG
• theme.scss & theme-widget.scss → Build Layer → CSS/JS artifacts
• Build Layer → CI/CD → npm Registry
• npm Registry → Consumer projects
• For local dev: Consumer projects ← npm link ← azion-theme source
c. Architectural patterns & design principles
• Layered modular architecture for SCSS (design tokens at core, then base, then overrides)
• Single-responsibility: each folder focuses on one type of style definition
• CI/CD-driven release management
• Extensibility via npm linking and custom override layers
d. Key technologies & frameworks
• SCSS (Sass)
• Node.js build scripts (default.js, widget.js)
• GitHub Actions for CI/CD
• npm for packaging & distribution
• PrimeVue Sass Theme as baseline