nibula 1.1.3 → 1.2.0

package/.eleventy.js

@@ -1,7 +1,6 @@
 const esbuild = require("esbuild");
 const glob = require("glob");
 const Image = require("@11ty/eleventy-img");
-const markdownIt = require('markdown-it');
 const fs = require("fs");
 const path = require("path");
 
@@ -24,18 +23,11 @@ module.exports = function (eleventyConfig) {
     }
   }
 
-  const md = markdownIt({ html: true });
-
   eleventyConfig.addShortcode('mdFile', function(filePath) {
     const content = fs.readFileSync(filePath, 'utf8');
     return md.render(content);
   });
 
-  eleventyConfig.addPassthroughCopy({
-    "node_modules/github-markdown-css/github-markdown-dark.css": "css/github-markdown-dark.css",
-    "node_modules/github-markdown-css/github-markdown-light.css": "css/github-markdown-light.css",
-  });
-
   eleventyConfig.on("eleventy.before", () => {
     copyRecursiveSync("src/backend", `${OUTPUT_DIR}/backend`);
   });
@@ -43,6 +35,7 @@ module.exports = function (eleventyConfig) {
   eleventyConfig.addPassthroughCopy("src/frontend/.htaccess");
   eleventyConfig.addPassthroughCopy("src/frontend/web.config");
   eleventyConfig.addPassthroughCopy("src/frontend/assets");
+  eleventyConfig.addPassthroughCopy("src/frontend/data");
   eleventyConfig.addPassthroughCopy("src/frontend/robots.txt");
 
   eleventyConfig.addPassthroughCopy({
@@ -76,7 +69,7 @@ module.exports = function (eleventyConfig) {
   });
 
   eleventyConfig.addWatchTarget("./src/frontend/scss");
-  eleventyConfig.addWatchTarget("./src/frontend/_routes");
+  eleventyConfig.addWatchTarget("./src/frontend/routes");
   eleventyConfig.addWatchTarget("./src/frontend/data");
 
   eleventyConfig.setServerOptions({

package/CHANGELOG.md

@@ -5,58 +5,36 @@ All notable changes to Nibula are documented here.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [1.1.3] - 2026-07-22
-
-### Changed
-- **The update check no longer runs on every command.** Previously every
-  invocation of `nib` (and the `nbl` / `nibula` aliases) contacted the npm
-  registry before doing anything, adding up to 2.5s of latency to `nib run`,
-  `nib build`, `nib cli` and `nib clean`. The check now runs only for `nib new`
-  and `nib update`; all other commands work entirely offline.
-- **`nib new` now completes the update automatically.** When a newer version is
-  available and you accept the prompt, Nibula installs it and immediately
-  re-runs the scaffolding with the new version, instead of asking you to type
-  `nib new <project-name>` a second time.
-- **New projects are scaffolded at version `0.0.0`** instead of `1.0.0`, so a
-  freshly created site no longer claims a stable public release. Bump it
-  yourself as the project grows, and reach `1.0.0` when you go to production.
-- **Framework SCSS imports are now short and readable.** The framework modules
-  in `src/frontend/scss/modules/frameworks/` used a five-level relative path
-  back to `node_modules`; they now import directly by package name, e.g.
-  `@import "bootstrap/scss/card";`. This matches what the styling docs already
-  showed, and makes commenting modules out far less error-prone.
-- `nib help` no longer appends an "a newer version is available" line, since it
-  no longer performs the check.
+## [1.2.0] - 2026-07-23
 
 ### Added
-- Internal `--skip-update-check` flag on `nib new`, set automatically when the
-  command is re-run after a self-update. It prevents a loop if the registry is
-  slow to propagate the new version.
-- `--load-path=node_modules` on the repository's own `build:css` and `serve:css`
-  scripts, so the short framework imports resolve. Generated projects already
-  carried this flag.
+- **Full favicon set**: `favicon.svg`, `favicon-32.png` and `apple-touch-icon.png`
+  (180×180, opaque) in `assets/brand/`. iOS home-screen icons no longer fall back
+  to a screenshot of the page.
 
-### Fixed
-- Repaired the ASCII header boxes and the commented-out example import inside
-  `_bootstrap.scss`, `_bulma.scss` and `_foundation.scss`, where an earlier
-  find-and-replace had injected the `node_modules` path into comment text and
-  broken the alignment.
-- `src/frontend/data` is no longer copied to the output folder. It holds the
-  Eleventy global data file, which is consumed at build time to render meta
-  tags and page config — publishing it produced a dead file in `out/` and
-  exposed the full page map, including `noindex` entries. It remains a watch
-  target, so edits still trigger a rebuild.
+### Changed
+- **`data_bs_theme` renamed to `theme`** in `site.json`. It still drives
+  `data-bs-theme` on the `<html>` tag; the shorter name keeps the config readable
+  and independent from the framework naming.
+- **`theme_color` is now a single value** instead of a `light`/`dark` pair. The
+  theme is fixed per build, so two per-scheme colors could contradict the
+  rendered page.
+- **Favicon paths are hardcoded in `base.njk`.** The `favicon` key was removed
+  from `site.json`: it only ever covered one of the three tags, which was more
+  confusing than helpful. Replace the files in `assets/brand/` instead.
+- `_routes/` renamed to `routes/` — it holds entry points, not internals.
 
-### Notes
-- If the updated installation can't be located after `npm install -g` (an
-  unusual `npm root -g` setup, for example), Nibula reports the problem and
-  asks you to re-run the command, rather than scaffolding silently with the
-  old templates.
-- Existing projects are unaffected by the version change: it applies only to
-  newly created ones.
-- Short SCSS imports rely on Sass's `--load-path`, which is passed by the npm
-  scripts. Compiling the stylesheets with a different tool (a VS Code Sass
-  extension, for instance) will need the same load path configured.
+### Removed
+- **`mdFile` shortcode** and the `markdown-it` dependency.
+- **`github-markdown-css`** and its two passthrough copies.
+
+### Migration
+- In `site.json`: rename `data_bs_theme` to `theme`, flatten `theme_color` to a
+  single string, drop `favicon`.
+- Place `favicon.svg`, `favicon-32.png` and `apple-touch-icon.png` in
+  `src/frontend/assets/brand/`.
+- If you used `{% mdFile %}`, render the Markdown ahead of time or add
+  `markdown-it` back to your own project.
 
 ## [1.1.0] - 2026-07-21
 
@@ -94,4 +72,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Notes
 - Both backends are always scaffolded, so you can switch later without
   re-creating the project. The PHP front controller only serves `.php` endpoint
-  files and the Node one only `.js`, so they coexist without conflict.
+  files and the Node one only `.js`, so they coexist without conflict.
+
+## [1.0.2]
+
+- Previous release (PHP backend only).
+
+[1.1.0]: https://github.com/Rhaastrake/Nibula/releases/tag/v1.1.0
+[1.0.2]: https://github.com/Rhaastrake/Nibula/releases/tag/v1.0.2

package/README.md

@@ -21,7 +21,7 @@ Building a website from scratch involves a lot of moving parts: templating, buil
 - 🪶 **Lightweight by default** — SCSS frameworks can be filtered so you ship only what you actually use
 - 🌍 **Open source** — free to use, free to modify, free to share
 
-![Version](https://img.shields.io/badge/version-1.1.3-blue)
+![Version](https://img.shields.io/badge/version-1.2.0-blue)
 ![License](https://img.shields.io/badge/license-Apache--2.0-blue)
 ![Eleventy](https://img.shields.io/badge/11ty-v3.1.2-black)
 
@@ -44,9 +44,13 @@ Nibula ships with a clean, opinionated layout so beginners are never lost. But i
 
 ## Prerequisites
 
+### Required
+
 * **Node.js**: v18.0.0 or higher — **always required** (the Nibula CLI, the build, and the optional Node backend all run on Node)
 * **Composer**: **only required if you choose the PHP backend**, to install its PHP dependencies. If you pick the **Node** backend, Composer is never used — you can skip installing it entirely.
-* *Optional:* the **Better Nunjucks** VS Code extension by Ed Heltzel
+### Recomended
+* *Suggested:* **Better Nunjucks** VS Code extension by Ed Heltzel
+* *Suggester:* **Material Icon Theme** VS Code extension by Philipp Kief
 
 ## Installation
 
@@ -88,7 +92,7 @@ Run these from anywhere inside a project (except `nib new`, which you run wherev
 | `nib clean` | Remove the output directory |
 | `nib update` | Update the CLI to the latest version |
 
-Before scaffolding, nib new checks the npm registry for a newer version and offers to update first. If you accept, Nibula updates itself and then creates the project with the new version automatically — no need to re-run the command. If the registry is unreachable, the check is skipped and creation proceeds normally.
+Before scaffolding, `nib new` checks the npm registry for a newer version and offers to update first (via `nib update`). If the registry is unreachable, the check is skipped and creation proceeds normally.
 
 ## Managing pages
 

package/bin/create.js

@@ -5,7 +5,7 @@ const path = require('path');
 const readline = require('readline');
 const { writeSync } = require('fs');
 const { spawnSync } = require('child_process');
-const { color } = require('../_tools/modules/constants');
+const { color } = require('../tools/modules/constants');
 
 // ── PATHS ────────────────────────────────────────────────────────────────────
 
@@ -75,7 +75,7 @@ const FRONTEND_EXCLUDE = {
 };
 
 const CREATE_DIRS = [
-    'src/frontend/_routes',
+    'src/frontend/routes',
 ];
 
 // Backend files that belong to exactly one backend, matched by basename.
@@ -148,7 +148,7 @@ src/backend/cache/
 
 const PROJECT_PACKAGE = {
     name:      path.basename(targetDir),
-    version:   '0.0.0',
+    version:   '1.0.0',
     private:   true,
     outputDir: 'out',
     "scripts": {
@@ -170,7 +170,6 @@ const PROJECT_PACKAGE = {
         'bootstrap-icons':    '^1.13.1',
         'bulma':              '^1.0.4',
         'foundation-sites':   '^6.9.0',
-        'github-markdown-css': '^5.9.0',
         'glob':               '^13.0.6',
         'uikit':              '^3.25.13',
     },

package/bin/nibula.js

@@ -5,20 +5,19 @@ const path = require('path');
 const https = require('https');
 const readline = require('readline');
 const { spawnSync } = require('child_process');
-const { findProjectRoot, color, NOT_INSIDE_PROJECT_MESSAGE } = require('../_tools/modules/constants');
+const { findProjectRoot, color, NOT_INSIDE_PROJECT_MESSAGE } = require('../tools/modules/constants');
 
 const pkg = require('../package.json');
 
 const [, , cmd, ...rest] = process.argv;
 
 const CREATE = path.join(__dirname, 'create.js');
-const ASSISTANT = path.join(__dirname, '..', '_tools', 'assistant.js');
-const BUILDJS   = path.join(__dirname, '..', '_tools', 'buildJs.js');
-const CLEAN     = path.join(__dirname, '..', '_tools', 'cleanOutput.js');
+const ASSISTANT = path.join(__dirname, '..', 'tools', 'assistant.js');
+const BUILDJS   = path.join(__dirname, '..', 'tools', 'buildJs.js');
+const CLEAN     = path.join(__dirname, '..', 'tools', 'cleanOutput.js');
 
 const REGISTRY = 'https://registry.npmjs.org/nibula/latest';
 const CHECK_TIMEOUT = 2500;
-const SKIP_FLAG = '--skip-update-check';
 
 function run(script, args) {
     const res = spawnSync('node', [script, ...args], {
@@ -140,32 +139,6 @@ function updateGlobal(version) {
     return res.status ?? 0;
 }
 
-function globalNibulaPath() {
-    const res = spawnSync('npm', ['root', '-g'], {
-        encoding: 'utf8',
-        shell: process.platform === 'win32',
-    });
-    if (res.status !== 0 || !res.stdout) return null;
-    const candidate = path.join(res.stdout.trim(), 'nibula', 'bin', 'nibula.js');
-    return fs.existsSync(candidate) ? candidate : null;
-}
-
-// Riesegue il comando con la versione appena installata: questo processo ha
-// ancora in memoria il codice vecchio, quindi non può scaffoldare da solo.
-function reexecAfterUpdate(args) {
-    const target = globalNibulaPath();
-    if (!target) {
-        console.error(`${color.red}Could not locate the updated Nibula installation.${color.reset}`);
-        console.error(`Run "nib new ${args[1]}" again to continue.`);
-        return 1;
-    }
-    const res = spawnSync(process.execPath, [target, ...args, SKIP_FLAG], {
-        stdio: 'inherit',
-        cwd: process.cwd(),
-    });
-    return res.status ?? 0;
-}
-
 function findExistingProject(baseDir, projectName) {
     let entries;
     try {
@@ -203,37 +176,33 @@ ${color.yellow}nib update${color.reset}               Update to the latest versi
 }
 
 async function main() {
+    const info = await checkVersion();
     switch (cmd) {
         case 'new': {
-            const args = rest.filter((a) => a !== SKIP_FLAG);
-            const skipCheck = rest.includes(SKIP_FLAG);
-
-            if (!args[0]) {
+            if (!rest[0]) {
                 console.error('Missing project name. Usage: nib new <project-name>');
                 process.exit(1);
             }
-
-            if (!skipCheck) {
-                const info = await checkVersion();
-                if (info.behind) {
-                    console.log(`\nA newer version of Nibula is available: ${info.current} → ${info.latest}`);
-                    if (process.stdin.isTTY) {
-                        const answer = await ask('Update before creating the project? [Y/n] ');
-                        if (answer === '' || answer === 'y' || answer === 'yes') {
-                            const code = updateGlobal(info.latest);
-                            if (code !== 0) process.exit(code);
-                            console.log(`\n${color.green}Updated.${color.reset} Continuing with the new version...\n`);
-                            process.exit(reexecAfterUpdate(['new', args[0]]));
+            if (info.behind) {
+                console.log(`\nA newer version of Nibula is available: ${info.current} → ${info.latest}`);
+                if (process.stdin.isTTY) {
+                    const answer = await ask('Update before creating the project? [Y/n] ');
+                    if (answer === '' || answer === 'y' || answer === 'yes') {
+                        const code = updateGlobal(info.latest);
+                        if (code === 0) {
+                            console.log(`\nUpdated. Re-run "nib new ${rest[0]}" to scaffold with the latest version.`);
                         }
-                    } else {
-                        console.log('Run "nib update" to update.\n');
+                        process.exit(code);
                     }
+                } else {
+                    console.log('Run "nib update" to update.\n');
                 }
             }
 
-            const existing = findExistingProject(process.cwd(), args[0]);
+            // Controllo progetto già esistente con lo stesso "name" nel package.json
+            const existing = findExistingProject(process.cwd(), rest[0]);
             if (existing) {
-                console.log(`\n${color.yellow}A project named "${args[0]}" already exists:${color.reset} ${existing}`);
+                console.log(`\n${color.yellow}A project named "${rest[0]}" already exists:${color.reset} ${existing}`);
                 let overwrite = false;
                 if (process.stdin.isTTY) {
                     const answer = await ask('Do you want to overwrite it? [y/N] ');
@@ -245,6 +214,7 @@ async function main() {
                     console.log('Stopped creating the new project');
                     process.exit(0);
                 }
+                // Sovrascrittura: cancello completamente la cartella preesistente
                 try {
                     fs.rmSync(existing, { recursive: true, force: true });
                     console.log(`${color.green}Removed existing project.${color.reset}`);
@@ -254,7 +224,7 @@ async function main() {
                 }
             }
 
-            run(CREATE, [args[0]]);
+            run(CREATE, [rest[0]]);
             break;
         }
         case 'cli': {
@@ -283,7 +253,6 @@ async function main() {
             break;
         }
         case 'update': {
-            const info = await checkVersion();
             if (info.latest !== null && !info.behind) {
                 console.log(`Already on the latest version (${info.current}).`);
                 process.exit(0);
@@ -296,12 +265,15 @@ async function main() {
         case '--help':
         case 'h':
         case '-h': {
-            usage(pkg.version);
+            usage(info.current);
+            if (info.behind) {
+                console.log(`A newer version is available: ${info.current} → ${info.latest}. Run "nib update".`);
+            }
             break;
         }
         default:
             console.error(`${color.red}\nUnknown command:${color.reset} ${cmd}`);
-            usage(pkg.version);
+            usage(info.current);
             process.exit(1);
     }
 }

package/docs/Assistant CLI.md

@@ -31,7 +31,7 @@ For a page named `my-page`, the following files are created:
 |---|---|
 | `src/frontend/scss/pages/myPage.scss` | SCSS entry point |
 | `src/frontend/js/pages/myPage.js` | JS entry point |
-| `src/frontend/_routes/my-page.njk` | Nunjucks template |
+| `src/frontend/routes/my-page.njk` | Nunjucks template |
 
 It also adds an `elif` block in `page-components.njk` and a stub entry in `site.json`:
 

package/docs/Components.md

@@ -43,18 +43,6 @@ Add a new `{% elif %}` block for each page, listing its components in order. If
 
 > ⚠️ If you move or delete a component, always update `page-components.njk` or the site will break
 
-### Using Markdown files in components
-
-You can also render a `.md` file directly inside any `.njk` component using the `mdFile` shortcode:
-
-```njk
-{% mdFile "docs/your-file.md" %}
-```
-
-The path is relative to the project root (where `.eleventy.js` lives).
-
-> ⚠️ The file is read at build time — changes to the `.md` file trigger a rebuild in watch mode.
-
 ## Nest components
 
 A component can include other components. This is useful for breaking complex sections into smaller, reusable pieces.
@@ -77,11 +65,12 @@ Header and footer live in `src/frontend/components/global/` and are automaticall
 
 All values defined in `src/frontend/data/site.json` are globally available in every component via `{{ site.* }}`
 
-### site.json <small>(`src/data/`)</small>
+### site.json <small>(`src/frontend/data/`)</small>
 ```json
 {
   "title": "My Site",
-  "logo": "/img/logo.png",
+  "theme": "dark",
+  "logo": "/assets/brand/logo.svg",
   "legal": {
     "privacy": "/privacy"
   }

package/docs/Creating pages.md

@@ -9,7 +9,7 @@ For a page named `my-page`:
 
 | File | Purpose |
 |---|---|
-| `src/frontend/_routes_/my-page.njk` | Template with front matter |
+| `src/frontend/routes/my-page.njk` | Template with front matter |
 | `src/frontend/scss/pages/myPage.scss` | Imports framework + modules |
 | `src/frontend/js/pages/myPage.js` | Imports JS modules |
 
@@ -31,7 +31,7 @@ The URL is the kebab-case name (`/my-page/`). The `title` in the front matter is
 
 ## Subpages (nested URLs)
 
-To create a URL like `domain.it/about/team`, edit the `permalink` in `src/frontend/_routes/team.njk` and add the parent segment before the final slash:
+To create a URL like `domain.it/about/team`, edit the `permalink` in `src/frontend/routes/team.njk` and add the parent segment before the final slash:
 
 ```njk
 ---
@@ -45,9 +45,9 @@ The parent path (`about`) does **not** need to exist as a real page — it's jus
 
 | Goal URL | permalink value | File |
 |---|---|---|
-| `/team/` | `/team/` | `_routes/team.njk` |
-| `/about/team/` | `/about/team/` | `_routes/team.njk` |
-| `/company/about/team/` | `/company/about/team/` | `_routes/team.njk` |
+| `/team/` | `/team/` | `routes/team.njk` |
+| `/about/team/` | `/about/team/` | `routes/team.njk` |
+| `/company/about/team/` | `/company/about/team/` | `routes/team.njk` |
 
 ## SEO
 

package/docs/Head and SEO.md

@@ -14,12 +14,7 @@ Global settings live in `src/frontend/data/site.json` and are available everywhe
   "url": "https://yoursite.com",
   "lang": "en",
   "author": "Name and surname",
-  "data_bs_theme": "dark",
-  "theme_color": {
-    "light": "#ffffff",
-    "dark": "#0d1117"
-  },
-  "favicon": "/assets/brand/favicon.svg",
+  "theme": "dark",
   "logo": "/assets/brand/logo.svg",
   "legal": {
     "privacy": "",
@@ -43,9 +38,8 @@ Global settings live in `src/frontend/data/site.json` and are available everywhe
 | `domain` / `url` | Canonical URLs, `og:url`, JSON-LD |
 | `lang` | HTML `lang` attribute |
 | `author` | Meta author and JSON-LD author |
-| `data_bs_theme` | Bootstrap color scheme (`light` / `dark`) |
-| `theme_color` | Browser UI / PWA color, per scheme (`light` / `dark`) |
-| `favicon` | Path to the favicon |
+| `theme` | Site color scheme (`light` / `dark`) — sets `data-theme`, `data-bs-theme` and `color-scheme` |
+| `theme_color` | Browser UI / PWA bar color — should match the chosen `theme` |
 | `logo` | Path to the logo, also used as social image |
 | `legal.privacy` / `cookie` / `cookieControls` / `terms` | Legal page URLs |
 | `legal.copyright.year` / `text` | Footer copyright |
@@ -93,16 +87,44 @@ Global values are defaults, not duplicates. A page value is used when present; o
 
 `noindex` and `canonical` have no global default: `noindex` defaults to indexable behavior, `canonical` is computed from the URL. They exist per-page only.
 
-## theme_color
+## Theme
 
-Two tags are emitted so the browser bar follows the user's system scheme:
+`theme` is a single fixed value that drives the whole site:
 
 ```njk
-<meta name="theme-color" content="{{ site.theme_color.light }}" media="(prefers-color-scheme: light)">
-<meta name="theme-color" content="{{ site.theme_color.dark }}" media="(prefers-color-scheme: dark)">
+<html data-theme="{{ site.theme }}" data-bs-theme="{{ site.theme }}">
+<meta name="color-scheme" content="{{ site.theme }}">
+<meta name="theme-color" content="{{ site.theme_color }}">
 ```
 
-This is independent from `data_bs_theme`, which controls the Bootstrap theme, not the browser UI.
+| Attribute | Purpose |
+|---|---|
+| `data-theme` | Your own hook — target it in SCSS to define theme variables |
+| `data-bs-theme` | Bootstrap's color mode. Ignored (harmless) if you use another framework |
+| `color-scheme` | Standard CSS — makes scrollbars, form controls and autofill follow the theme |
+| `theme-color` | Color of the browser UI bar on mobile |
+
+Keep `theme` and `theme_color` consistent: a `dark` theme with a white `theme_color` gives a white browser bar over a dark page.
+
+See the SCSS docs for how to hook your variables to `data-theme`.
+
+## Favicon
+
+The three favicon tags are hardcoded in `base.njk`. To change the icons, replace the files in `src/frontend/assets/brand/` keeping the same names:
+
+```html
+<link rel="icon" type="image/svg+xml" href="/assets/brand/favicon.svg">
+<link rel="icon" type="image/png" sizes="32x32" href="/assets/brand/favicon-32.png">
+<link rel="apple-touch-icon" sizes="180x180" href="/assets/brand/apple-touch-icon.png">
+```
+
+| File | Purpose |
+|---|---|
+| `favicon.svg` | Modern browsers, scales to any size |
+| `favicon-32.png` | Fallback for older browsers and some crawlers |
+| `apple-touch-icon.png` | iOS home screen icon — 180×180, must be opaque (iOS renders transparency as black) |
+
+> ⚠️ Without `apple-touch-icon.png`, iOS uses a screenshot of the page as the home screen icon.
 
 ## AI & SEO bots
 

package/docs/Javascript.md

@@ -48,6 +48,4 @@ In TypeScript, omit the extension:
 
 ```ts
 import { exampleModule } from '../modules/exampleModule';
-```
-
-> ⚠️ Files inside `_tools/` run directly in Node.js without a bundler — use CommonJS (`require` / `module.exports`) there, not ESM.
+```

package/docs/Styling with SCSS.md

@@ -7,6 +7,7 @@ Each page has its own SCSS entry point in `src/frontend/scss/pages/`
 It must contain `_root.scss` + other modules like `_global.scss` or any other one that you need and its own specific css rules
 
 `_root.scss` uses `@use` to enable namespaced access (`root.$var`); other modules use `@import` as they don't expose variables.
+
 ### examplePage.scss <small>(`src/frontend/scss/pages/`)</small>
 ```scss
 //==========================
@@ -39,7 +40,9 @@ header {
   height: root.$header-height;
 }
 ```
+
 ## Scss modules
+
 You can create your custom css modules by creating a new `.scss` file in `src/frontend/scss/modules/` (the name of the file must start with `_`)
 
 You can create subfolders if you want to refactor the structure, but be sure to update the relative paths in the pages that import them
@@ -70,7 +73,7 @@ body {
 |---|---|
 | `_root.scss` | Global variables (colors, spacing) |
 | `_global.scss` | Site-wide base rules and frameworks |
-| `_typography.scss` | Font rules
+| `_typography.scss` | Font rules |
 | `_header.scss` | Header styles |
 | `_footer.scss` | Footer styles |
 | `_mobile.scss` | Media query rules |
@@ -84,7 +87,6 @@ You can choose one or none of them (more than 1 works, but you may get in variou
 
 To enable/disable them you have to modify 3 files around the project by just commenting them
 
-
 ### 1. _global.scss <small>(`src/frontend/scss/modules/`)</small>
 ```scss
 @import "../modules/frameworks/bootstrap";
@@ -109,7 +111,7 @@ To enable/disable them you have to modify 3 files around the project by just com
 {# Bulma — no JS needed #}
 ```
 
-### 3. .eleventy.js
+### 3. eleventy.config.js
 
 ```javascript
 eleventyConfig.addPassthroughCopy({
@@ -128,8 +130,12 @@ eleventyConfig.addPassthroughCopy({
 });
 ```
 
+> ⚠️ Changes to `eleventy.config.js` are not picked up while the dev server is running — restart it.
+
 ### Reducing bundle size
+
 To reduce the bundle size, open the corresponding framework file (`src/frontend/scss/modules/frameworks/`) and comment out any modules you don't need
+
 ```scss
 @import "bootstrap/scss/card"; // Cards
 @import "bootstrap/scss/carousel"; // Carousel