How salehtz/my-website works
Major Components
• Content Repository – This includes the “content” directory (with pages, posts, categories, tags, and multilingual folders), which holds the raw markdown files.
• Assets & Static Files – The “assets” folder (containing CSS, images, and media like music) and the “static” folder (with redirects, browserconfig, manifest, etc.) provide styling and non-processed files.
• Configuration & Internationalization – Files like “hugo.toml” for overall configuration and the “i18n” directory for language-specific translations.
• Themes – The “themes” directory (specifically “LoveIt”) that defines the presentation layer and template system for Hugo.
• Generated Resources – The “resources” folder that holds preprocessed/generated styles, images, and other assets.
• Build & Deployment System – The “.github/workflows/hugo.yaml” indicates a CI/CD pipeline (using GitHub Actions) that automates the site generation process.
• Public Output – The “public” directory contains all the generated output (HTML, XML, and assets) ready for deployment to GitHub Pages.
Relationships and Data Flows
• Content, assets, and static files are combined by Hugo using the configuration file (hugo.toml) and the selected theme to produce the website.
• The multilingual structure of “content” and “i18n” is combined during the build to generate language-specific folders in the “public” output (e.g., “fa”, “en”, “zh-cn”, etc.).
• GitHub Actions (triggered by pushes/commits) leverages the “hugo.yaml” workflow to run the Hugo build process.
• The final generated site (in the “public” folder) is deployed – likely to GitHub Pages as indicated by the README link.
Architectural Patterns and Technologies
• Static Site Generation – The entire site is built as a static website using Hugo.
• Separation of Concerns – The project neatly separates content (in “content”), styling and images (in “assets” and “static”), configuration (hugo.toml and i18n files), and presentation (themes).
• CI/CD Integration – Use of GitHub Actions to automatically build and (presumably) deploy the site.
• Multi-Language Support – Organizing multilingual content is a key feature.