How gotno/gtnoblg works
Main Components
• Content Repository – Represented by the src directory which holds:
• Blog posts: Files under src/vcvrvr (each file named with a date, e.g., “2023-03-01.liquid”). This folder essentially forms the content (blog posts) that the site renders.
• Templates and Layouts: Under src/_includes (layout.liquid, templates, style, etc.), these files define the structure of the pages and apply the visual styles.
• Assets: Images and possibly other static files (stored in src/assets and src/img).
• Build Engine – The Eleventy configuration (eleventy.config.js) and associated package.json scripts. This is the engine that takes the source content and templates and transforms them into a static site.
• Data/Configuration Files – Files such as vcvrvr.11tydata.js (which likely provides metadata or dynamic data for the blog posts) along with configuration files in the root (.gitignore, .tool-versions, package-lock.json, etc.) which support environment and dependency management.
• Deployment/Output Component – Even though not directly visible in the file tree, the output of the build process (the static site files) is destined for the blog domain (blog.gotno.net).
Relationships and Interactions
• The “src” directory is the heart of the project where content (blog posts), presentation (layouts and style files), and additional data (vcvrvr.11tydata.js) reside.
• The Eleventy build engine (configured via eleventy.config.js) reads the source content and applies the templates and styles to generate the final static output.
• Assets (images, CSS, additional resources) are integrated within the templates during the build process.
• The npm/package configuration files support dependency management and might trigger build commands, thereby linking development to production.
Architectural Patterns/Design Principles
• Separation of Concerns: Notice how content (blog posts), presentation (templates and styles), and configuration are segmented into different directories.
• Static Site Generation: The system is designed for static site generation using Eleventy, where runtime dependencies and databases are absent – the site is built at compile time.
• Use of Templating: Liquid templating is used to facilitate reusability and maintain consistency across the blog pages.
Relevant Technologies and Frameworks
• Eleventy (11ty) as the static site generator.
• Liquid Templating Language for the layout and content files.
• JavaScript (for the build process and possible dynamic data handling via files like vcvrvr.11tydata.js).
• npm for package management, and possibly Node.js as the underlying runtime.
• CSS approaches are evident via the style files (modular CSS files like _reset.css, _theme.css, etc.) ensuring styling is centralized.