How aonghasmackay/planetarysystemgenerator works
[Configuration Layer] (Top)
• ↓
[Generation Engine] (Middle)
• ↓
[Presentation Layer] (Bottom)
Detailed Component Breakdown
A. Configuration Layer
• Into logical categories (celestial objects, naming conventions, planetary attributes)
B. Generation Engine (Core)
• Supporting modules around it:
• Planet Name Generator (planetNames.js)
• Global Utilities (globalFunctions.js)
• Debug System (debugFunctions.js)
C. Presentation Layer
• UI Components:
• Filtering System (filteringHandler.js)
• Disabled Elements Handler (disabledElementsHandler.js)
• SCSS/CSS structure:
• Hierarchy of SCSS files (variables → mixins → elements → modular → main.scss)
Data Flow Representation
Configuration Files → System Generator
System Generator → UI Components
UI Components → User Interface (HTML/CSS)
Technical Stack Indicators
• HTML5
• CSS3/SCSS
• Vanilla JavaScript
Render to UI
• The modular nature of the configuration system
• The central role of the generation engine
• The separation of concerns between generation and presentation
• The SCSS architecture
This approach will give other developers a clear understanding of how the system works, from configuration loading through generation to final presentation, while maintaining a good balance between detail and clarity.