How shirleyzmj/singapore-sharing-ppt works
Main Components
• Client-Side Presentation Layer: Represented by the Next.js application and its page components in the ‘ppt/src/app’ directory. This is your core entry point.
• Slide Components: All slide-related components in ‘ppt/src/components’ (especially in the ‘slides’ subdirectory). List each significant slide type such as TitleSlide, HousingSlide, TransportationSlide, etc.
• Assets & Static Files: The ‘ppt/public’ directory, which contains images and other static content, and the global styles in ‘ppt/src/app/globals.css’.
• Styling & Configurations: Represent configuration files (tailwind.config.js, postcss.config.js) and the overall build setup (package.json, next.config.js) as they define styling and app behavior.
• External Libraries/Frameworks: Include Next.js (for the application framework), Tailwind CSS (for styling), recharts.js (for any graphical data visualizations), and Reveal.js (to support slide transitions, navigation and presentation features).
Relationships and Interactions
• Data Flow: Start with the main entry (layout.js and page.js in the app directory), which then loads and orchestrates slide components from the ‘components/slides’ directory.
Architectural Patterns and Design Principles
• Component-Based Architecture: Break down the presentation into reusable slide components with independent functionalities.
• Separation of Concerns: Distinguish between presentation logic (slide components), global styling (CSS and Tailwind configuration), and static assets.
• Routing and Layout: Illustrate how Next.js’s file-based routing drives the display of the presentation and how the app’s global layout wraps all slide components.
• Extensibility: Note that new slides are added by creating new components in ‘src/components/slides’ and updating the main slide order in ‘src/app/page.js’.