Open changes waiting for a look, and what shipped recently. Anyone can open a preview below and leave feedback on GitLab.
Add markdown support in the footer text item
What this affectssrc/components/Footer.astro
update any footer item text with markdown text
Updates · newest first
creat/edit event markdown editor line break and event type detector fixed
What this affectspublic/scripts/render-markdown.js & src/components/MarkdownEditor2.astro markdown editor renderingsrc/pages/[...locale]/create-event.astro event type detectorsrc/pages/[...locale]/event-preview.astro preview menus after title1. create or edit an event description or event type 2. after update and redirect to preview page check the menus right after the title
Updates · newest first
Statusbar UI flexible for both desktop and mobile, text show without turncate, navbar overflow fixed, reduce motion, dynamic color detector error and fallback. disable notifiaction aria label is now from strapi
What this affectssrc/utils/getGlobals.ts, src/layouts/Layout.astro, src/components/StatusBar.astro, src/components/NavBar.astro
take a new window and load the page, check with both mobile and desktop version
main) wondersofwork.nl 🎉Adds public/_headers so Cloudflare Pages sends an explicit Cache-Control per asset class. Goal: returning visitors stay fast and pick up new deploys quickly, without ever needing a manual Cloudflare cache purge.
Context: the root cause of the recurring "site messed up until purge-everything" was Cloudflare APO (a WordPress-era leftover) edge-caching HTML on an Astro/Pages origin — that has been disabled in the Cloudflare dashboard. This MR is the browser-side hardening so stale caching cannot bite returning visitors either.
Per class:
/assets/* — content-hashed by Astro (CSS, JS, fonts under /assets/fonts/) → max-age=31536000, immutable. Filename changes on content change, so no revalidation is ever needed./images/* — clean stable filenames; by editor convention a replaced photo gets a NEW filename → max-age=31536000 without immutable, so a hard reload can still revalidate and recover if a filename is ever reused./scripts/* — hand-written modules keep the same filename (external references depend on it) but their content changes on deploy → max-age=60, stale-while-revalidate=86400: served instantly from cache, refreshed in the background, at most one navigation behind after a deploy.Freshness relies on the ETags Pages already sends, so a revalidation is a cheap bodyless 304. HTML is intentionally untouched (already max-age=0, must-revalidate, served fresh from origin).
Only HTTP response headers for static assets served by Cloudflare Pages. No application code, no build logic, no filenames change. Nothing security-sensitive (no profile / key export / OpenBunker paths touched). _headers has no effect in local dev — it only applies on Pages (preview + production).
On the preview deploy link, check the three classes:
`` curl -sSI <preview-url>/assets/<any-hashed>.css | grep -i cache-control # max-age=31536000, immutable curl -sSI <preview-url>/images/og-default.jpg | grep -i cache-control # max-age=31536000 (no immutable) curl -sSI <preview-url>/scripts/global.js | grep -i cache-control # max-age=60, stale-while-revalidate=86400 ``
Expect each header to match the class above. Also confirm the site still loads and Nostr scripts run (the /scripts/* change is the only one that alters behaviour for returning visitors).
Status bar added
What this affectsdynamic component src/components/StatusBar.astro added, gets active, color and text update via strapi
take a new new window and visit site
preview-menu.js hardcoded "calendar" as the post-delete redirect, so Dutch users always landed on /nl/calendar/ (404) instead of /nl/agenda/. Now uses window.eventCollectionPrefix which is baked in at build time per locale.
public/scripts/preview-menu.js — delete redirect for both events and storiessrc/pages/[...locale]/event-preview.astro — inline onclick replaced with a wired handler; eventCollectionPrefix exposed via define:varsSign in as the event owner on the NL preview link
Open an event, click the kebab menu → Delete → confirm
Should redirect to /nl/agenda/ — not /nl/calendar/
Repeat on the EN preview link and confirm it still lands on /en/calendar/
Fixes a white-page blocker for new OpenBunker users: the post-login redirect pointed at the removed /profile route. Also fixes the export-key page sending signed-out users to the same dead route, adds an OpenBunker welcome prompt on the edit-profile page, improves the offline-at-load relay error message, and disables the Send Code button while the OTP request is in flight to prevent double-submits.
What this affectspublic/scripts/login/check-user-metadata.js — redirect target for new OpenBunker userssrc/pages/[...locale]/edit-profile.astro — reads source=openbunker-new and shows the completion promptsrc/pages/[...locale]/export-key.astro — dead /profile fallback replaced with /loginsrc/pages/[...locale]/login.astro — Send Code button disabled state + back-button resetpublic/scripts/login/login-page.js — button loading state logic; offline relay error message says "Reload the page"Create a new OpenBunker account with no name set → should land on /edit-profile?source=openbunker-new with the "Please complete your profile details" prompt visible
On the login page, enter an email and click Send Code → button should gray out immediately; click Back → button should be clickable again
While on the export-key page, sign out → should redirect to /login, not a blank page
Nav edit button dispatched a profileEditMode custom event the page never listened to — fixed to dispatch popstate instead. Edit href now includes key=npub built from userInfo at click time. Entering from another page appends returnUrl and redirects back on save/cancel. returnUrl was followed raw without origin check — added safeReturnUrl() matching the guard from the old profile.astro.
What this affectsNavBar.astro — key=npub in edit href, popstate dispatch, returnUrl on cross-page navprofile-preview.astro — leaveEditMode redirects to returnUrl when presentedit-profile.astro — safeReturnUrl() validates same-origin before navigating, falls back to /profile-previewClick edit profile from navbar on any page — profile-preview opens in edit mode, save/cancel returns to the originating page. Craft a link to /edit-profile?returnUrl=.... — save or cancel stays on-site instead of redirecting away.
__fetchNewest helper__: Single shared helper replaces duplicated "keep newest across relays" logic in story/event-preview and adds it to profile-preview, which was missing it — causing stale profile data for returning visitors.
__NIP-09 e-tag deletions fix__: deletion-cache.js only tracked a-tag (coordinate) deletions and completely ignored e-tag (event id) deletions. A kind:5 deletion referencing an event by ["e", "<id>"] was invisible, so deleted events kept showing. prefetchDeletionsForEvent also used a #a filter that excluded e-tag deletions from relay queries. Fixed by:
recordDeletion: now processes both a-tag and e-tag deletion references, with a comment that author-trust relies on callers using an authors filterisEventDeleted: checks event.id against deleted IDs alongside the existing a-coordinate checkprefetchDeletionsForEvent: dropped the #a filter to retrieve all kind:5 from the authorremoveDeletedCard: now looks up the bare d-tag from the matched event's own tags instead of using the coordinate key (kind:pubkey:dtag) as a DOM selector— fixing the race where a card rendered before its deletion arrived was never removed
nostr-fetch.js — new fetchNewest export; kind:5 bundled into fetchStories / fetchCalendarEventsdeletion-cache.js — e-tag support, proactive card removal with correct d-tag lookup, author-check comment, #a filter removed from prefetchDeletionsForEventevent-handlers.js — handleStory and handleCalendarEvent route kind:5 → recordDeletionstory-preview, event-preview, profile-preview — all use fetchNewest; profile now bypasses fetchProfiles cache short-circuitDetail pages were first-relay-wins: story-preview resolved on the first event received, event-preview gated re-renders with a one-shot found flag. A stale relay answering first meant the old version was shown even when a newer one arrived moments later. nostr-fetch was also writing cache entries under pubkey:kind:dtag while every reader uses generateUId (kind:pubkey:dtag) — dead writes under a key nobody looks up.
Previously: late-connecting relays received a raw ws.send() without attachMux, so their EVENT/EOSE frames were silently dropped. handleCalendarEvent also had no created_at guard, so a stale relay answering last could overwrite a newer cached version.
What this affectsDetail pages were first-relay-wins: story-preview resolved on the first event received, event-preview gated re-renders with a one-shot found flag. A stale relay answering first meant the old version was shown even when a newer one arrived moments later. nostr-fetch was also writing cache entries under pubkey:kind:dtag while every reader uses generateUId (kind:pubkey:dtag) — dead writes under a key nobody looks up.
Previously: late-connecting relays received a raw ws.send() without attachMux, so their EVENT/EOSE frames were silently dropped. handleCalendarEvent also had no created_at guard, so a stale relay answering last could overwrite a newer cached version.
How to try itLoad any page that fetches Nostr content. Edit a story or calendar event from a Nostr client, reload the detail page while one relay is slow — the updated version should always win. For the cache key fix: confirm stories and events still load correctly on overview pages after navigation.
Reverts MR 88 (fix/relay-connection-delay, merge commit 2e123fb) in full. That change introduced a regression: the calendar overview now shows only a single event instead of the full list. Reverting restores the previous, working version so it goes live again while the relay-update fix is reworked.
Open any page with the calendar events overview after this merges and deploys. All events should render again, not just one.
What this affectsNostr fetch/queue layer and the story/event detail pages: public/scripts/nostr-queue.js, public/scripts/nostr-fetch.js, public/scripts/event-handlers.js, public/scripts/send-message.js, src/pages/[...locale]/story-preview.astro, src/pages/[...locale]/event-preview.astro, plus the prettier bump and formatting changes bundled in MR 88. No content or auth changes.
Note: this reverts a merge commit, so fix/relay-connection-delay will count as already-merged. The relay-update fix must be reworked on a fresh branch (or by reverting this revert) before it can land again.
Detail pages were first-relay-wins: story-preview resolved on the first event received, event-preview gated re-renders with a one-shot found flag. A stale relay answering first meant the old version was shown even when a newer one arrived moments later. nostr-fetch was also writing cache entries under pubkey:kind:dtag while every reader uses generateUId (kind:pubkey:dtag) — dead writes under a key nobody looks up.
Previously: late-connecting relays received a raw ws.send() without attachMux, so their EVENT/EOSE frames were silently dropped. handleCalendarEvent also had no created_at guard, so a stale relay answering last could overwrite a newer cached version.
What this affectsDetail pages were first-relay-wins: story-preview resolved on the first event received, event-preview gated re-renders with a one-shot found flag. A stale relay answering first meant the old version was shown even when a newer one arrived moments later. nostr-fetch was also writing cache entries under pubkey:kind:dtag while every reader uses generateUId (kind:pubkey:dtag) — dead writes under a key nobody looks up.
Previously: late-connecting relays received a raw ws.send() without attachMux, so their EVENT/EOSE frames were silently dropped. handleCalendarEvent also had no created_at guard, so a stale relay answering last could overwrite a newer cached version.
How to try itLoad any page that fetches Nostr content. Edit a story or calendar event from a Nostr client, reload the detail page while one relay is slow — the updated version should always win. For the cache key fix: confirm stories and events still load correctly on overview pages after navigation.
Center hero text content when pages have multiple images
What this affectssrc/components/blocks/Hero.astro and src/utils/getHeroAlign.ts
How to try itgo to /nl/zomer-focusdagen-ondernemers/