How la-ots/pelican works
Main Components
a. Core Components:
• Design System Core (SCSS/CSS Layer)
• JavaScript Components Layer
• Documentation System
• Build System
b. External Dependencies:
• Bootstrap Base
• Font Awesome
• Public Sans Typography
• jQuery
• Popper.js
┌─ Documentation Layer ─────────────────────┐
• (Eleventy Static Site Generator) │
• Component Examples │
• Usage Guidelines │
• Accessibility Documentation │
• ┘
• ↑
┌─ Design System Core ───────────────────────┐
• ┌─ Presentation Layer ─┐ ┌─ JS Layer ────┐ │
• Theme Variables │ │ - Components │ │
• Component Styles │ │ - Utilities │ │
• Utilities │ │ - Behaviors │ │
• ┘ └──────────────┘ │
• ┘
• ↑
┌─ External Dependencies ──────────────────┐
• Bootstrap Base │
• Font Awesome │
• Public Sans Font │
• jQuery │
• Popper.js │
• ┘
• ↑
┌─ Build System ────────────────────────────┐
• npm Scripts │
• esbuild │
• PostCSS │
• Eleventy │
• ┘
Important Details to Highlight
a. Component Architecture:
• How SCSS components (_alert.scss, _buttons.scss, etc.) compile into the final CSS
• Relationship between JS components and their CSS counterparts
• Demonstrate the theming system with _default-theme-variables.scss
b. Build Process Flow:
• How npm scripts coordinate the build process
• Documentation generation process using Eleventy
• Relationship between source files and distributed assets
c. Distribution Outputs:
• Different bundle types (minified, source maps, ESM)
• How the documentation is built and deployed
Notes
• Keep the focus on the design system's architecture rather than individual components
• Extensibility points for agency theming
• Relationship between documentation and implementation
• Build process but keep it at a high level
Remember to maintain a balance between showing enough detail to understand the system's architecture while not overwhelming the viewer with implementation specifics.