How tanishkthoria/personal-website works
Main Components
• Content Management – The “content” folder holds the markdown files (posts, pages such as about.md, contact.md, etc.) which represent the website’s content.
• Configuration & Metadata – The “config.toml” file contains the global configuration for the Hugo site, including settings for themes, menus, taxonomies, and build parameters.
• Theme Components – The “themes” directory (particularly the Hugo-Programmer theme) contains the layout templates, partials, and styling (CSS/SCSS) that dictate the website’s look and feel.
• Assets & Resources – The “resources” folder holds generated assets (CSS/JS) that are compiled from source (e.g., SCSS) and optimized by Hugo.
• Build Outputs – The “public” folder and alternate “isableFastRender” folder contain the pre-built static files (HTML, CSS, JS, images, etc.) that will be deployed.
• Deployment – The “netlify.toml” file and badges in the README indicate that Netlify handles the build/deploy process.
• Auxiliary/Supporting Files – The “archetypes” (default page/template definitions) and other configuration/log files help manage content creation and site behavior.
Out Relationships and Interactions
• The Content Layer: The “content” folder provides the website’s textual data (posts, pages, etc.).
• The Configuration Layer: “config.toml” and archetypes define the project’s settings and behavior.
• The Presentation Layer: The “themes” directory supplies templates, layouts, and styling which the Hugo engine uses to render the content.
• The Build Process: Hugo, as the static site generator, reads the content and configuration, applies the theme/templates, and produces the final static files stored in “public” (or “isableFastRender”).
• The Deployment: Once built, the static assets are deployed (via Netlify or a similar service) to be served as the live website.
Architectural Patterns and Technology Use
• Static Site Generation – The system follows a build pipeline where content and configuration are compiled into static files.
• Separation of Concerns – The content (Markdown files), configurations (config.toml, archetypes), and presentation (themes, assets) are clearly separated into distinct directories.
• Modular Theming – The use of an external theme (Hugo-Programmer) simplifies maintenance and modular development.
• Build & Deployment Automation – With Netlify configuration and a dedicated branch for testing (as per the README), continuous deployment and version control practices are evident.