equinor / equinor/component-contracts
Migration from the meetup POC
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Tracking issue for moving the "Teach AI your design system" POC (private repo) into this public home, per its issue #43. The plan of record lives there; the headlines:
- [ ] pnpm workspaces done properly from day one (the POC's packages were standalone by necessity)
- [ ] Packages: contracts + emitters + parity harness, token build, CLI, Storefront, demos
- [ ] GitHub Pages via Actions source (upload-pages-artifact + deploy-pages), publishing the repo root so relative paths hold; Storefront as an MPA with cross-document view transitions
- [ ] Clean history: content migrates as fresh commits, no POC history carried
- [ ] Speaker material does not migrate
- [ ] Sequence with the per-opsz typography ramp (POC issue #48) so the new repo never carries the flat correction, and consider the ceil4 box question (POC issue #50) while the ramp is open
- [ ] Equinor font stays CDN-only (licence); Inter and CommitMono vendored under OFL
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the migration plan in the private POC's issue #43 and inspecting the current repository root. Use the listed package, GitHub Pages, typography, font, and history requirements to define the work; done means the POC is migrated into the public repository without speaker material or POC history and all listed checklist items are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- build-system, devops, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100