@nera-static/nera 1.15.0 → 1.16.1

package/README.md

@@ -45,7 +45,7 @@ and its scripts call the CLI:
     "dev": "nera dev", "build": "nera build", "serve": "nera serve",
     "validate": "nera validate", "check": "nera build --check"
   },
-  "dependencies": { "@nera-static/nera": "^1.14.1" }
+  "dependencies": { "@nera-static/nera": "^1.16.0" }
 }
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@nera-static/nera",
-    "version": "1.15.0",
+    "version": "1.16.1",
     "description": "The Nera CLI — scaffold, build, preview and update a Nera static site with one command over the @nera-static/core engine",
     "type": "module",
     "bin": {

package/skills/nera/recipes/business-site.md

@@ -11,12 +11,15 @@ imprint and privacy, with a menu on every page.
    live URL, e.g. `https://example.com`) once the domain is known.
 3. Write one Markdown page per topic, each with `layout: pages/default.pug`,
    a `title` and a `description`: `pages/index.md`, `pages/about.md`,
-   `pages/services.md`, `pages/opening-hours.md`, `pages/contact.md`,
-   `pages/imprint.md`, `pages/privacy.md`. Opening hours fit a Markdown
-   table.
+   `pages/services.md`, `pages/opening-hours.md`, `pages/contact.md`.
+   Opening hours fit a Markdown table. A new site already has
+   `pages/imprint.md` and `pages/privacy.md` as placeholders, linked from
+   the layout's footer: replace their text, or write them if they are
+   missing.
 4. Menu: `npm install @nera-static/plugin-navigation`, list the pages in
    `config/navigation.yaml` (`href` ending in `.html`, `name`; groups such
-   as `main:` and `footer:` for a footer menu with imprint and privacy), run
+   as `main:` and `footer:`; a footer menu replaces the layout's own
+   imprint and privacy links, so keep only one of the two), run
    `npx nera-navigation` and include a menu in
    `theme/views/layouts/layout.pug` (see the plugin README for the mixins).
 5. Contact form: follow [contact-form](contact-form.md).

package/src/scaffold.js

@@ -197,6 +197,14 @@ async function applyTheme(targetDir, theme) {
         await fs.writeFile(pkgPath, `${JSON.stringify(pkg, null, 4)}\n`)
     }
     console.log(`  ✓ Using theme "${theme}"${pkgName ? ` (${pkgName})` : ''}`)
+    // The scaffold's footer, which links the imprint and privacy
+    // placeholders, is a starter template and so left out with a theme.
+    console.log(
+        '  • pages/imprint.md and pages/privacy.md are placeholders: link them ' +
+            'from the theme\'s layout (theme-blog and theme-business take ' +
+            '`footer_links` in config/theme.yaml), or `nera build --check` ' +
+            'keeps warning legal-imprint-link and legal-privacy-link.'
+    )
 }
 
 // `--name`: any non-empty text without line breaks. It is written as a JSON

package/template/AGENTS.md

@@ -61,10 +61,9 @@ finds pages the build would skip silently. Run it first.
   says nothing; `nera validate` warns (`layout-missing`). Renaming or deleting
   a layout breaks every page that uses it.
 - **The page body.** The rendered Markdown reaches the template as `content`.
-  Without a theme, `theme/views/pages/default.pug` prints it with
-  `main !{ content }` inside `block content`; with a theme, the theme's layout
-  may already hold the `<main>`. A page has exactly one `<main>`: check the
-  layout and the page template before adding one.
+  Without a theme, `theme/views/pages/default.pug` prints it in a `main`
+  element inside `block content`; with a theme, the theme's layout may hold
+  the `<main>`. A page has exactly one `<main>`: check before adding one.
 - **`public/` is wiped on every build.** Put source files in `pages/`,
   `theme/` or `config/`; anything written into `public/` by hand is lost.
 - **Site files override theme files.** If `config/app.yaml` sets `theme:`,
@@ -114,8 +113,9 @@ the URL.
 
 ## Getting online
 
-`npm run build` writes the finished site into `public/`. That folder is what
-gets deployed: upload its contents to any static web host.
+`npm run build` writes the site into `public/`: upload its contents to any
+static web host. Replace the imprint and privacy placeholders in `pages/`
+first, if any; `legal-*` warnings are expected until they are filled and linked.
 
 <!-- nera:site-notes — everything below this line belongs to the site owner; `nera update` keeps it as it is -->
 ## Notes for this site

package/template/config/app.yaml

@@ -6,3 +6,6 @@ translations:
   en:
     app_description: A static site built with Nera
     app_keywords: nera, static site generator
+    skip_to_content: Skip to content
+    imprint: Imprint
+    privacy: Privacy

package/template/pages/imprint.md

@@ -0,0 +1,21 @@
+---
+layout: pages/default.pug
+title: Imprint
+description: Imprint placeholder — replace it with your own legal notice
+---
+# Imprint
+
+**This is a placeholder.** It is not a legal notice. Replace this page with your
+own imprint before you publish the site; if you are unsure what you need, ask a
+lawyer.
+
+## To do
+
+What an imprint typically names (the exact duty depends on your country and on
+what the site does):
+
+- who runs the site: full name, or company name and legal form
+- a postal address where you can be reached
+- fast ways to contact you: email address, and often a phone number
+- the person responsible for the content, if the law asks for one
+- register entries and VAT ID, if your business has them

package/template/pages/privacy.md

@@ -0,0 +1,23 @@
+---
+layout: pages/default.pug
+title: Privacy
+description: Privacy policy placeholder — replace it with your own privacy policy
+---
+# Privacy
+
+**This is a placeholder.** It is not a privacy policy. Replace this page with
+your own privacy policy before you publish the site; if you are unsure what you
+need, ask a lawyer.
+
+## To do
+
+What a privacy policy typically covers (the exact duty depends on your country
+and on what the site does):
+
+- who is responsible for the data processing, and how to contact them
+- what your hosting provider logs (such as IP addresses) and for how long
+- every plugin, form, font, embed or analytics tool that processes visitor
+  data, its purpose and legal basis
+- how long data is kept
+- the visitor's rights (access, correction, deletion, objection) and where to
+  complain

package/template/theme/views/layouts/layout.pug

@@ -9,6 +9,14 @@ html(lang=app.lang)
     meta(name="keywords", content=`${ meta.keywords || t('app_keywords') }`)
     meta(name="generator" content="nera")
     meta(name="robots" content=`${ meta.robots || app.robots }`)
+    style.
+      .skip-link { position: absolute; left: -9999px; }
+      .skip-link:focus { position: static; }
 
   body
+    a.skip-link(href="#main") #{ t('skip_to_content') }
     block content
+    footer
+      a(href="/imprint.html") #{ t('imprint') }
+      = ' · '
+      a(href="/privacy.html") #{ t('privacy') }

package/template/theme/views/pages/default.pug

@@ -2,4 +2,4 @@
 extends ../layouts/layout
 
 block content
-  main !{ content }
+  main#main !{ content }