Skip to content

PointSav Documentation

The engineering library for the PointSav platform — operating systems and services for regulated businesses that own their data, their AI, and their record-keeping outright. Where the monorepo holds the code, this wiki holds the reasoning: architecture, services, security, and the governance commitments that bind future development.

Historical revision — this record as it stood on 22 August 2026, not the current version. View the current record →

Wiki dark mode

The PointSav wiki supports light and dark colour schemes using semantic tokens from the platform design system. Dark mode reduces eye strain in low-light environments and is preferred by a significant proportion of readers. This article describes the implementation: how the theme is set, persisted across sessions, and toggled, together with the full colour palette for each mode.


How it works

Dark mode is controlled by a data-theme="dark" attribute on the <html> element. The wiki's CSS uses this attribute as a selector override:

/* Light (default) — defined on :root */
:root {
  --k-surface: #ffffff;
  --k-ink: #202122;
  /* ... */
}

/* Dark — overrides semantic tokens only */
:root[data-theme="dark"] {
  --k-surface: #101418;
  --k-ink: #e7e9ea;
  /* ... */
}

Only semantic tokens (surfaces, ink, borders, status colours) change between modes. Primitive tokens — the raw colour palette — remain unchanged. Adding dark mode support to a new component requires only that the component uses semantic tokens; no per-component [data-theme="dark"] selectors are needed.


Initialisation

Theme preference is stored in localStorage under the key k-theme. The chrome script resolves the initial theme by checking that stored value first and falling back to the operating system's prefers-color-scheme only when nothing has been stored, then applies it by setting data-theme on the document root and updating the toggle button's aria-pressed state and label. An integrator embedding this engine is expected to also inline an equivalent pre-paint snippet in <head> so the correct theme applies before first paint, rather than flashing the wrong one and correcting after load.

An explicit user choice stored in localStorage overrides the operating-system preference (prefers-color-scheme). If no choice has been stored, the OS preference is honoured.

On mobile, prefers-color-scheme is the primary trigger — most mobile readers rely on their OS setting and never encounter the manual toggle. The toggle component is the progressive-enhancement layer for readers who want to override. The <meta name="color-scheme" content="light dark"> declaration in the <head> prevents the browser from drawing a white flash before the inline script reads localStorage.


Toggle component

The theme control (.k-control--theme) uses aria-pressed and updates aria-label to describe both the action available and the current state — "Switch to dark theme (current: light)" and its inverse — rather than a bare action-only label. On click, the toggle sets data-theme on the document root and writes the new value to localStorage.


Colour palette

Light mode

Token Value Use
--k-surface #ffffff Page background
--k-ink #202122 Body text
--k-ink-secondary (defined alongside --k-ink) Secondary text, metadata
--k-link (defined alongside --k-ink) Hyperlinks

Dark mode

Token Value Use
--k-surface #101418 Page background
--k-surface-sunken #171c22 Site notice, footer
--k-surface-raised #1b2027 Mobile drawer
--k-ink #e7e9ea Body text
--k-ink-secondary #a6abb1 Secondary text
--k-border #3a4149 Borders
--k-link #7aa6f0 Hyperlinks
--k-link-hover #a3c1f5 Hyperlink hover state
--k-code-block-bg #2b303b Code block background

Code blocks stay dark in dark mode, with syntax highlighting switching to its own dark palette rather than following the same tokens as prose text. Two instance-specific overrides exist for the documentation and projects/corporate deployments, adjusting the accent color while the rest of the dark palette stays shared.

Wiki surface aliases

The wiki CSS names its semantic surfaces directly rather than through a separate short-form alias layer — --k-surface, --k-ink, --k-link, and the rest are the names components reference. There is no second --color-* naming tier over them.


See also

  • Theming via semantic tokens — the concept background for this article: why theming is semantic-token substitution, not a parallel stylesheet, and how the same pattern appears in Carbon, Material 3, and Radix
  • Wiki component library — the nine components that consume these dark-mode token overrides
  • Wiki typography system — the type stack that pairs with these colour settings
  • Design-system substrate — the token vault where semantic token values are defined and versioned
Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is currently a trade name of Woodfine Capital Projects Inc. ("Woodfine"), planned to become a wholly-owned Woodfine subsidiary upon incorporation. PointSav does not itself offer, sell, or solicit any security. Any securities offering associated with Woodfine's real-property direct-hold solutions is made exclusively by Woodfine, and only by means of the applicable Private Placement Memorandum.

No investment advice. This wiki's content is provided for engineering, operational, research, and development purposes. Nothing on this wiki constitutes investment advice or a solicitation to invest in any Woodfine partnership or direct-hold solution.

Intellectual property. The PointSav name, trade name, wordmark, and marks, together with all current and future PointSav- and Totebox-branded products, services, and offerings — and the software, source code, documentation, design system, and all related materials — are proprietary to Woodfine and its affiliates, except for components identified as open source. No rights are granted except as expressly set out in a written license or agreement. The full trademark notice appears in the footer of every page on this site.

Open source components. Portions of the platform are made available under permissive open-source licenses identified in the accompanying repository. Use of those components is governed by their respective license terms.

No warranty; informational use. Content on this wiki is provided for general informational purposes only and does not constitute a representation, warranty, or commitment with respect to product functionality, availability, pricing, or roadmap. Some articles describe planned or intended features, capabilities, and milestones — language such as "planned," "intended," "targeted," "may," and "expected" marks this forward-looking content, which is subject to change and does not constitute a commitment regarding future performance.

Confidentiality. Where an article describes an operational or deployment detail that is not intended for public disclosure, that article is not published on this wiki. Content here is general-purpose engineering documentation, not customer-specific configuration.

Jurisdiction. Woodfine Capital Projects Inc. is organized in British Columbia, Canada. References to the Sovereign Data Foundation on this wiki describe a planned or intended initiative only, not a current equity holder or active governance body.

Changes to this notice. PointSav may update this notice from time to time; the version posted on this page governs.

Not a filing system. This wiki is not a securities filing system, an electronic disclosure repository, or a substitute for SEDAR+ or any other regulatory filing system. Formal securities filings are made through the applicable regulatory filing system, not through this wiki.

Full disclaimer. This notice supplements, and does not replace, the full Disclaimers article. In the event of any conflict, the full Disclaimers article governs.

Read the full disclaimer →