Design Documentation

Welcome to the LunyScript design documentation. This section covers the architecture, technical decisions, and implementation details.

📐 Architecture & Design

Core Documentation

• Problem Statement - Why LunyScript exists and what problems it solves
• Vision - Long-term vision and desired outcomes
• Author - About the author and personal experience
• Philosophy - API design philosophy and principles
• Engine Differences - How engines differ and how LunyScript unifies them
• Architecture - System architecture and layer structure
• Architecture Diagram - Visual architecture overview
• Namespace Structure - API organization and usage patterns
• Code Comparison - Side-by-side comparison: LunyScript vs traditional approaches
• FAQ - Frequently asked questions
• LunyScript: DSL or API? - It’s a DSL with API-like qualities

Design Risk Assessment

• Cross-Cutting Concerns - Architectural concerns requiring upfront design
• Cross-Engine Concerns - Feature requirements and portability risks

Design Decisions

See Architectural Decision Records for detailed rationale behind key design choices:

• Naming Scheme

Project Evolution

• CHANGELOG - Version history and completed work

🔗 Quick Links

• ← Back to Home
• Join Discussions →

---

AI Usage Info

^{LunyScript is helped by AI. AI usage is regulated to adhere to FOSS principles: → FOSS-compliant AI-Usage}