How sabinomaggi/mundana-theme-jekyll-multilang works
Main Components
• Jekyll Engine & Build Process – at the core is Jekyll, which takes in markdown and HTML files from folders like _posts, _pages, _data, _includes, and _layouts to generate the final static HTML.
• Content Sources – these include:
• _posts (for blog posts in multiple languages under /en and /it),
• _pages (for standalone pages such as About, Contact, Privacy Policy),
• _data (for additional content configuration like translations).
• Presentation Layer – the theme and templates:
• _layouts (defines various page templates such as default, page sidebar, post),
• _includes (reusable partials/sections like comments, menus, sidebar features, tracking headers/footers, etc.).
• Static Assets – contained in the assets folder:
• CSS (main.css, theme.css) that govern the styling,
• JavaScript (bootstrap.js, lunr.js, theme.js) providing interactivity and tooling (like search using Lunr.js),
• Images used across the blog.
• Configuration and Dependency Files – such as:
• _config.yml which configures Jekyll,
• Gemfile/Gemfile.lock for Ruby dependency management,
• docker-compose.yml that suggests the project can be containerized or has deployment scripts.
• Version Control & Contribution Workflow – managed via Git (indicated by .gitignore, GitHub directory) and contribution instructions in the README.
Relationships and Interactions
• The Jekyll Build Process reads configuration from _config.yml and uses Gemfile dependencies. It then compiles pages and posts (from _posts and _pages) using layouts (_layouts) and partial views (_includes) to produce the final HTML pages.
• The static assets (from the assets folder) are linked into these pages.
• The README and ancillary documentation files indicate that contributions follow a Git-based workflow (fork, branch, pull request), which might also be captured as part of the development cycle.
Architectural Patterns
• Separation of Concerns: Content is separated (posts, pages), presentation (layouts, includes, assets) and configuration (YAML files, Gemfile).
• Template Inheritance: HTML components are reused and dynamically combined during site generation.
• Multi-Language Support: The project organizes content into language-specific directories (e.g., /en, /it) and includes language-switcher components.
Final Steps
• Branch off into two main clusters: the Static Site Build Process and the Final Site Output.
• Within the build process cluster, highlight the roles of configuration files, the content folders, layouts/includes, and static assets.
• User interactions (HTTP requests hitting the static site, possibly served via a CDN or simple static file server) as the endpoint of the build process.