How titicacadev/triple-frontend works
High-Level Architecture Overview
a. Core Framework Layer:
• Next.js integration packages (triple-web-nextjs, triple-web-nextjs-pages) at the foundation
• Core utilities and type definitions packages
b. Component Layer:
• Main UI component library (tds-ui)
• Specialized widget components (tds-widget)
• Document handling components (triple-document, triple-email-document)
c. Feature Layer:
• Functional packages (router, fetcher, i18n)
• Experimental features (ab-experiments)
• Cross-cutting concerns (middlewares)
Package Dependencies
• Core infrastructure (blue)
• UI components (green)
• Utilities (gray)
• Feature modules (orange)
Integration Points
Integration areas:
• Storybook integration for component documentation
• Next.js framework integration
• Testing utilities and infrastructure
• Build and deployment pipeline
Component Architecture
For the UI component section:
• Components by type (basic, composite, specialized)
• Theme system integration (tds-theme)
• Shared utilities and hooks
• State management patterns
Development Infrastructure
A section showing:
• GitHub Actions workflows
• Testing framework integration
• Documentation generation
• Build system configuration
• Rectangles for packages
• Hexagons for core services
• Circles for integration points
• Double rectangles for framework components
Key Considerations:
Development workflow and tools
• Infrastructure and core utilities at the bottom
• UI components and widgets in the middle
• Application-specific integrations at the top
This will create a clear visualization of how the Triple Frontend system is structured and how its various components interact while maintaining a focus on its primary purpose as a component library and frontend framework.