How gillopy/portfolio works
Main components
• Frontend/UI Layer: This is primarily in the “src” folder, subdivided into:
• Components (UI building blocks like Header, HeroSection, ContactSection, etc.)
• Layouts (overall page templates such as Layout.astro and ProjectLayout.astro)
• Pages (routes for the home page, project details, 404, etc.)
• Data Layer: JSON files under “src/data” (profile.json, projects.json, skills.json, siteConfig.json) that drive the content and configuration of the site.
• Public Assets: Static assets folder (e.g., images and the website screenshot)
• Utility Functions: “src/utils” where functions like getProjectData.js process the content for pages.
• Configuration & Build Tools: astro.config.mjs, tailwind.config.mjs, package.json, and bun.lock – these files define project behavior and are used during development and deployment.
• Deployment/Hosting: The Netlify configuration (netlify.toml) and build scripts (via Bun or npm) indicate how the site is built and served as a static site.
And Represent Relationships/Interactions
• The Pages consume Layouts and UI Components to render the website. For example, the homepage (index.astro) uses multiple components (HeroSection, AboutSection, etc.) and a primary Layout.
• Utility functions act as connectors that process data before it is rendered by the components.
• The Build/Configuration module (Astro, Bun, Tailwind) encapsulates the entire source code and ties the static site generation process together.
• Deployment configuration (Netlify/Vercel configuration files) indicates the output (build produce in the “dist” directory) and the hosting strategy.
Architectural Patterns and Design Principles
• The project is structured in a modular way with separation of concerns: Data, Presentation, and Utilities.
• Component reusability: UI components and layouts are decoupled to allow consistency across multiple pages.
• Static-site generation: Astro’s build process creates static HTML based on dynamic JSON content.
• Responsive design principles are implemented via Tailwind CSS.
• A clear distinction exists between static assets and dynamic content configuration.