poops 1.9.6 → 1.9.7

package/README.md

@@ -1093,6 +1093,18 @@ All filters are available in both engines. The only syntax difference is how arg
   ---
   ```
 
+  The same `jsonld` object works in your `site` data, as a site-wide default — useful when every page on the site is one type. A docs site is `TechArticle`, not `WebPage`:
+
+  ```json
+  "markup": {
+    "site": {
+      "jsonld": { "@type": "TechArticle" }
+    }
+  }
+  ```
+
+  Precedence is defaults → `site.jsonld` → `page.jsonld`, so a single page can still opt out (a `FAQPage` inside a `TechArticle` site). A site-wide `@type` also overrides the auto-detected `BlogPosting` on dated pages, so on a site mixing docs and a blog set the type per page instead. Both merge into the page's own block only — the auto-emitted `WebSite` and `BreadcrumbList` blocks are untouched.
+
   poops auto-picks `BlogPosting` (page has a `date`) or `WebPage`. Override `@type` with the `jsonld` object for any schema.org type — common ones search/generative engines act on: `Article`, `NewsArticle`, `HowTo`, `FAQPage`, `QAPage`, `Product`, `Recipe`, `Event`, `Course`, `VideoObject`, `SoftwareApplication`, `Organization`, `Person`, `BreadcrumbList`, `WebSite`. Full list at [schema.org/docs/full](https://schema.org/docs/full.html); validate with the [Rich Results Test](https://search.google.com/test/rich-results). A per-`@type` table with the notable fields is in the [Templating docs](example/src/markup/docs/quick-start/templating-html.md).
 
 - `breadcrumb` — generates a visible breadcrumb `<nav class="breadcrumb"><ol>…</ol></nav>` trail for the page body (blog posts, nested pages), from the same URL-depth data the `jsonld` `BreadcrumbList` uses: the site root, each ancestor folder (humanized, e.g. `docs/static-site` → _Static Site_), then the current page as `aria-current` text. Pass `relativePathPrefix` so links resolve against the current output location (localhost in dev, your deployed subpath in prod) — not the absolute domain.

package/lib/markup/helpers.js

@@ -532,10 +532,12 @@ export function buildBreadcrumb(page, site = {}, prefix = '') {
 // gains a `logo` ImageObject when `site.logo` is set — Google Article rich
 // results require it. On the homepage (page has no `url`) a second `WebSite`
 // block is emitted, declaring the site name for search results.
-// Anything in `page.jsonld` (an object) is merged over the generated defaults,
-// so a page can add or replace any field — including @type — as a full escape
-// hatch. Values come from front matter, so the JSON is escaped for a <script>
-// context to prevent a `</script>` break-out (XSS).
+// `site.jsonld` and `page.jsonld` (objects) are merged over the generated
+// defaults — site-wide first, then the page — so a site can set a default
+// @type (a docs site is TechArticle, not WebPage) and a page can still add or
+// replace any field as a full escape hatch. Values come from front matter, so
+// the JSON is escaped for a <script> context to prevent a `</script>`
+// break-out (XSS).
 export function buildJsonLd(page, site = {}) {
   page = page || {}
   site = site || {}
@@ -577,8 +579,10 @@ export function buildJsonLd(page, site = {}) {
     if (page.wordcount) data.wordCount = page.wordcount
   }
 
-  // page.jsonld extends/overrides. Shallow merge — nested schema is rare and
-  // the escape hatch is meant for whole-key replacement.
+  // site.jsonld then page.jsonld extend/override — the page wins. Shallow
+  // merge — nested schema is rare and the escape hatch is meant for whole-key
+  // replacement.
+  if (site.jsonld && typeof site.jsonld === 'object') Object.assign(data, site.jsonld)
   if (page.jsonld && typeof page.jsonld === 'object') Object.assign(data, page.jsonld)
 
   const blocks = [jsonLdScript(data)]

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "poops",
   "description": "Straightforward, no-bullshit bundler for the web.",
-  "version": "1.9.6",
+  "version": "1.9.7",
   "license": "MIT",
   "type": "module",
   "main": "poops.js",