create-berna-stencil 2.6.3 → 2.6.4

package/docs/Components.md

@@ -1,96 +0,0 @@
-# Nunjucks (HTML) Components
-
-## What is Nunjucks
-
-Nunjucks (`.njk`) is an HTML file that supports logic like variables, `if` statements, and `for` loops. It can extend a base layout and include other `.njk` components
-
-## Create a component
-
-Create a new `.njk` file anywhere inside `src/frontend/components/`. You can organize them into subfolders freely
-
-```
-src/frontend/components/
-├── global/
-├── layouts/
-├── modals/
-│   └── privacyModal.njk # You can move it to a modals/subfolder
-├── welcome.njk
-```
-
-## Include a component
-
-To render a component inside a page, navigate to `src/frontend/layouts/` and edit `pageComponents.njk`
-
-### pageComponents.njk <small>(`src/frontend/layouts/`)</small>
-
-```js
-{% if title == "homepage" %}
-  {% include "welcome.njk" %}
-
-{% elif title == "examplePage" %}
-  {% include "exampleComponent1.njk" %}
-  {% include "subfolder/exampleComponent2.njk" %}
-
-{% else %}
-  {% include "404/_404.njk" %}
-  {{ content | safe }}
-{% endif %}
-```
-
-Add a new `{% elif %}` block for each page, listing its components in order. If a component lives in a subfolder, specify the relative path accordingly
-
-> ⚠️ A new `elif` block is automatically added when you create a page via the Assistant CLI
-
-> ⚠️ If you move or delete a component, always update `pageComponents.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.
-
-### exampleComponent.njk
-```js
-<section class="hero">
-  {% include "ui/heroTitle.njk" %}
-  {% include "ui/heroButton.njk" %}
-</section>
-```
-
-> The same path rules apply: if the included component is in a subfolder, specify the full relative path.
-
-## Global components
-
-Header and footer live in `src/frontend/components/global/` and are automatically included in every page via `base.njk`. Edit them to change the site-wide layout
-
-## Site data in components
-
-All values defined in `src/frontend/data/site.json` are globally available in every component via `{{ site.* }}`
-
-### site.json <small>(`src/data/`)</small>
-```json
-{
-  "title": "My Site",
-  "logo": "/img/logo.png",
-  "legal": {
-    "privacy": "/privacy"
-  }
-}
-```
-
-### Usage in any `.njk` file
-```js
-<p>{{ site.title }}</p>
-<a href="{{ site.legal.privacy }}">Privacy Policy</a>
-<img src="{{ site.logo }}" alt="{{ site.title }}">
-```

package/docs/Creating pages.md

@@ -1,65 +0,0 @@
-# Creating Pages
-
-> 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/`.
-
-The recommended way is via the **Assistant CLI**
-
-## What gets created
-For a page named `my-page`:
-
-| File | Purpose |
-|---|---|
-| `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 |
-
-## Adding content
-
-1. Create a component in `src/frontend/components/` (e.g. `_myPage.njk`)
-2. Include it in `src/frontend/layouts/pageComponents.njk` inside the generated `elif` block:
-
-```njk
-{% elif title == "myPage" %}
-  {% include "_myPage.njk" %}
-```
-
-See **Components** DOC file for more info
-
-## URL and title
-
-The URL is the kebab-case name (`/my-page/`). The `title` in the front matter is camelCase (`myPage`) and is used internally to load the correct CSS and JS files — do not change it.
-
-## 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:
-
-```njk
----
-title: "team"
-permalink: "about/team/"
-layout: pageComponents.njk
----
-```
-
-The parent path (`about`) does **not** need to exist as a real page — it's just a URL prefix. Only the last segment (`team`) must match the filename and the `title` in the front matter.
-
-| 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` |
-
-## SEO
-
-The CLI creates a stub entry in `src/frontend/data/site.json`. Fill it in:
-
-```json
-"myPage": {
-  "seo": {
-    "title": "My Page | Site Name",
-    "description": "Page description"
-  }
-}
-```
-
-See **Head & SEO** for all available options.

package/docs/Deploy.md

@@ -1,55 +0,0 @@
-# Server Configuration
-
-Berna-Stencil includes ready-made server configuration for Apache and IIS. For Nginx, a reference config is provided in the project root.
-
-## Apache
-
-`.htaccess` files at `src/frontend/` and `src/backend/` are automatically copied to the build output by Eleventy. No additional setup required.
-
-Covers:
-- Directory listing disabled
-- 403 / 404 → `/404.html`
-- Sensitive files blocked (`web.config`, dotfiles, etc.)
-- `/api/*` → `backend/_core/index.php`
-- HTTPS redirect
-
-## IIS
-
-`web.config` files at `src/frontend/` and `src/backend/` are automatically copied to the build output by Eleventy. No additional setup required.
-
-Covers the same rules as the Apache configuration above.
-
-## Nginx
-
-Nginx does not support per-directory configuration files. The `nginx.conf` in the project root is a reference config that must be manually placed on the server.
-
-### Setup
-
-1. Copy `nginx.conf` to the server:
-```bash
-scp nginx.conf user@server:/etc/nginx/sites-available/your-site
-```
-
-2. Edit `server_name` and `root` to match your environment:
-```nginx
-server_name example.com;
-root /var/www/html/out;
-```
-
-3. Add your SSL certificate paths.
-
-4. Enable and reload:
-```bash
-ln -s /etc/nginx/sites-available/your-site /etc/nginx/sites-enabled/
-nginx -t && systemctl reload nginx
-```
-
-### PHP-FPM socket
-
-The default socket path in `nginx.conf` targets RHEL / Fedora systems. Adjust for your distro:
-
-| Distro | Path |
-|---|---|
-| RHEL / Fedora | `unix:/run/php-fpm/php-fpm.sock` |
-| Debian / Ubuntu | `unix:/run/php/php-fpm.sock` |
-| TCP fallback | `127.0.0.1:9000` |

package/docs/Head and SEO.md

@@ -1,94 +0,0 @@
-# Head & SEO
-
-
-This json holds global settings used across all pages in `base.njk` and other components:
-
-### site.json <small>`(src/frontend/data/)`</small>
-```json
-"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",
-"data_bs_theme": "dark",
-"favicon": "/assets/brand/favicon.svg",
-"logo": "/assets/brand/logo.svg",
-...
-```
-
-## Per-page SEO and CDN
-
-Each page entry is keyed by its camelCase `title` from the front matter:
-
-If you don't want to use a particular cdn inserting it in `base.njk` for all pages, you can add extra specific cdn (css, js) by inserting the link in each page of site.json separating them with a `,` and setting them in ""
-
-### site.json <small>`(src/frontend/data/)`</small>
-```json
-"pages": {
-    ...
-    "examplePage": {
-      "seo": {
-        "title": "Example Page",
-        "description": "description"
-      },
-      "cdn": {
-        // You can leave the [] empty
-        "css": ["https://example1.com/lib.min.css", "https://example2.com/lib.min.css"],
-        "js": ["https://example1.com/lib.min.js", "https://example2.com/lib.min.js"]
-      }
-    }
-    ...
-}
-```
-
-## AI & SEO bots
-
-`llms.txt` and `robots.txt` are generated automatically from `site.json` via their respective `.njk` files — no manual editing needed.
-
-| File | Purpose | Reachable at |
-|---|---|---|
-| `llms.njk` | Tells AI models what your site is about | `yoursite.com/llms.txt` |
-| `robots.njk` | Controls search engine crawling | `yoursite.com/robots.txt` |
-
-To customize them, edit `src/llms.njk` or `src/robots.njk` directly.
-
-### Customizing llms.txt
-
-`src/llms.njk` ships with a base template — **replace the placeholders with your own content**:
-
-```
-# {{ site.site_name }}
-
-> {{ site.description }}
-
-Built by {{ site.author }} — {{ site.url }}
-
-## Pages
-
-- {{ site.url }}: Homepage
-
-## Notes
-
-- Language: {{ site.lang }}
-- All content may be used for AI inde   xing unless otherwise stated
-```
-
-> The more accurate and detailed your `llms.txt`, the better AI models will understand and reference your site.
-
-## Configuration field description
-
-| Field | Purpose |
-|---|---|
-| `site_name` | Brand name (used in meta tags) |
-| `title` | Default page title |
-| `description` | Default meta description |
-| `keywords` | Default meta keywords |
-| `domain` / `url` | Used for canonical URLs and og:url |
-| `lang` | HTML `lang` attribute |
-| `author` | Meta author tag |
-| `data_bs_theme` | Bootstrap color scheme (`light` / `dark`) |
-| `favicon` | Path to the favicon |
-| `logo` | Path to the logo (available as `{{ site.logo }}`) |

package/docs/Javascript.md

@@ -1,53 +0,0 @@
-# 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';
-```
-
-> ⚠️ 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

@@ -1,140 +0,0 @@
-# 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";
-
-@import "../modules/notification";
-
-//==========================
-// 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 |
-| `_buttons.scss` | Style and hovers for buttons 
-| `_animations.scss` | Keyframe animations (`fade-in`, `spin`) |
-| `_notification.scss` | Notification component style |
-
-## 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.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
-});
-```
-
-### 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,69 +0,0 @@
-# Redirect all HTTP traffic to HTTPS
-server {
-    listen 80;
-    server_name _;
-    return 301 https://$host$request_uri;
-}
-
-server {
-    listen 443 ssl;
-    server_name _;
-
-    # SSL certificate — replace with your own paths.
-    # Let's Encrypt default shown below; adjust the domain.
-    ssl_certificate     /etc/letsencrypt/live/your-domain/fullchain.pem;
-    ssl_certificate_key /etc/letsencrypt/live/your-domain/privkey.pem;
-
-    # 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/html/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
-    location ^~ /backend/ {
-        return 404;
-    }
-
-    # Block server config files anywhere in the tree (.htaccess, web.config).
-    # return 404 is served internally as /404.html via error_page above.
-    location ~* (^|/)(\.htaccess|web\.config)$ {
-        return 404;
-    }
-
-    # Block dotfiles (.git, .env, etc.)
-    location ~ /\. {
-        return 404;
-    }
-
-    # Route all /api/ requests to the PHP front controller.
-    # Security headers for API responses are set by the front controller (PHP).
-    location ^~ /api/ {
-        try_files $uri =404;
-        fastcgi_pass unix:/run/php-fpm/php-fpm.sock;
-        fastcgi_param SCRIPT_FILENAME $document_root/backend/_core/index.php;
-        include fastcgi_params;
-    }
-
-    # 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/src/backend/.htaccess

@@ -1,7 +0,0 @@
-<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 +0,0 @@
-{
-    "require": {
-        "vlucas/phpdotenv": "^5.6"
-    }
-}