Skip to content

feat(icons): publish 2nd-gen icon docs and make UI icons deliverable - #6733

Open
caseyisonit wants to merge 1 commit into
mainfrom
caseyisonit/docs-icon-phase-6-swc-2447
Open

caseyisonit wants to merge 1 commit into
mainfrom
caseyisonit/docs-icon-phase-6-swc-2447

Conversation

@caseyisonit

Copy link
Copy Markdown
Contributor

Description

Phase 6 of the Spectrum 2 icon work: publish consumer documentation for all three icon surfaces and pivot UI icons from internal-only to deliverable.

  • UI icons are now deliverable. <swc-ui-icon> (chevrons, checkmarks, arrows, and other control internals) ships from @adobe/spectrum-wc with its own consumer docs page next to workflow icons, instead of being internal-only.
  • Custom SVG contract documented. The <swc-icon> frame has a public docs page describing the contract for a slotted SVG (single <svg>, viewBox, no width/height, fill="currentColor").
  • Per-family usage docs for UI icons and the <swc-icon> frame, plus the 1st-gen icon migration guide, now ship in the production Storybook build (previously excluded as .internal pages).
  • Removed the internal shared-template catalog (icon/elements); the icon VRT fixtures now slot a workflow icon (Icon_ChevronDown) via unsafeSVG.
  • RFC updated to record the UI-icon deliverable pivot.
  • Build fixes: move the @adobe/spectrum-wc-icons ambient *.css module declaration into src/, and exclude **/*.vrt.ts from the swc declaration build so it no longer fails on the generated custom-elements.json import.

Motivation and context

The audience for these docs is consumers. Previously the UI-icon page, the <swc-icon> custom-SVG frame page, and the migration guide were all .internal and excluded from the published Storybook build, so a consumer following the published docs could not add a UI icon or a custom SVG icon without further guidance. Design also asked that UI icons be deliverable rather than internal-only.

Related issue(s)

  • SWC-2447

Screenshots (if appropriate)

N/A. Documentation and Storybook docs-page changes. Note: swc-icon VRT baselines will change because the reference fixture icon changed from the removed internal chevron to the workflow ChevronDown.

Author's checklist

  • I have read the CONTRIBUTING and PULL_REQUESTS documents.
  • I have reviewed the Accessibility Practices for this feature.
  • I have added automated tests to cover my changes.
  • I have included a well-written changeset if my change needs to be published.
  • I have included updated documentation if my change required it.

Phase 6 of the S2 icon work: publish consumer documentation for all three
icon surfaces and pivot UI icons from internal-only to deliverable.

- Un-internalize the UI icon (swc-ui-icon) and swc-icon frame docs pages and
  the 1st-gen icon migration guide so they ship in the production Storybook
  build alongside workflow icons.
- Document the custom SVG contract for swc-icon (single <svg>, viewBox, no
  width/height, currentColor fill).
- Reframe UI icons and the frame as deliverable in JSDoc and the ui-icons
  README.
- Remove the internal shared-template catalog (icon/elements); the icon VRT
  fixtures now slot a workflow icon (Icon_ChevronDown) via unsafeSVG.
- Record the UI-icon deliverable pivot in the icon RFC.
- Fix declaration builds: move the icons package ambient *.css module
  declaration into src/, and exclude **/*.vrt.ts from the swc dts build so it
  no longer fails on the generated custom-elements.json import.
@caseyisonit
caseyisonit requested a review from a team as a code owner September 11, 2026 00:41
@changeset-bot

changeset-bot Bot commented Sep 11, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 8dd7e4f

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions

Copy link
Copy Markdown
Contributor

📚 Branch Preview Links

🔍 Gen1 Visual Regression Test Results

When a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:

Deployed to Azure Blob Storage: pr-6733

If the changes are expected, update the current_golden_images_cache hash in the circleci config to accept the new images. Instructions are included in that file.
If the changes are unexpected, you can investigate the cause of the differences and update the code accordingly.

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