From 60bcd589c08a1292c3682e0fb44da904ebaa7af8 Mon Sep 17 00:00:00 2001 From: vickydotbat Date: Thu, 16 Jul 2026 18:13:49 +0000 Subject: [PATCH] Set wiki overlay scrim tokens to theme charcoal (#26) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Companion to sow-nodebb-plugin-wiki#22: the plugin now exposes `--wiki-scrim`/`--wiki-scrim-strong` for drawer and dialog backdrops. Override them from `--wg-bg-deep` so overlays match the plum/gold palette instead of the plugin's slate-blue defaults. Verified in the dev forum bundle. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Reviewed-on: https://git.westgate.pw/ShadowsOverWestgate/sow-nodebb-theme/pulls/26 Co-authored-by: vickydotbat Co-committed-by: vickydotbat --- custom_pages/westgate-pages/topbar-custom.js | 224 ------------------- scss/westgate/_wiki-prose.scss | 4 + 2 files changed, 4 insertions(+), 224 deletions(-) delete mode 100644 custom_pages/westgate-pages/topbar-custom.js diff --git a/custom_pages/westgate-pages/topbar-custom.js b/custom_pages/westgate-pages/topbar-custom.js deleted file mode 100644 index 4f18c2b..0000000 --- a/custom_pages/westgate-pages/topbar-custom.js +++ /dev/null @@ -1,224 +0,0 @@ -/* ============================================================================ - SHADOWS OVER WESTGATE — top bar controller - ---------------------------------------------------------------------------- - Paste into ACP -> Settings -> Custom Content -> "Custom JavaScript". - (In the live theme this can instead live in the theme's client-side bundle.) - - WHY THIS FILE EXISTS - - The static page (join-the-team.html) needs NO JavaScript; it is pure - HTML/CSS (the only inline bit is an fallback). Home lives - in the westgate-pages plugin now (templates/home.tpl). - - The TOP BAR needs this small controller for: Forums mega-menu, inline - search, the mobile burger/drawer, and the drawer's Forums accordion. - - NODEBB-SPECIFIC NOTES - - NodeBB is a single-page app: it swaps #content on navigation instead of - reloading. So we DON'T bind to specific nodes on DOMContentLoaded — we use - event delegation on `document`, which keeps working across page changes and - even if the header is re-rendered. - - Inline