@bygghammar/cms-platform 0.96.0 → 0.97.0

package/CHANGELOG.md

@@ -8,6 +8,55 @@ matches `package.json` exactly. See
 Versions 0.1.0 through 0.78.0 predate this repository and were reconstructed
 from the published npm tarballs.
 
+## 0.97.0
+
+Booking-off search landing pages. No migration: the settings live in the
+existing `site_settings` table (the migration manifest is unchanged at 60). Two
+exports were added — `./cms/booking-landing` and `./site/BookingOffNotice` —
+and none removed. With nothing stored, every site behaves exactly as on 0.96.0.
+
+- **Pages hidden from the website while booking is hidden** (Site settings →
+  Booking, after the pages that keep their booking links). While booking is
+  hidden, a page on this list is left out of every structured link the website
+  offers, and returns when booking is shown again. It stays live (200),
+  self-canonical, indexable and in the sitemap, so a visitor arriving from a
+  search result still gets the page: `pageIsIndexable` and `unlistedPages` are
+  unchanged, link-only stays `noindex`, offline stays a 404. Being indexable is
+  not a ranking promise, and the screen says so.
+- **One rule for structured links** (`useDiscoverableLink`,
+  `isHiddenFromDiscovery`, `hiddenPaths` reason `booking-off`): header menu,
+  mobile menu and footer; link tiles (dropped); hero, banner, media-split,
+  price-table, countdown and trip buttons (dropped); media-split slide links,
+  icon-grid card links and Instagram links (link removed, picture or card
+  kept). Applied in render from the link policy the server rendered with, so
+  the server's HTML and later client navigations agree. Links inside rich text
+  are the one documented exception. `restrictToLinks` keeps `booking-off`
+  entries, which name public pages.
+- **Popups** that lead to a hidden page are retired in the runtime the way
+  booking popups are; `withoutPopupsLeadingTo` lets a host withhold them on the
+  server.
+- **The booking-off notice** (`BookingOffNotice`, placed by the page renderer's
+  new `notice` prop after a leading hero): a plain-text heading, message and an
+  optional link, from a site-wide default with optional per-page replacements,
+  field by field, Swedish and English. The link must be an internal path or an
+  `https://` address and never leads to booking or to a hidden page: hosts name
+  their booking page (`LinkVisibilityPolicy.bookingPagePaths`, checked when the
+  notice renders) and check links on save (`VisibilityDeps.noticeTargetProblem`,
+  with `noticeTargetProblem(href, routes)` doing the work from the host's
+  routes). The platform names no route.
+- **Storage and staff writes**: rows `booking.landing.<page uuid>` and
+  `booking.landing.default`, written by `setBookingLandingCore` and
+  `setBookingLandingDefaultCore` — staff only, validated, compare-and-swap on
+  `updated_at`, audited, cache-invalidating. Protected pages and booking
+  exceptions are refused, and adding an exception for a landing page is refused
+  too (`BookingConflictError`); rows that say both are treated as an exception
+  only, and the Booking card warns. After a refused save the page-message editor
+  shows the stored version and says why, so a stale draft is never resubmitted
+  unseen.
+- **Host wiring (optional)**: `booking.fns.setBookingLanding` and
+  `setBookingLandingDefault` show the new subsection; without them the Booking
+  card is unchanged.
+
 ## 0.96.0
 
 Security release. No migration, and no export was added or removed.

package/docs/PAGES.md

@@ -541,11 +541,50 @@ Listing is a second property beside publication, and the two never touch:
   booking links in their own content. Removal (`stripBookingDeep`,
   `withoutBookingPopups`) is for the host to apply to data before it leaves the
   server; stored content is never changed.
+- **Booking-off landing pages** (`cms/booking-landing`). While booking is off, a
+  page in this list leaves every structured link the website offers (see the
+  inventory below; `hiddenPaths` reason `booking-off`, `isHiddenFromDiscovery`,
+  `useDiscoverableLink`), but stays live, self-canonical, indexable and in the
+  sitemap: `pageIsIndexable` and `unlistedPages` do not change. Indexable is
+  not a ranking promise: removing a page's internal links can change how search
+  engines value it. Its booking links go as on any page, and it shows a
+  plain-text notice (`BookingOffNotice`, placed by the page renderer's `notice`
+  prop after a leading hero) with an optional link that never leads to booking
+  or to another hidden page. Staff write a site-wide default and optional
+  per-page replacements, field by field (`resolveNotice`). A page cannot be both
+  a booking exception and a landing page (`BookingConflictError`); stored rows
+  that say both are treated as an exception only, and the Booking card warns.
+  Offline still wins (404); link-only stays `noindex`. Protected pages are
+  refused. With booking on, nothing changes.
+
+### Booking-off landing pages: structured links (reviewed 2026-10-17)
+
+Enforced in render from the link policy the server rendered with (and every
+client navigation refreshes), so server HTML and the browser agree. Stored
+content is never changed. `tests/booking-landing-discovery-inventory.test.tsx`
+fails when a block type is added without being classified here.
+
+| Surface | While booking is hidden, a link to a landing page… |
+| --- | --- |
+| Header menu, mobile menu, footer, header button | not rendered (`hiddenPaths`); an emptied footer column goes |
+| `linkTiles` | tile dropped |
+| `heroFull`, `ctaBanner`, `mediaSplit` (both buttons), `priceTable`, `countdown` (expired button), `tripList`/`courseList` button | button dropped |
+| `mediaSplit` slide link, `iconGrid` card link, `instagram` profile and tiles | link removed, picture or card kept |
+| Popups (link block, button or answer `openUrl`, form success `openUrl`) | popup withheld on the server (`withoutPopupsLeadingTo`) and retired in the runtime, like a booking popup |
+| Booking-off notice link | dropped when it leads to booking (a booking site or the host's `bookingPagePaths`) or to a hidden page; refused at save by the host's `noticeTargetProblem` |
+| `richText` | **exception**: links in editor-written text stay as written |
+| `form` thank-you redirect | exempt: the result of submitting, not a link offered |
+| `layout`, `faq`, `prose`, `checklist`, `imageMarquee`, `cabinTabs` | no links of their own |
+
+Hosts add their own sections to the same rule with `useDiscoverableLink()`
+(Voyara: its legacy hero buttons and destination cards).
 
 ### Storage
 
 No migration: one `site_settings` row per decision, keyed by page id —
-`page.listing.<uuid>`, `booking`, `booking.exception.<uuid>`. Every write is a
+`page.listing.<uuid>`, `booking`, `booking.exception.<uuid>`,
+`booking.landing.<uuid>` (`{ landing, notice? }`) and `booking.landing.default`
+(`{ notice }`). Every write is a
 compare-and-swap on `updated_at` (`VisibilityConflictError` when someone else
 changed the row first). None is an `OVERRIDABLE_SETTING_KEYS` key, so the generic
 settings save and reset cannot reach them.
@@ -570,7 +609,11 @@ shown. The public page route takes a per-page `pagePolicy` query and adds
 
 ```ts
 pages: { fns: { setPageStatus?, setPageListing?, ... } }
-booking?: { fns: { getBookingSettings, setBookingEnabled, setBookingException } }
+booking?: { fns: { getBookingSettings, setBookingEnabled, setBookingException,
+                   setBookingLanding?, setBookingLandingDefault? } }
+// server: VisibilityDeps.noticeTargetProblem?(href) — the host's route check
+// (noticeTargetProblem(href, routes) does the work from the host's routes)
+// browser policy: LinkVisibilityPolicy.bookingPagePaths — the host's booking page, every alias
 useLinkVisibility?: () => LinkVisibilityPolicy | undefined
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bygghammar/cms-platform",
-  "version": "0.96.0",
+  "version": "0.97.0",
   "description": "Shared CMS platform: blocks, block types, i18n core, UI primitives and design-token contract used by every Bygghammar/Voyara site.",
   "type": "module",
   "sideEffects": [
@@ -210,6 +210,7 @@
     "./cms/page-publication": "./src/cms/page-publication.ts",
     "./cms/page-visibility": "./src/cms/page-visibility.ts",
     "./cms/booking-links": "./src/cms/booking-links.ts",
+    "./cms/booking-landing": "./src/cms/booking-landing.ts",
     "./site/routes": "./src/site/routes.ts",
     "./site/PageRenderer": "./src/site/PageRenderer.tsx",
     "./server/env": "./src/server/env.ts",
@@ -239,6 +240,7 @@
     "./site/route-index": "./src/site/route-index.ts",
     "./site/route-aliases": "./src/site/route-aliases.ts",
     "./site/link-visibility": "./src/site/link-visibility.tsx",
+    "./site/BookingOffNotice": "./src/site/BookingOffNotice.tsx",
     "./site/SiteHeader": "./src/site/SiteHeader.tsx",
     "./site/SiteFooter": "./src/site/SiteFooter.tsx",
     "./server/schemas": "./src/server/schemas.ts",

package/src/admin/describe-log.ts

@@ -37,6 +37,8 @@ export const ACTION_LABELS: Record<string, string> = {
   "page.listing": "Changed whether a page is listed",
   "booking.settings": "Switched booking on or off",
   "booking.exception": "Changed which pages keep booking links",
+  "booking.landing": "Changed which pages are hidden from the website while booking is hidden",
+  "booking.landing.default": "Changed the booking-off landing page message",
   "page.version.create": "Saved page version",
   "page.version.restore": "Restored page version",
   "template.create": "Created block template",