How the-physicist/universo-de-particulas works
Main Components
• Content Sources:
• _posts and _traducoes – blog posts in original language and translations.
• _pages – special pages like 404, about (sobre), etc.
• _data – additional structured information (such as authors, navigation, UI text).
• Presentation and Layout:
• _layouts – templates for different types of pages (default, home, single, archive, etc.).
• _includes – reusable partials (footer, comments, headers etc.) that help build up pages.
• Styling:
• _sass and assets/css – SCSS files and stylesheets to define the look and feel.
• Assets:
• assets/images – images for posts, authors, and site-specific images.
• Additional asset folders might include JavaScript (if any; not seen explicitly here).
• Configuration:
• _config.yml – central configuration file controlling jekyll settings.
• Gemfile – dependencies for the Ruby/Jekyll environment.
• Deployment/Infrastructure:
• Files like CNAME and maybe static hosting details (although hosting is external, the presence of CNAME suggests a custom domain likely used by GitHub Pages or similar).
Relationships and Interactions
• At build-time, Jekyll reads the _config.yml and processes the content from _posts, _pages, and _data. It merges these with templates from _layouts and partials in _includes.
• SCSS files in _sass and assets/css are compiled into CSS, which is then referenced by the resulting pages.
• The output of this static build is deployed to a hosting environment (likely GitHub Pages given the CNAME, or another static hosting provider).
• During runtime, users (site visitors) access the static pages and assets via a web server.
Highlighted Architectural Patterns and Technologies
• Static Site Generation: The entire site is pre-built by Jekyll, which is driven by well-known patterns for organizing content (separation of concerns with layouts, includes, data, and posts).
• Template Inheritance & Reusability: _layouts and _includes promote reuse to keep the structure DRY (Don’t Repeat Yourself).
• The project is modular: Content (Markdown files), Presentation (layouts and stylesheets), and Infrastructure (configuration/deployment aspects) are clearly separated.
• Although not explicitly documented in the README, the use of directories like _sass/minimal-mistakes indicates that an established theme (“Minimal Mistakes”) is in use, which brings predefined design and responsiveness.