How cassie-tatibana/echo_in_yue works
Main Components
• User Interface (UI) Layers:
• Landing pages like index.html, login.html, preface/preface.html.
• Chapter pages organized in the “chapter” directory (each chapter folder contains an HTML file, its specific CSS, and images assets).
• Content pages under the “content” directory which also come with individual HTML, style CSS and image directories.
• A dedicated “directory” section that might serve as an index or navigation helper.
• Interactive 3D Module:
• The “3D” folder contains HTML, CSS, and JS files for interactive or visual 3D content.
• 3D models are stored in the “3D/image” folder (supported formats like .glb, .max).
• Multimedia and Assets:
• Images: Distributed across several folders (general_image, chapter, content, index, etc.).
• Audio: Located in “chapter/voice” and “content/内容音频”.
• Fonts and additional resources.
• Deployment and CI/CD:
• The .github folder with a deploy workflow indicates an automated deployment process, suggesting integration with GitHub Actions or similar tools.
Out the Relationships and Interactions
• Navigation and Linking:
• That each chapter page or content page typically includes a paired CSS and JS file (or multiple scripts, like chapter_scripts.js and content_scripts.js) that help manage user interactions and page-specific behaviors.
• Static Asset Usage:
• 3D Module Integration:
• CI/CD Pipeline:
Architectural Patterns and Design Principles
• Separation of Concerns:
• Each major section (e.g., chapters, content, 3D) is divided into its own folder, keeping HTML, styling, and scripts modular.
• Static Content Delivery:
• There is no dynamic backend layer; the project is organized as a static website where the content is loaded directly from pre-generated HTML files.
• Modular Interactivity:
• The 3D and interactive elements are encapsulated and can be updated or replaced without affecting the overall structure.
• Automated Deployment:
• The inclusion of deployment configurations shows that continuous integration and deployment (CI/CD) practices are in place, ensuring updates are safely and automatically pushed when changes occur.
Relevant Tools, Frameworks, or Libraries
• HTML, CSS, and JavaScript as the primary web technologies.
• GitHub Actions (as seen in the .github/workflows folder) for CI/CD.