Skip to content
Historical revision — this record as it stood on 1 June 2026, not the current version. View the current record →

Wiki component library

Wiki component library

The PointSav wiki component library defines nine reusable interface units that together render a complete wiki article page in the app-mediakit-knowledge wiki engine. Each component targets Wikipedia's established layout conventions — following the leapfrog design philosophy — while applying current accessibility standards and the PointSav token system.


Architecture overview

A wiki article page is composed from a stack of components:

┌─────────────────────────────────────────────────────┐
│  wiki-drawer-mobile-nav  (compact viewports only)   │
├─────────────────────────────────────────────────────┤
│  wiki-article-header  (breadcrumb + H1 + badge + meta)│
├──────────────────┬──────────────────────────────────┤
│                  │  wiki-toc-sidebar  (right rail)  │
│  Article body    │  (desktop only)                  │
│  (prose)         ├──────────────────────────────────┤
│                  │  wiki-badge-tag (quality/category)│
├──────────────────┴──────────────────────────────────┤
│  wiki-article-footer  (categories + refs + edit)    │
├─────────────────────────────────────────────────────┤
│  wiki-pagination  (prev/next article in category)   │
└─────────────────────────────────────────────────────┘

Overlays (triggered by user action):
  wiki-modal-dialog     — image lightbox, search overlay
  wiki-dark-mode-toggle — persistent theme switch (site header)

Search:
  wiki-search-results   — results list (own page or in modal)

Components

wiki-article-header

Top-of-article surface. Renders four elements in sequence: (1) slug breadcrumb showing the article's category path, (2) the article H1 title from frontmatter, (3) an optional quality badge, and (4) a byline showing last-edited date and a history link.

Quality grades: Featured Article (gold), Good Article (green), A-class (blue), B-class (light blue), C-class (grey), Stub (light grey). Ungraded articles omit the badge slot.

Token: --ps-wiki-text-h1 = 2.25 rem (36 px at 17 px base).


wiki-article-footer

Bottom-of-article surface. Three sections: (1) category tag links, (2) a numbered references list using <ol id="ref-N"> for in-article back-links, and (3) an edit-on-GitHub link for contributors.


wiki-toc-sidebar

Sticky right-rail sidebar listing article headings (H2 and H3). On desktop (≥ 800 px) it uses position: sticky; top: 1rem. On compact viewports (≤ 799 px) it collapses to an inline <details> / <summary> toggle above the article body.

The active section is highlighted via a JavaScript IntersectionObserver watching all [id] heading anchors. When a heading enters the viewport, its table-of-contents entry receives aria-current="true" and the active visual style.


wiki-search-results

Ordered list of search hits returned by the Tantivy search engine. Each result displays the article title as a link and a plain-text excerpt of approximately 180 characters, truncated at a word boundary. The component wraps in aria-live="polite" so assistive technologies announce result-count updates.

API shape: POST /mcp, JSON-RPC 2.0, method search. Response: {query, count, hits: [{slug, title, snippet}]}. Snippets are plain text only. A zero-results state is toggled with the [hidden] attribute.


wiki-modal-dialog

Overlay using the native <dialog> element with showModal(). The native dialog element provides a built-in focus trap: all content outside the dialog is unreachable by keyboard until the dialog closes. Used for image lightboxes, the search overlay, and confirmation prompts. Closes on Escape (native browser behaviour) and on backdrop click.


wiki-dark-mode-toggle

A toggle button that sets data-theme="dark" on <html> and persists the choice in localStorage under the key ps-theme. On each page load, an inline script reads this value before the stylesheet renders, preventing a flash of the unintended theme. Falls back to prefers-color-scheme: dark if no explicit choice is stored.


wiki-badge-tag

Dual-purpose chip: (1) article quality grade badge — a non-interactive <span> with aria-label providing the full grade name — and (2) category tag links using <a> chips. Used in the article header (quality badge) and article footer (category tags).


wiki-pagination

Prev/Next article navigation within a category. The component is a three-column grid: previous article link (left), current category name link (centre), next article link (right). Each directional link carries rel="prev" / rel="next" for SEO and an aria-label providing the full adjacent article title for assistive technologies.

This component handles sequential article navigation. Numbered pagination for search results and category listings is a separate planned component.


wiki-drawer-mobile-nav

Slide-in left-panel navigation for compact (≤ 799 px) viewports. A hamburger trigger button opens the drawer. When open, the inert attribute is applied to the main content region and header, locking keyboard focus inside the drawer until it is dismissed. Closes on Escape or backdrop click.

The inert attribute is natively supported in Chrome 102+, Firefox 112+, and Safari 15.5+. A WICG polyfill (approximately 3 KB gzipped) covers older browsers.


Mobile discipline

All nine components are designed mobile-first against a 375 px reference viewport. The Inter typeface (UI and headings) and Source Serif 4 (body prose) are loaded as variable fonts via font-display: swap; fallback system fonts render immediately on slow connections — see wiki-typography-system.

Touch-target discipline applies across all interactive elements: trigger buttons, TOC entries, edit pencils, pagination links, toggle controls, and modal close targets each carry a 44 px × 44 px minimum touch target (WCAG 2.2 SC 2.5.8). No interaction depends on hover state — every hover affordance (page preview, citation tooltip, quality-badge popover) degrades to a tap-triggered equivalent.

Safe-area padding (env(safe-area-inset-*)) is applied to the shell chrome (wiki-drawer-mobile-nav trigger and footer region) to accommodate notched and dynamic-island displays. Content columns do not apply safe-area insets; only chrome elements that sit at the screen edge do.

Token dependency

All nine components draw exclusively from the PointSav token system defined in dist/tokens.css. No component introduces raw colour or dimension values. New wiki pages and templates add components without introducing new CSS variables.


See also

Important Information

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is a trade name of Woodfine Capital Projects Inc. ("Woodfine"). 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. See TRADEMARK.md in this repository for the full trademark notice.

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 →