№ 01 · SYSTEMREC / azwerks-portfolio-foundation
candidate

azwerks portfolio foundation

The static-first Astro foundation for the public werkregister, wired to existing Radium React components through the website adapter layer.

Foundation implementation report, root layout, Radium CSS entry, and adapter source files.

  • Astro
  • React
  • Radium
  • static-first
Domainpublic-registerVersion0.1.0Updated2026-07-01MaintainerazwerksProofpartial

Overview

01

What it is

The static-first Astro foundation for the public werkregister, wired to existing Radium React components through the website adapter layer.

Canonical facts

Domain
public-register
Version
0.1.0
Updated
2026-07-01
Maintainer
azwerks
Proof
partial
  • The foundation is implemented, but deployment preparation and quality gates remain open.
  • The record documents repository work only; it does not claim production adoption.

How the record thinks

02

Key decisions

01

Decision

How should the website consume the design system?

ChosenUse Astro plus existing React/JSX Radium components through `src/components/azwerks/` adapters.

This preserves vendor source, keeps imports auditable, and avoids recreating components.

Alternatives considered

  • Copy component source locally — Would fork the source of truth and increase drift risk.
  • Use the browser global bundle — Would reduce type safety and weaken static rendering.

Consequences accepted

  • Adapters must be extended deliberately as new surfaces need components.
  • Interactive components need explicit hydration only where behavior requires it.
Recorded
2026-06-30
Source
architecture plan

Lineage

03

History

Operations

Foundation

  1. Foundation2026-06-30

    completed

    Wire Astro and React foundation

    Created the static Astro foundation, React integration, and initial smoke route.

    Intent
    Prove that the existing Radium package can be consumed without editing vendor source.
    Action
    Configured Astro, added React integration, and created the root layout plus smoke route.
    Result
    The site builds static routes and renders existing Radium React components.

    This is implementation proof only; production content remains limited.

  2. Foundation2026-06-30

    completed

    Import Radium CSS once

    Created a local Radium CSS entry and imported it through the base layout.

    Intent
    Keep token and visual foundations centralized.
    Action
    Imported the vendor Radium CSS through `src/styles/radium.css` and the root layout.
    Result
    Public routes share the same Radium token foundation.

    Theme and visual regression coverage still need quality-phase checks.

How do you know?

04

Evidence

03

Foundation implementation report

reviewed

Documents the Astro, React, Radium import, adapter strategy, and smoke route verification.

File:
docs/azwerks-portfolio-foundation-implementation-report-v1.0.md
State:
source-cited

The report covers foundation behavior, not final surface quality.

Base layout source

reviewed

Shows the single Radium CSS import and document shell used by public routes.

File:
src/layouts/BaseLayout.astro
State:
source-cited

Radium CSS entry

reviewed

Shows the local site CSS entry that imports the vendor Radium stylesheet once.

File:
src/styles/radium.css
Layer:
style foundation

This proves import strategy, not visual regression coverage.

Unresolved

05

Open matters

02

Matter ledger

Open matters stay visible and separate from decisions.

Open implementation matters

  1. Open questionmat-foundation-deployment-prep2026-07-01

    open

    Prepare deployment and release checks

    The foundation builds locally, but deployment configuration, release checks, and final public hosting behavior are not complete.

    Position
    Keep the foundation public as a repository implementation record while marking deployment as open.

    Local build success is not a production launch claim.

  2. Open questionmat-search-fallback

    open

    Add static search fallback

    The command index still needs a real no-JS search fallback route or equivalent public search surface.

    Position
    Keep `/work/` as a temporary fallback until the search prompt adds the dedicated route.

    Command overlay behavior is not a full search implementation.

Links

06

Relations

Relations

How azwerks portfolio foundation relates to the rest of the register.

Register dependencies

COLOPHON · № 01REC / azwerks-portfolio-foundation
Created
Updated
Record ID
REC / azwerks-portfolio-foundation
Version
0.1.0
State
candidate
Maintained by
azwerks
Derived from
Foundation implementation report, root layout, Radium CSS entry, and adapter source files.

LimitsRepository implementation record; public deployment, search, and full quality coverage are not complete.