How pottekkat/personal-website works
Based on our review of both the file tree and README, this project is the source for a personal website (navendu.me) built with Hugo and a highly personalized version of the Hugo PaperMod theme. The website is content rich (with posts, dailies, newsletters, and TILs), and it uses various assets (CSS, JavaScript, images) along with custom scripts for managing front matter, deployments, and even some minor Go code. There’s also a CI/CD setup using GitHub workflows and integration with Netlify for hosting.
Main Components
• Content Repository: Show “content”, “archetypes”, and “data” folders – these are where all the textual/blog content and structured data (like stats) reside.
• Assets & Static Files: Include “assets” (with subfolders for CSS and JS) and “static” (images, web manifest, etc.). These serve as the front-end cosmetics and resources for the site.
• Layouts & Templates: Represent the “layouts” folder (and its subfolders like _default, partials, shorts codes, etc.) which define how content is rendered into HTML.
• Build System (Hugo): Indicate Hugo (the static site generator) as the build engine that takes content (from content, assets, etc.) and layout instructions to produce the final static site.
• Custom Scripts & Tools: Note the “scripts” folder and use of “cmd/main.go” (and other language-specific scripts in “.github” and “frontmatter” directories) that help with front matter processing, content management, and possibly custom build steps.
Relationships & Data Flow
• How custom scripts (frontmatter adjustments, Go programs) interact with the content repository as pre- or post-processing tools.
• Deployment flow: from the committed repository triggering GitHub workflows that eventually push the final static files to Netlify.
• How the end user (web browser) accesses content served from the Netlify-hosted site.
Architectural Patterns & Design Principles
• Static Site Generation: Emphasize that the site is built using a static site generation pattern where content is pre-rendered.
• Separation of Concerns: Distinguish clearly between content (markdown files, JSON data), presentation (layouts, CSS, JavaScript), and build orchestration (Hugo, CI scripts).
• Personalization Layer: Note that the project uses a highly personalized version of the Hugo PaperMod theme – which means that while following PaperMod’s structure, further customizations are applied.
• Content (content folder, archetypes, data)
• Presentation (assets, static, layouts)
• Custom Tools & Scripts (scripts folder, cmd/main.go, frontmatter)