nibula 1.2.4 → 1.2.6

package/docs/Javascript.md

@@ -1,51 +1,51 @@
-# JavaScript
-
-> Examples use JavaScript, but everything applies equally to TypeScript. The only difference is the file extension (`.ts` instead of `.js`), that imports do **not** include the extension, and that paths use `src/frontend/ts/` instead of `src/frontend/js/`.
-
-## Page JS
-
-Each page has its own JS entry point in `src/frontend/js/pages/`, bundled and minified by esbuild and loaded automatically by `base.njk`.
-
-Import only what the page needs.
-
-### examplePage.js <small>(`src/frontend/js/pages/`)</small>
-
-```js
-// import { initExampleModule } from '../modules/exampleModule.js';
-
-document.addEventListener("DOMContentLoaded", () => {
-    // initExampleModule();
-});
-
-// Page logic here
-```
-
-## Modules
-
-Modules live in `src/frontend/js/modules/`. Modules that interact with the DOM must be called inside `DOMContentLoaded`; others can be called anywhere.
-
-## Adding a module
-
-Create a new `.js` file in `src/frontend/js/modules/`. Subfolders are allowed.
-
-Use ESM syntax — esbuild handles the bundling:
-
-### exampleModule.js <small>(`src/frontend/js/modules/`)</small>
-
-```js
-export function exampleModule() {
-    // Module logic here
-}
-```
-
-Then import it in the pages that need it:
-
-```js
-import { exampleModule } from '../modules/exampleModule.js';
-```
-
-In TypeScript, omit the extension:
-
-```ts
-import { exampleModule } from '../modules/exampleModule';
+# JavaScript
+
+> Examples use JavaScript, but everything applies equally to TypeScript. The only difference is the file extension (`.ts` instead of `.js`), that imports do **not** include the extension, and that paths use `src/frontend/ts/` instead of `src/frontend/js/`.
+
+## Page JS
+
+Each page has its own JS entry point in `src/frontend/js/pages/`, bundled and minified by esbuild and loaded automatically by `base.njk`.
+
+Import only what the page needs.
+
+### examplePage.js <small>(`src/frontend/js/pages/`)</small>
+
+```js
+// import { initExampleModule } from '../modules/exampleModule.js';
+
+document.addEventListener("DOMContentLoaded", () => {
+    // initExampleModule();
+});
+
+// Page logic here
+```
+
+## Modules
+
+Modules live in `src/frontend/js/modules/`. Modules that interact with the DOM must be called inside `DOMContentLoaded`; others can be called anywhere.
+
+## Adding a module
+
+Create a new `.js` file in `src/frontend/js/modules/`. Subfolders are allowed.
+
+Use ESM syntax — esbuild handles the bundling:
+
+### exampleModule.js <small>(`src/frontend/js/modules/`)</small>
+
+```js
+export function exampleModule() {
+    // Module logic here
+}
+```
+
+Then import it in the pages that need it:
+
+```js
+import { exampleModule } from '../modules/exampleModule.js';
+```
+
+In TypeScript, omit the extension:
+
+```ts
+import { exampleModule } from '../modules/exampleModule';
 ```

package/docs/Styling with SCSS.md

@@ -1,142 +1,142 @@
-# Styling with SCSS
-
-## Page CSS
-
-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
-//==========================
-// CSS MODULES IMPORTS
-//==========================
-
-@use "../modules/root" as root;
-
-@import "../modules/global";
-
-//==========================
-// PAGE CUSTOM CSS RULES
-//==========================
-
-body {
-  background-color: root.$primary;
-}
-```
-
-## Global Variables
-
-Instead of using `:root` in your custom modules or pages, the best thing to do is to centralize all your variables in a single file (that will be tree-shaken automatically by Sass)
-
-### _root.scss <small>(`src/frontend/scss/modules/`)</small>
-```scss
-$header-height: 10vh;
-
-// Usage example (in any other file): 
-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
-
-### _yourModule.scss <small>(`src/frontend/scss/modules/subfolder/`)</small>
-```scss
-@use '../root' as root;
-
-body {
-  background-color: root.$primary;
-}
-```
-
-### examplePage.scss
-```scss
-@import "../modules/subfolder/yourModule";
-
-// This page will now inherit the body tag rules
-// If the same property is declared in both, the last imported one wins
-body {
-  color: root.$dark;
-}
-```
-
-### Pre-existing modules
-
-| 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 |
-| `_mobile.scss` | Media query rules |
-| `_animations.scss` | Keyframe animations (`fade-in`, `spin`) |
-
-## CSS Framework
-
-Some of the most popular css frameworks that supports scss with modules are already installed in `node_modules`
-
-You can choose one or none of them (more than 1 works, but you may get in various conflicts)
-
-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";
-// @import "../modules/frameworks/bulma";
-// @import "../modules/frameworks/foundation";
-// @import "../modules/frameworks/uikit";
-```
-
-### 2. base.njk <small>(`src/frontend/layouts/`)</small>
-
-```html
-{# Bootstrap JS #}
-<script src="/js/bootstrap.bundle.min.js" defer></script>
-
-{# Foundation JS #}
-{# <script src="/js/foundation.min.js" defer></script> #}
-
-{# UIkit JS #}
-{# <script src="/js/uikit.min.js" defer></script> #}
-{# <script src="/js/uikit-icons.min.js" defer></script> #}
-
-{# Bulma — no JS needed #}
-```
-
-### 3. eleventy.config.js
-
-```javascript
-eleventyConfig.addPassthroughCopy({
-  // Bootstrap
-  "node_modules/bootstrap/dist/js/bootstrap.bundle.min.js": "js/bootstrap.bundle.min.js",
-  "node_modules/bootstrap-icons/font/fonts": "css/fonts",
-
-  // Foundation
-  // "node_modules/foundation-sites/dist/js/foundation.min.js": "js/foundation.min.js",
-
-  // UIkit
-  // "node_modules/uikit/dist/js/uikit.min.js": "js/uikit.min.js",
-  // "node_modules/uikit/dist/js/uikit-icons.min.js": "js/uikit-icons.min.js",
-
-  // Bulma — CSS only, no JS passthrough needed
-});
-```
-
-> ⚠️ 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
+# Styling with SCSS
+
+## Page CSS
+
+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
+//==========================
+// CSS MODULES IMPORTS
+//==========================
+
+@use "../modules/root" as root;
+
+@import "../modules/global";
+
+//==========================
+// PAGE CUSTOM CSS RULES
+//==========================
+
+body {
+  background-color: root.$primary;
+}
+```
+
+## Global Variables
+
+Instead of using `:root` in your custom modules or pages, the best thing to do is to centralize all your variables in a single file (that will be tree-shaken automatically by Sass)
+
+### _root.scss <small>(`src/frontend/scss/modules/`)</small>
+```scss
+$header-height: 10vh;
+
+// Usage example (in any other file): 
+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
+
+### _yourModule.scss <small>(`src/frontend/scss/modules/subfolder/`)</small>
+```scss
+@use '../root' as root;
+
+body {
+  background-color: root.$primary;
+}
+```
+
+### examplePage.scss
+```scss
+@import "../modules/subfolder/yourModule";
+
+// This page will now inherit the body tag rules
+// If the same property is declared in both, the last imported one wins
+body {
+  color: root.$dark;
+}
+```
+
+### Pre-existing modules
+
+| 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 |
+| `_mobile.scss` | Media query rules |
+| `_animations.scss` | Keyframe animations (`fade-in`, `spin`) |
+
+## CSS Framework
+
+Some of the most popular css frameworks that supports scss with modules are already installed in `node_modules`
+
+You can choose one or none of them (more than 1 works, but you may get in various conflicts)
+
+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";
+// @import "../modules/frameworks/bulma";
+// @import "../modules/frameworks/foundation";
+// @import "../modules/frameworks/uikit";
+```
+
+### 2. base.njk <small>(`src/frontend/layouts/`)</small>
+
+```html
+{# Bootstrap JS #}
+<script src="/js/bootstrap.bundle.min.js" defer></script>
+
+{# Foundation JS #}
+{# <script src="/js/foundation.min.js" defer></script> #}
+
+{# UIkit JS #}
+{# <script src="/js/uikit.min.js" defer></script> #}
+{# <script src="/js/uikit-icons.min.js" defer></script> #}
+
+{# Bulma — no JS needed #}
+```
+
+### 3. eleventy.config.js
+
+```javascript
+eleventyConfig.addPassthroughCopy({
+  // Bootstrap
+  "node_modules/bootstrap/dist/js/bootstrap.bundle.min.js": "js/bootstrap.bundle.min.js",
+  "node_modules/bootstrap-icons/font/fonts": "css/fonts",
+
+  // Foundation
+  // "node_modules/foundation-sites/dist/js/foundation.min.js": "js/foundation.min.js",
+
+  // UIkit
+  // "node_modules/uikit/dist/js/uikit.min.js": "js/uikit.min.js",
+  // "node_modules/uikit/dist/js/uikit-icons.min.js": "js/uikit-icons.min.js",
+
+  // Bulma — CSS only, no JS passthrough needed
+});
+```
+
+> ⚠️ 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
 ```

package/nginx.conf

@@ -1,75 +1,75 @@
-# Example nginx directives for a Nibula site — covers BOTH backends.
-#
-# /api is served by Node (index.js) if it is running on 127.0.0.1:3000; if Node
-# is unreachable, nginx falls back to the PHP front controller automatically.
-# So the same config works whether you deployed the Node backend or the PHP one:
-#   - Node backend running  -> Node answers /api
-#   - only PHP deployed      -> Node is down -> falls back to PHP-FPM
-#
-# This is NOT a ready-to-use file: paste these directives inside your own
-# server { } block (the one with server_name, listen and SSL) and set `root`
-# to your `out` folder.
-
-# Hide the nginx version from response headers
-server_tokens off;
-
-# Force HTTPS on future requests (applies site-wide, including /api)
-add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
-
-root /var/www/your-site/out;
-index index.html;
-
-# Disable directory listing
-autoindex off;
-
-error_page 403 404 /404.html;
-location = /404.html {
-    internal;
-}
-
-# Never expose the backend source directory over HTTP.
-location ^~ /backend/ {
-    return 404;
-}
-
-# Block server config files anywhere in the tree (.htaccess, web.config).
-location ~* (^|/)(\.htaccess|web\.config)$ {
-    return 404;
-}
-
-# --- /api: Node primary, PHP fallback ---------------------------------------
-# Try the Node backend first. If it is down (502/504), retry through the PHP
-# front controller. Security headers for API responses are set by the backend.
-location ^~ /api/ {
-    proxy_pass http://127.0.0.1:3000;
-    proxy_http_version 1.1;
-    proxy_set_header Host              $host;
-    proxy_set_header X-Real-IP         $remote_addr;
-    proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
-    proxy_set_header X-Forwarded-Proto $scheme;
-
-    proxy_intercept_errors on;
-    error_page 502 504 = @php_backend;
-}
-
-location @php_backend {
-    include fastcgi_params;
-    fastcgi_param SCRIPT_FILENAME $document_root/backend/_core/index.php;
-
-    # Adjust the PHP-FPM socket to your distro:
-    #   Debian / Ubuntu : unix:/run/php/php8.3-fpm.sock
-    #   RHEL / Fedora   : unix:/run/php-fpm/php-fpm.sock
-    #   TCP fallback    : 127.0.0.1:9000
-    fastcgi_pass unix:/run/php/php8.3-fpm.sock;
-}
-
-# Serve static files, fall back to the 404 page.
-# A location with add_header does not inherit server-level headers,
-# so Strict-Transport-Security is repeated here.
-location / {
-    add_header X-Content-Type-Options "nosniff" always;
-    add_header X-Frame-Options "SAMEORIGIN" always;
-    add_header Referrer-Policy "strict-origin-when-cross-origin" always;
-    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
-    try_files $uri $uri/ /404.html;
-}
+# Example nginx directives for a Nibula site — covers BOTH backends.
+#
+# /api is served by Node (index.js) if it is running on 127.0.0.1:3000; if Node
+# is unreachable, nginx falls back to the PHP front controller automatically.
+# So the same config works whether you deployed the Node backend or the PHP one:
+#   - Node backend running  -> Node answers /api
+#   - only PHP deployed      -> Node is down -> falls back to PHP-FPM
+#
+# This is NOT a ready-to-use file: paste these directives inside your own
+# server { } block (the one with server_name, listen and SSL) and set `root`
+# to your `out` folder.
+
+# Hide the nginx version from response headers
+server_tokens off;
+
+# Force HTTPS on future requests (applies site-wide, including /api)
+add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+
+root /var/www/your-site/out;
+index index.html;
+
+# Disable directory listing
+autoindex off;
+
+error_page 403 404 /404.html;
+location = /404.html {
+    internal;
+}
+
+# Never expose the backend source directory over HTTP.
+location ^~ /backend/ {
+    return 404;
+}
+
+# Block server config files anywhere in the tree (.htaccess, web.config).
+location ~* (^|/)(\.htaccess|web\.config)$ {
+    return 404;
+}
+
+# --- /api: Node primary, PHP fallback ---------------------------------------
+# Try the Node backend first. If it is down (502/504), retry through the PHP
+# front controller. Security headers for API responses are set by the backend.
+location ^~ /api/ {
+    proxy_pass http://127.0.0.1:3000;
+    proxy_http_version 1.1;
+    proxy_set_header Host              $host;
+    proxy_set_header X-Real-IP         $remote_addr;
+    proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
+    proxy_set_header X-Forwarded-Proto $scheme;
+
+    proxy_intercept_errors on;
+    error_page 502 504 = @php_backend;
+}
+
+location @php_backend {
+    include fastcgi_params;
+    fastcgi_param SCRIPT_FILENAME $document_root/backend/_core/index.php;
+
+    # Adjust the PHP-FPM socket to your distro:
+    #   Debian / Ubuntu : unix:/run/php/php8.3-fpm.sock
+    #   RHEL / Fedora   : unix:/run/php-fpm/php-fpm.sock
+    #   TCP fallback    : 127.0.0.1:9000
+    fastcgi_pass unix:/run/php/php8.3-fpm.sock;
+}
+
+# Serve static files, fall back to the 404 page.
+# A location with add_header does not inherit server-level headers,
+# so Strict-Transport-Security is repeated here.
+location / {
+    add_header X-Content-Type-Options "nosniff" always;
+    add_header X-Frame-Options "SAMEORIGIN" always;
+    add_header Referrer-Policy "strict-origin-when-cross-origin" always;
+    add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
+    try_files $uri $uri/ /404.html;
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nibula",
-  "version": "1.2.4",
+  "version": "1.2.6",
   "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",

package/src/backend/.htaccess

@@ -1,7 +1,7 @@
-<IfModule mod_rewrite.c>
-    RewriteEngine On
-    RewriteBase /api/
-
-    RewriteRule ^_core/index\.php$ - [L]
-    RewriteRule ^(.*)$ _core/index.php [QSA,L]
+<IfModule mod_rewrite.c>
+    RewriteEngine On
+    RewriteBase /api/
+
+    RewriteRule ^_core/index\.php$ - [L]
+    RewriteRule ^(.*)$ _core/index.php [QSA,L]
 </IfModule>

package/src/backend/_core/composer.json

@@ -1,5 +1,5 @@
-{
-    "require": {
-        "vlucas/phpdotenv": "^5.6"
-    }
-}
+{
+    "require": {
+        "vlucas/phpdotenv": "^5.6"
+    }
+}