Skip to content

Evaluate intentionally-left off-scale spacing values (bucket B & C) #202

Description

@dprodger

Follow-up to #199.

During the #199 spacing-token adoption, some off-scale spacing/padding values were deliberately left as literals rather than snapped to the scale. This ticket is to decide their long-term treatment: introduce extended/component tokens, or keep them as documented intentional exceptions.

Bucket B — component-internal / structural (likely keep, or add named tokens)

  • Badge / pill insets: .padding(6), .padding(.vertical, 6), .padding(.vertical, 2) — e.g. RecordingRowView, AuthorityRecommendationView, RecordingDetailView, ArtistImageCarousel (PageDots), CommunityDataSection chips.
  • Button / toast vertical padding: 14ApproachNoteButton, ToastView.
  • DetailHeader title horizontal inset: 64 — clears the nav circle buttons.
  • Settings sub-item leading indent: 48SettingsView.

Bucket C — large page-level spacing (auth / onboarding / hero / empty-state)

  • 28 / 30 / 32 / 40 / 60 across the auth views, OnboardingPages / OnboardingView, AddToRepertoireSheet, AboutView, RecordingsListView, and empty-state paddings in RecordingsSection / PerformerRecordingsSection.

Decision needed

Per bucket, either:

  • (a) introduce extended/component tokens — e.g. spacingXXL = 32, spacingXXXL = 40; a badge-inset token; a control vertical-padding token; or
  • (b) keep as intentional literals, documented as exceptions in doc/design/layout.md.

Ref: doc/design/layout.md spacing scale; #199.

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions