How milyd/milyovh works
Main components
• Personal Website Frontend (Content)
• Markdown pages (e.g., index.md, about-me.md, hardware.md, test.md, karmelek.md, projects.md)
• HTML layout files under _layouts (default.html, header.html, footer.html)
• Configuration & Data
• Jekyll configuration file (_config.yml)
• Data files in the _data folder (hardware.yaml, navigation.yaml, projects.yaml) which drive dynamic content
• Assets
• CSS files (assets/css folder – aos.css, custom.css)
• JavaScript files (assets/js folder – aos.js)
• Image files (assets/img folder)
• Supporting Files
• Gemfile and Gemfile.lock for dependency management (Ruby gems for Jekyll)
• Miscellaneous static files (404.html, sitemap.xml, robots.txt)
• Deployment Context
• The site is likely hosted using GitHub Pages or similar deployment for static sites
Relationships and interactions
• The Jekyll configuration (_config.yml) directs how the content pages, layouts, and data integrate together.
• Markdown files are processed with the corresponding Liquid templates from _layouts to produce the final HTML.
• The _data files feed dynamic content into pages via Liquid templating.
• Assets (CSS, JS, images) are integrated within the HTML during build-time to style and add interactivity.
• External dependencies are defined in the Gemfile, with Jekyll and related libraries being crucial.
Important architectural patterns and design principles
• The Model-View-Like separation: Content (Markdown files and _data) is kept separate from presentation (layouts and assets).
• Standard static site generation flow: source files are compiled into a static HTML website.
• Reusability and modularity are promoted through modular layout components (header, footer, default) and data files.
Incorporate relevant technologies and frameworks
• Jekyll as a static site generator (Ruby-based)
• Liquid templating for merging content with layouts
• Standard web technologies for the frontend (HTML, CSS, JavaScript)
• RubyGems (indicated by Gemfile/Gemfile.lock) for dependency management
Detail and Clarity
• That every component—ranging from content files to assets—is represented.
• Even though the project is relatively straightforward (a personal static website), capturing each element explicitly makes it easier for future maintainers or collaborators to understand the full system architecture.