wtclaude
3d6b2e23a7
Phases 3-4 of docs/website/THEMING_AND_NAV.md. Three presets, the curated font shortlist, and /admin/appearance to drive them. The design put the presets in theme.css as [data-theme] blocks. That does not work: SiteContext writes --accent as an inline style on <html>, which beats any attribute-selector block, so a preset's accent would have been painted over by BRAND_ACCENT_COLOR while getPublic().brand.accent -- the value the Android app themes itself from -- reported the other one. Presets now live in server/src/config/themePresets.js. themeResolve.js layers :root <- preset <- custom per field into a token map, getPublic() returns it as `theme`, and the client writes it onto <html>. One authority for the merge, and brand.accent is by construction the accent the site paints. theme.css's :root is untouched, so an instance with no row gets no theme block and renders as today. Also: presets carry the full 15-token palette (eight would have left Fantasy with blue-grey borders); the option catalog is served from GET /settings/theme/options so the form cannot offer what the server rejects; validation is strict on write and forgiving on read; and the Discord bot now fetches the effective accent instead of its boot-time env copy. Fixes a Phase 0 bug in passing: settings/nav.controller.js imported the logger factory rather than calling it, so a DB fault would have thrown a TypeError inside the catch instead of returning 500. Co-Authored-By: Claude <noreply@anthropic.com>
52 lines
2.1 KiB
JavaScript
52 lines
2.1 KiB
JavaScript
// Read-only client for the main site's PUBLIC API (no shared secret — this is
|
|
// the same unauthenticated data any visitor's browser can fetch). Used by
|
|
// /wiki (search) and /announce (re-post an existing news item). Distinct from
|
|
// botInternalClient.js, which is the shared-secret-gated server<->bot channel.
|
|
const createLogger = require('../utils/logger')
|
|
|
|
const log = createLogger('site-api')
|
|
|
|
const BASE_URL = (process.env.SITE_PUBLIC_URL || 'http://localhost:3000/api/v1/public').replace(/\/+$/, '')
|
|
const TIMEOUT_MS = 5000
|
|
|
|
async function call(path) {
|
|
const controller = new AbortController()
|
|
const timeout = setTimeout(() => controller.abort(), TIMEOUT_MS)
|
|
try {
|
|
const res = await fetch(`${BASE_URL}${path}`, { signal: controller.signal })
|
|
const data = await res.json().catch(() => null)
|
|
// Public content routes 503 with this shape while the site is in
|
|
// maintenance mode (see server/src/middleware/siteMode.js) — surface it
|
|
// distinctly so commands can show a clear message instead of a generic error.
|
|
if (res.status === 503 && data?.mode === 'maintenance') {
|
|
return { ok: false, maintenance: true, message: data.message }
|
|
}
|
|
if (!res.ok) return { ok: false, error: `site responded ${res.status}` }
|
|
return { ok: true, data }
|
|
} catch (err) {
|
|
log.warn('site API call failed', { path, message: err.message })
|
|
return { ok: false, error: err.message }
|
|
} finally {
|
|
clearTimeout(timeout)
|
|
}
|
|
}
|
|
|
|
// The site's public settings, including the brand block. Used for the embed
|
|
// accent (see brand.js): the admin can theme the site at runtime, and the
|
|
// server resolves the effective accent into brand.accent, so this is how the
|
|
// bot's embeds track a theme change instead of being stuck on the value
|
|
// BRAND_ACCENT_COLOR had when the container started.
|
|
function getPublicSettings() {
|
|
return call('/settings')
|
|
}
|
|
|
|
function getNewsPost(idOrSlug) {
|
|
return call(`/posts/news/${encodeURIComponent(idOrSlug)}`)
|
|
}
|
|
|
|
function searchWiki(query) {
|
|
return call(`/wiki?q=${encodeURIComponent(query)}`)
|
|
}
|
|
|
|
module.exports = { getPublicSettings, getNewsPost, searchWiki }
|