nibula 1.5.3 → 1.6.1

package/CHANGELOG.md

@@ -5,6 +5,44 @@ 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.6.1] - 2026-08-06
+
+### Fixed
+- `src/frontend/scss/pages/prova.scss` was left in the template and shipped with 1.6.0, so every new project started with a stylesheet for a page that doesn't exist — no route, no script, no entry in `pages.json`.
+- Open Graph and Twitter Card tags read `seo.title` and `seo.description` directly, with none of the fallbacks the `<title>` and meta description already had. A page that left those fields empty in `pages.json` published an empty social preview — exactly the case the fallbacks exist for. They now follow the same chain.
+- `data-theme` was missing from the `<html>` tag. It is documented as the hook to target in SCSS for theme variables, so a selector written against it never matched.
+
+## [1.6.0] - 2026-08-06
+
+### Breaking
+- Per-page settings must move out of `site.json`. Take the block under the `pages`
+  key and make it the root object of a new `src/frontend/data/pages.json`, then
+  update `base.njk`, `sitemap.njk` and `llms.njk` to read `pages[title]` instead of
+  `site.pages[title]`. Without `pages.json` the assistant reports the missing file
+  and stops.
+- SCSS and JS import paths change with the `_root`, `_global` and `global` moves.
+  Update the `@use` and `@import` lines in your page entry points accordingly.
+- Existing projects keep working until you run `npm install nibula@latest` inside
+  them: commands now delegate to the project's own copy, so an old project keeps
+  running the version it was built with.
+
+### Changed
+- **Per-page settings moved from `site.json` to a new `pages.json`.** They were nested under a `pages` key in the same file the CLI writes on every page operation; splitting them means a syntax error in one page's record no longer makes the whole site configuration unreadable. Access changes from `{{ site.pages[title] }}` to `{{ pages[title] }}`, and the CLI now reads and writes `pages.json` only.
+- Commands run inside a project now execute the project's own Nibula, taken from its `node_modules`, instead of the globally installed one. `nib cli` typed in a terminal used to run the global copy against local files, so a project scaffolded with an older version could be operated on by a newer CLI expecting a different structure. When the two versions differ, the one being used is reported before the command runs, and the assistant's title shows it as well.
+- `_root.scss` and `_global.scss` moved out of `scss/modules/`. They are not modules — every page imports them and nothing else does — so they now sit at the root of `scss/`.
+- `global.js` and `global.ts` moved out of their `modules/` folders, for the same reason.
+- Import paths updated across existing modules, pages and scaffold templates to match both moves.
+- `base.njk` applies the `url` filter to per-page CSS and JS, to the favicons and to the framework scripts. Without it these paths ignore `pathPrefix`, so every asset 404s on a site published under a subpath — GitHub Pages being the common case.
+- Documentation updated throughout for the new structure and the `site.json` / `pages.json` split.
+
+### Fixed
+- TypeScript page entry points imported modules with a `.js` extension.
+- `logo` was nested inside `legal` in `site.json`, so `{{ site.logo }}` resolved to nothing in the header, the footer, the Open Graph image and the JSON-LD publisher block. It now sits at the root, where the templates already looked for it.
+
+### Removed
+- `legal.cookieControls` from `site.json`.
+- Preconnect hint to `cdn.jsdelivr.net` in `base.njk`. The project loads its framework from `node_modules` through passthrough copy, so the hint opened a TCP and TLS connection to a host that was never used.
+
 ## [1.5.3] - 2026-08-05
 
 ### Fixed

package/README.md

@@ -106,3 +106,5 @@ Thanks for giving Nibula a try.
 It's a one-person project, so every bit of feedback counts more than you'd think: if something breaks, if the documentation isn't clear, or if a feature is missing, open an [issue](https://github.com/Rhaastrake/Nibula/issues) — even just to tell me what you built with it.
 
 If Nibula was useful to you, leaving a ⭐ on the repository is the easiest way to help other people find it.
+
+You can support the project by [buying me a coffee](https://paypal.me/rhaastrake) ☕🫡

package/bin/create.js

@@ -78,7 +78,7 @@ const CREATE_DIRS = [];
 
 // Backend files that belong to exactly one backend, matched by basename.
 // Everything else (migrations, .htaccess, web.config, README, ...) is shared.
-const NODE_ONLY_FILES = new Set(['package.json', 'backend-node.service.example']);
+const NODE_ONLY_FILES = new Set(['package.json']);
 const PHP_ONLY_FILES  = new Set(['composer.json', 'composer.lock']);
 const PHP_ONLY_DIRS   = new Set(['vendor']);
 // Runtime artifacts that must never be copied from the template, either way.

package/bin/delegate.js

@@ -0,0 +1,58 @@
+const fs = require('fs');
+const path = require('path');
+const { spawnSync } = require('child_process');
+const { color } = require('../tools/lib/colors');
+const { message } = require('../tools/lib/logger');
+
+const PACKAGE_NAME = 'nibula';
+const NODE_MODULES = 'node_modules';
+const ENTRY_FILE = path.join('bin', 'nibula.js');
+const PACKAGE_FILE = 'package.json';
+const LOCAL_FLAG = 'NIBULA_LOCAL';
+const LOCAL_FLAG_VALUE = '1';
+
+const globalVersion = require(`../${PACKAGE_FILE}`).version;
+
+function realPath(target) {
+    try {
+        return fs.realpathSync(target);
+    } catch {
+        return null;
+    }
+}
+
+function readVersion(packageRoot) {
+    try {
+        return JSON.parse(fs.readFileSync(path.join(packageRoot, PACKAGE_FILE), 'utf8')).version;
+    } catch {
+        return null;
+    }
+}
+
+function delegateToLocal(projectRoot) {
+    if (process.env[LOCAL_FLAG] === LOCAL_FLAG_VALUE) return;
+
+    const localRoot = realPath(path.join(projectRoot, NODE_MODULES, PACKAGE_NAME));
+    const selfRoot = realPath(path.join(__dirname, '..'));
+
+    if (!localRoot || localRoot === selfRoot) return;
+
+    const localEntry = path.join(localRoot, ENTRY_FILE);
+    if (!fs.existsSync(localEntry)) return;
+
+    const localVersion = readVersion(localRoot);
+
+    if (localVersion && localVersion !== globalVersion) {
+        console.log(`${color.dim}${message('cli.usingLocalVersion', { local: localVersion, global: globalVersion })}${color.reset}`);
+    }
+
+    const result = spawnSync(process.execPath, [localEntry, ...process.argv.slice(2)], {
+        stdio: 'inherit',
+        cwd: process.cwd(),
+        env: { ...process.env, [LOCAL_FLAG]: LOCAL_FLAG_VALUE },
+    });
+
+    process.exit(result.status ?? 0);
+}
+
+module.exports = { delegateToLocal };

package/bin/nibula.js

@@ -8,6 +8,7 @@ const { spawnSync } = require('child_process');
 const { findProjectRoot, NOT_INSIDE_PROJECT_MESSAGE } = require('../tools/lib/paths');
 const { color } = require('../tools/lib/colors');
 const { message } = require('../tools/lib/logger');
+const { delegateToLocal } = require('./delegate');
 
 const pkg = require('../package.json');
 
@@ -48,27 +49,9 @@ function requireOutsideProject() {
     process.exit(1);
 }
 
-function maybeDelegateToLocal(root) {
-    const local = path.join(root, 'node_modules', 'nibula', 'bin', 'nibula.js');
-    if (!fs.existsSync(local)) return;
-
-    let localReal;
-    let selfReal;
-    try { localReal = fs.realpathSync(local); } catch { return; }
-    try { selfReal = fs.realpathSync(__filename); } catch { selfReal = __filename; }
-
-    if (localReal !== selfReal) {
-        const res = spawnSync('node', [localReal, ...process.argv.slice(2)], {
-            stdio: 'inherit',
-            cwd: process.cwd(),
-        });
-        process.exit(res.status ?? 0);
-    }
-}
-
 function enterProject() {
     const root = requireProjectRoot();
-    maybeDelegateToLocal(root);
+    delegateToLocal(root);
     return root;
 }
 
@@ -198,6 +181,7 @@ function findExistingProject(baseDir, projectName) {
 
 function usage(currentVersion) {
     console.log(`
+
 ${color.bold}${color.cyan}Nibula (${currentVersion})${color.reset} ${color.bold}by Michele Garofalo${color.reset}
 
 ${color.yellow}nib new <project-name>${color.reset}   Create your new project
@@ -206,6 +190,7 @@ ${color.yellow}nib run${color.reset}                  Start the dev server and b
 ${color.yellow}nib build${color.reset}                Build the site out folder to publish
 ${color.yellow}nib clean${color.reset}                Remove the output directory
 ${color.yellow}nib update${color.reset}               Update to the latest version
+
 `);
 }
 

package/docs/Assistant CLI.md

@@ -33,7 +33,7 @@ For a page named `my-page`, the following files are created:
 | `src/frontend/js/pages/myPage.js` | JS entry point |
 | `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`:
+It also adds an `elif` block in `page-components.njk` and a stub entry in `pages.json`:
 
 ```json
     "myPage": {
@@ -53,11 +53,11 @@ It also adds an `elif` block in `page-components.njk` and a stub entry in `site.
 
 ## Remove page
 
-Deletes all source files for the page and cleans up the output directory, `page-components.njk`, and `site.json`.
+Deletes all source files for the page and cleans up the output directory, `page-components.njk`, and `pages.json`.
 
 ## Rename page
 
-Renames all three source files, updates the `elif` block in `page-components.njk`, and renames the record in `site.json` while preserving all existing fields.
+Renames all three source files, updates the `elif` block in `page-components.njk`, and renames the record in `pages.json`. Nothing inside the record is touched — your SEO title, description and CDN links stay exactly as you wrote them.
 
 ## Configure output path
 

package/docs/Components.md

@@ -28,8 +28,8 @@ To render a component inside a page, navigate to `src/frontend/layouts/` and edi
 {% include "welcome.njk" %}
 
 {% elif title == "examplePage" %}
-{% include "exampleComponent1.njk" %}
-{% include "subfolder/exampleComponent2.njk" %}
+{% include "example-component-1.njk" %}
+{% include "subfolder/example-component-2.njk" %}
 
 {% else %}
 {% include "404/_404.njk" %}
@@ -50,8 +50,8 @@ A component can include other components. This is useful for breaking complex se
 ### exampleComponent.njk
 ```js
 <section class="hero">
-  {% include "ui/heroTitle.njk" %}
-  {% include "ui/heroButton.njk" %}
+  {% include "hero/hero-title.njk" %}
+  {% include "hero/hero-button.njk" %}
 </section>
 ```
 
@@ -67,14 +67,23 @@ All values defined in `src/frontend/data/site.json` are globally available in ev
 
 ### site.json <small>(`src/frontend/data/`)</small>
 ```json
-{
-  "title": "My Site",
-  "theme": "dark",
-  "logo": "/assets/brand/logo.svg",
-  "legal": {
-    "privacy": "/privacy"
+"site_name": "Site name",
+"title": "Site title",
+"description": "Site description",
+"keywords": "keyword1, keyword2, keyword3",
+"domain": "yoursite.com",
+"url": "https://yoursite.com",
+"lang": "en",
+"author": "Name and surname",
+"logo": "/assets/brand/logo.svg",
+"legal": {
+  "privacy": "", // This is supposed to contain a link
+  "cookie": "", // This is supposed to contain a link
+  "terms": "", // This is supposed to contain a link
+  "copyright": {
+    "year": "2026",
+    "text": "All rights reserved."
   }
-}
 ```
 
 ### Usage in any `.njk` file
@@ -82,4 +91,51 @@ All values defined in `src/frontend/data/site.json` are globally available in ev
 <p>{{ site.title }}</p>
 <a href="{{ site.legal.privacy }}">Privacy Policy</a>
 <img src="{{ site.logo }}" alt="{{ site.title }}">
-```
+```
+
+## Your own data files
+
+`site.json` isn't special: **any** `.json` file you drop in `src/frontend/data/` becomes a global variable, and the variable takes the name of the file.
+
+Create `test.json`, put anything you want inside it, and every key is reachable as `test.yourKey` — no import, no configuration, no restart.
+
+### test.json <small>(`src/frontend/data/`)</small>
+```json
+{
+  "testMessage": "This is a test"
+}
+```
+
+### Usage in any `.njk` file
+```js
+<p>{{ test.testMessage }}</p>
+```
+
+Renders as:
+```html
+<p>This is a test</p>
+```
+
+That's the whole rule: **file name = variable name, keys inside = what you write after the dot.** `site.json` gives you `site.title` for exactly the same reason.
+
+Values can be anything JSON allows, so a list lets you loop instead of copying markup:
+
+```json
+{
+  "testMessage": "This is a test",
+  "links": [
+    { "label": "Home",    "url": "/" },
+    { "label": "Contact", "url": "/contact/" }
+  ]
+}
+```
+
+```js
+{% for link in test.links %}
+  <a href="{{ link.url }}">{{ link.label }}</a>
+{% endfor %}
+```
+
+Subfolders create nested names: `data/shop/products.json` becomes `{{ shop.products }}`.
+
+> ⚠️ Don't reuse a name that already exists. Another file named `site.json` in a subfolder overwrites the original one silently, with no error to point you at the cause.

package/docs/Creating pages.md

@@ -11,16 +11,16 @@ For a page named `my-page`:
 |---|---|
 | `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 |
+| `src/frontend/js/pages/myPage.js` | Imports JS/TS modules |
 
 ## Adding content
 
-1. Create a component in `src/frontend/components/` (e.g. `_myPage.njk`)
+1. Create a component in `src/frontend/components/` (e.g. `my-component.njk`)
 2. Include it in `src/frontend/layouts/page-components.njk` inside the generated `elif` block:
 
 ```njk
 {% elif title == "myPage" %}
-  {% include "_myPage.njk" %}
+  {% include "my-component.njk" ignore missing %}
 ```
 
 See **Components** DOC file for more info
@@ -51,15 +51,20 @@ The parent path (`about`) does **not** need to exist as a real page — it's jus
 
 ## SEO
 
-The CLI creates a stub entry in `src/frontend/data/site.json`. Fill it in:
+The CLI creates a stub entry in `src/frontend/data/pages.json`. Fill it in:
 
 ```json
-"myPage": {
-  "seo": {
-    "title": "My Page | Site Name",
-    "description": "Page description"
-  }
-}
-```
-
-See **Head & SEO** for all available options.
+    "myPage": {
+      "seo": {
+        "title": "My Page",
+        "description": "Description",
+        "keywords": "",
+        "noindex": false,
+        "canonical": ""
+      },
+      "cdn": {
+        "css": [],
+        "js": []
+      }
+    }
+```

package/docs/Head and SEO.md

@@ -1,6 +1,6 @@
 # Head & SEO
 
-Global settings live in `src/frontend/data/site.json` and are available everywhere via `{{ site.* }}`.
+Global settings live in `src/frontend/data/pages.json` and are available everywhere via `{{ pages.* }}`.
 
 ## Global fields
 
@@ -46,10 +46,10 @@ Global settings live in `src/frontend/data/site.json` and are available everywhe
 
 ## Per-page SEO and CDN
 
-Each page is keyed by its camelCase `title` from the front matter:
+Per-page settings live in `src/frontend/data/pages.json`, available via `{{ pages.* }}`. Each page is keyed by its camelCase `title` from the front matter, at the root of the file:
 
 ```json
-"pages": {
+{
   "examplePage": {
     "seo": {
       "title": "Example Page",
@@ -113,14 +113,15 @@ See the SCSS docs for how to hook your variables to `data-theme`.
 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">
+<link rel="icon" type="image/svg+xml" href="{{ '/assets/brand/favicon.svg' | url }}">
+<link rel="icon" type="image/png" sizes="32x32" href="{{ '/assets/brand/favicon-32.png' | url }}">
+<link rel="apple-touch-icon" sizes="180x180" href="{{ '/assets/brand/apple-touch-icon.png' | url }}">
 ```
 
 | File | Purpose |
 |---|---|
 | `favicon.svg` | Modern browsers, scales to any size |
+| `favicon-48.png` | Fallback for older browsers and some crawlers |
 | `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) |
 

package/docs/Javascript.md

@@ -11,7 +11,8 @@ Import only what the page needs.
 ### examplePage.js <small>(`src/frontend/js/pages/`)</small>
 
 ```js
-import '../modules/global.js';
+import '../global.js';
+
 // import { initExampleModule } from '../modules/exampleModule.js';
 
 document.addEventListener("DOMContentLoaded", () => {
@@ -25,9 +26,9 @@ document.addEventListener("DOMContentLoaded", () => {
 
 Some code has to run on every page: a header menu, a theme toggle, a cookie banner. Repeating it in every page entry point means you'll eventually forget it on one of them, and the bug only shows up on that single page.
 
-That's what `global.js` is for. It lives in `src/frontend/js/modules/`, every page entry point imports it, and it takes care of running the shared modules.
+That's what `global.js` is for. It lives in `src/frontend/js/`, every page entry point imports it, and it takes care of running the shared modules.
 
-### global.js <small>(`src/frontend/js/modules/`)</small>
+### global.js <small>(`src/frontend/js/`)</small>
 
 ```js
 // import { initExampleModule } from './exampleModule.js';
@@ -38,14 +39,15 @@ function initGlobal() {
 
 // Global logic here
 
-// Do not touch this line
+// Do not touch
+// This instruction starts global.js itself
 document.addEventListener('DOMContentLoaded', initGlobal);
 ```
 
 Pages import it without curly braces, since there is nothing to export — the module runs on its own as soon as it's part of the bundle:
 
 ```js
-import '../modules/global.js';
+import '../global.js';
 ```
 
 Note that the import path inside `global.js` is `'./exampleModule.js'` and not `'../modules/exampleModule.js'`: `global.js` already sits in the modules folder, next to the modules it imports.
@@ -56,9 +58,8 @@ A responsive header has a burger button that opens the navigation on small scree
 
 Write the behaviour as a normal module:
 
+### header.js <small>(`src/frontend/js/modules/`)</small>
 ```js
-// src/frontend/js/modules/header.js
-
 export function initHeader() {
     const toggle = document.querySelector('.menu-toggle');
     const menu = document.querySelector('.menu');
@@ -74,13 +75,14 @@ export function initHeader() {
 Then wire it up once, in `global.js`:
 
 ```js
-import { initHeader } from './header.js';
+import { initHeader } from './modules/header.js';
 
 function initGlobal() {
     initHeader();
 }
 
-// Do not touch this line
+// Do not touch
+// This instruction starts global.js itself
 document.addEventListener('DOMContentLoaded', initGlobal);
 ```
 

package/docs/Styling with SCSS.md

@@ -4,7 +4,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
+It must contain `_root.scss` + any other module 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.
 
@@ -14,9 +14,9 @@ It must contain `_root.scss` + other modules like `_global.scss` or any other on
 // CSS MODULES IMPORTS
 //==========================
 
-@use "../modules/root" as root;
+@use "../root" as root;
 
-@import "../modules/global";
+@import "../global";
 
 //==========================
 // PAGE CUSTOM CSS RULES
@@ -49,7 +49,7 @@ You can create subfolders if you want to refactor the structure, but be sure to
 
 ### _yourModule.scss <small>(`src/frontend/scss/modules/subfolder/`)</small>
 ```scss
-@use '../root' as root;
+@use '../../root' as root;
 
 body {
   background-color: root.$primary;
@@ -71,8 +71,6 @@ body {
 
 | File | Purpose |
 |---|---|
-| `_root.scss` | Global variables (colors, spacing) |
-| `_global.scss` | Site-wide base rules and frameworks |
 | `_typography.scss` | Font rules |
 | `_header.scss` | Header styles |
 | `_footer.scss` | Footer styles |
@@ -87,12 +85,12 @@ 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>
+### 1. _global.scss <small>(`src/frontend/scss/`)</small>
 ```scss
-@import "../modules/frameworks/bootstrap";
-// @import "../modules/frameworks/bulma";
-// @import "../modules/frameworks/foundation";
-// @import "../modules/frameworks/uikit";
+@import "modules/frameworks/bootstrap";
+// @import "modules/frameworks/bulma";
+// @import "modules/frameworks/foundation";
+// @import "modules/frameworks/uikit";
 ```
 
 ### 2. base.njk <small>(`src/frontend/layouts/`)</small>

package/package.json

@@ -1,34 +1,28 @@
 {
   "name": "nibula",
-  "version": "1.5.3",
+  "version": "1.6.1",
   "description": "A beginner-friendly static site generator built on Eleventy that stays close to vanilla HTML, CSS and JS — with a page-management CLI, an optional PHP backend, and SEO files generated for you.",
   "keywords": [
-    "static-site-generator",
-    "ssg",
-    "eleventy",
     "11ty",
+    "beginner-friendly",
     "boilerplate",
-    "starter",
-    "scaffolding",
+    "bootstrap",
+    "bulma",
     "cli",
-    "vanilla",
-    "vanilla-js",
-    "html",
-    "css",
-    "scss",
-    "sass",
+    "deploy-ready",
+    "eleventy-template",
+    "nginx",
     "njk",
-    "nunjucks",
-    "components",
-    "backend",
+    "nodejs",
     "php",
-    "node",
-    "python",
-    "beginner-friendly",
-    "seo",
-    "sitemap",
-    "website-template",
-    "frontend"
+    "rest-api",
+    "sass",
+    "scaffolder",
+    "seo-optimization",
+    "ssg",
+    "static-site-generator",
+    "typescript",
+    "uikit"
   ],
   "author": "Michele Garofalo",
   "license": "Apache-2.0",
@@ -40,6 +34,7 @@
   "bugs": {
     "url": "https://github.com/Rhaastrake/Nibula/issues"
   },
+  "funding": "https://paypal.me/rhaastrake",
   "outputDir": "out",
   "bin": {
     "nib": "bin/nibula.js",

package/src/frontend/components/welcome.njk

@@ -31,6 +31,7 @@
         </a>
       </div>
     </div>
+    <div class="prova">{{ test.prova }}</div>
 <style>
   .layout-container {
     width: 100%;

package/src/frontend/data/pages.json

@@ -0,0 +1,27 @@
+{
+  "404": {
+    "seo": {
+      "title": "404 - Not found",
+      "keywords": "",
+      "noindex": true,
+      "canonical": ""
+    },
+    "cdn": {
+      "css": [],
+      "js": []
+    }
+  },
+  "homepage": {
+    "seo": {
+      "title": "Homepage",
+      "description": "Description",
+      "keywords": "",
+      "noindex": false,
+      "canonical": ""
+    },
+    "cdn": {
+      "css": [],
+      "js": []
+    }
+  }
+}

package/src/frontend/data/site.json

@@ -8,41 +8,14 @@
   "lang": "en",
   "author": "Name and surname",
   "theme": "dark",
+  "logo": "/assets/brand/logo.svg",
   "legal": {
     "privacy": "",
     "cookie": "",
-    "cookieControls": "",
     "terms": "",
     "copyright": {
       "year": "2026",
       "text": "All rights reserved."
     }
-  },
-  "pages": {
-    "404": {
-      "seo": {
-        "title": "404 - Not found",
-        "keywords": "",
-        "noindex": true,
-        "canonical": ""
-      },
-      "cdn": {
-        "css": [],
-        "js": []
-      }
-    },
-    "homepage": {
-      "seo": {
-        "title": "Homepage",
-        "description": "Description",
-        "keywords": "",
-        "noindex": false,
-        "canonical": ""
-      },
-      "cdn": {
-        "css": [],
-        "js": []
-      }
-    }
   }
 }