Skip to content

Define the portable Wippy frontend contract - #27

Open
AndrewKirkovski wants to merge 3 commits into
mainfrom
codex/wippy-fe-contract-docs
Open

Define the portable Wippy frontend contract#27
AndrewKirkovski wants to merge 3 commits into
mainfrom
codex/wippy-fe-contract-docs

Conversation

@AndrewKirkovski

Copy link
Copy Markdown
Contributor

Summary

  • make PrimeVue-theme-first portability the canonical frontend contract
  • distinguish runtime-backed theme semantics from compile-time Tailwind baselines
  • document source-backed theme switching through host.setThemeMode, @theme, AppConfig, and host.getThemeMode
  • define build ownership, import-map, casing, custom-composite, and unsupported project-bound rules
  • add generated token/Tailwind catalogues and fail-closed documentation/visual checks

Verification

  • frontend documentation publication gate passed
  • generated catalogues match the selected @wippy-fe/theme source
  • commit-bound visible-browser evidence checker passed
  • final cold review found no remaining blockers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant