Harbour rebrand
Identity, site and launch kit for the harbour trust.
Familiar parts: a button, an input, a tag.
Identity, site and launch kit for the harbour trust.
data-rebar-component (plus data-rebar-part/data-rebar-state if it has any internal structure or state worth targeting in a test or a re-skin).data-*/aria-* props through to the root DOM node.--rebar-* custom properties with sensible fallback values — never a hardcoded pixel or color.value/onChange) and uncontrolled (defaultValue) use, the same convention every existing Imitation follows.For anything bigger than a small fix, open an issue first describing what you're planning — this project's architecture (the placement layer, token-only theming, "defer to migration rather than fine-tune styling") is deliberate, and ref/PLAN.md/ref/ASSESSMENT.md already record a lot of "we tried this, here's why not." No write access to this repo is required to start: fork it, build the construct there against the checklist below, then open an issue linking your fork or branch asking for it to be adopted into the main project — a real, normal path in, not a formality.
Once you're building:
packages/core/src/components/Name.tsx, following the checklist above.packages/core/src/index.ts.apps/docs/src/data/constructTier.ts's CONSTRUCT_TIER.component map as "imitation" — every name in the generated prop table must appear there, or the tier lookup throws.apps/docs/scripts/generate-props.mjs's scan list so pnpm run generate:props (or the app's own predev/prebuild hooks) picks up its prop table.apps/docs/src/app/imitations/<kebab-name>/page.tsx with a real, live-rendered example — not just a props table and prose.pnpm run lint, test, build, and typecheck at the repo root — the same four checks CI runs on every PR, in that order.