Skip to content

Verify a Website component in the real Next and Tina pipeline #5048

Description

@isaaclombardssw

Part of #5046

Integrate one representative Website component from an exact published design-system beta version. Prove compatibility before bulk extraction or page migrations.

Acceptance checks:

  • Verify this site’s Tailwind 3 setup works with the library’s Tailwind 4 output without a site-wide upgrade, duplicate resets, class collisions or global style changes.

  • Check Next server/client rendering, hydration, fonts, image integration, CSS order, peer dependencies and one explicit Application fallback.

  • Verify Tina edit/preview, selected gradients and colour-picker behaviour; reproduce checks motivated by PR 💄 Redesign /consulting index + card colour tokens #4939.

  • Capture matched Before/After screenshots, keyboard/focus checks and bundle/performance observations; run lint, relevant tests and a production build.

  • Record package version/artifact, findings and the supported integration recipe. Surface incompatibilities before proceeding; keep the pilot reversible.

  • Work on a dedicated Website preview/integration branch, pin the exact beta package version and commit the lockfile. Keep this validation out of production; all full page migrations wait for the stable design-system release.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    • Status
      🤷‍♂️ Needs Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions