Skip to content

docs(link, tag, taggroup, tooltip): component analysis#5980

Merged
aramos-adobe merged 90 commits into2nd-gen-component-analysisfrom
aramos-adobe/swc1222-link-tag-group-migration-docs
Feb 19, 2026
Merged

docs(link, tag, taggroup, tooltip): component analysis#5980
aramos-adobe merged 90 commits into2nd-gen-component-analysisfrom
aramos-adobe/swc1222-link-tag-group-migration-docs

Conversation

@aramos-adobe
Copy link
Contributor

@aramos-adobe aramos-adobe commented Jan 22, 2026

Description

Creates AI-generated migration documentation to analyze component differences to guide SWC migration to S2, with human vetting. The documentation serves as a bridge between the migrated Spectrum 2 CSS work and the corresponding web components, in order to help engineers understand what needs to be implemented, updated, or aligned between the two systems to guide the development of 2nd generation web components.

This batch is for the components: Link, Tag, Tag group, Tooltip.

Motivation and context

  • Clear development roadmap: Provides comprehensive feature gap analysis for building 2nd generation web components
  • Implementation requirements: Identifies all features and capabilities that need to be implemented to match Spectrum 2 CSS and design specs
  • Breaking change transparency: Establishes implementation requirements and design changes that may lead to breaking changes and/or API changes for the next major version
  • Adoption planning: Enables developers and consuming teams to plan for 2nd gen web component adoption and understand migration effort required

Related issue(s)

SWC-1222

Screenshots (if appropriate)

N/A - Documentation only

Author's checklist

  • I have read the CONTRIBUTING and PULL_REQUESTS documents.
  • I have reviewed at the Accessibility Practices for this feature, see: Aria Practices
  • 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.

Manual review test cases

Documentation Quality

  • All files follow template structure with proper collapsible sections
  • CSS => SWC mapping tables use correct status values
  • Summary sections are concise and actionable
  • No broken markdown syntax

Cross-Reference Accuracy

  • CSS selectors match actual metadata.json files
  • SWC attributes match actual TypeScript source files
  • DOM structure comparisons match template files
  • Implementation gaps are complete and accurate

Device review

  • Did it pass in Desktop?
  • Did it pass in (emulated) Mobile?
  • Did it pass in (emulated) iPad?

marissahuysentruyt and others added 10 commits December 10, 2025 11:30
…tton, In-field button and In-field progress circle (#5738)

* chore(docs): barebones analysis for SWC-1218

* chore(docs): address feedback

* chore(docs): address feedback
…roadmap (#5729)

* docs(checkbox): migration roadmap

* docs(fieldgroup): migration roadmap

* docs(radio): migration roadmap

* docs(switch): migration roadmap

* docs(checkbox, field-group): update migration roadmap
- gives clarification on invalid checkbox consideration
- clarifies some of the implementation gaps for field group
… roadmap (#5775)

* docs: add component analysis docs

adds migration roadmap and component analysis docs for
meter, progress bar, slider, illustrated message and drop
zone.
@aramos-adobe aramos-adobe requested a review from a team as a code owner January 22, 2026 04:37
@changeset-bot
Copy link

changeset-bot bot commented Jan 22, 2026

⚠️ No Changeset found

Latest commit: 34ebc7d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

@aramos-adobe aramos-adobe added 2nd gen These issues or PRs map to our 2nd generation work to modernizing infrastructure. Component:Documentation Issues or PRs involving changes to docs or docs website. Component prefix is for Jira integration. Status:Ready for review PR ready for review or re-review. labels Jan 22, 2026
@aramos-adobe aramos-adobe self-assigned this Jan 22, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Jan 22, 2026

📚 Branch Preview Links

🔍 First Generation 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-5980

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.

@Rajdeepc
Copy link
Contributor

@aramos-adobe How can i test this?

@aramos-adobe
Copy link
Contributor Author

@Rajdeepc Just added a guide to test the documentation!

@marissahuysentruyt marissahuysentruyt self-requested a review January 22, 2026 15:47
Copy link
Collaborator

@marissahuysentruyt marissahuysentruyt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed was that there were some CSS callouts that were actually from S1, but most things should be for Spectrum 2.

I also had a bunch of questions for you, so I'm happy to pair if you want to talk through anything.

Comment on lines +104 to +110
spectrum-Link--quiet (if isQuiet)
spectrum-Link--[variant] (if variant)
spectrum-Link--static[StaticColor] (if staticColor)
is-hover (if isHovered)
is-active (if isActive)
is-focus-visible (if isFocused)
is-visited (if isVisited)"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally, I don't know that we need all of the parentheses and "(if staticColor)" etc. I'm on the fence about including the is-hover/is-active etc. interaction state class names. Aren't those more Storybook-specific so our controls show the states? I don't know that it hurts to keep them (and this wouldn't be the only component to have them listed here either).

Really, the point of my comment was that we could probably remove all of the if statements in the parentheses! 😆

Comment on lines +309 to +322
| `.spectrum-Tooltip--bottom-left` | | Missing from WC |
| `.spectrum-Tooltip--bottom-right` | | Missing from WC |
| `.spectrum-Tooltip--top-left` | | Missing from WC |
| `.spectrum-Tooltip--top-right` | | Missing from WC |
| `.spectrum-Tooltip--left-bottom` | | Missing from WC |
| `.spectrum-Tooltip--left-top` | | Missing from WC |
| `.spectrum-Tooltip--right-bottom` | | Missing from WC |
| `.spectrum-Tooltip--right-top` | | Missing from WC |
| `.spectrum-Tooltip--start` | | Missing from WC |
| `.spectrum-Tooltip--start-top` | | Missing from WC |
| `.spectrum-Tooltip--start-bottom` | | Missing from WC |
| `.spectrum-Tooltip--end` | | Missing from WC |
| `.spectrum-Tooltip--end-top` | | Missing from WC |
| `.spectrum-Tooltip--end-bottom` | | Missing from WC |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These all sound like "non-logical" properties instead. I wonder if you could figure out each one of these and map it back to the logical property version instead. For instance, bottom-left sounds like maybe it could be the same positioning as left-end? Does that make sense?

Copy link
Collaborator

@rise-erpelding rise-erpelding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is shaping up nicely, I read through Tag & Tag Group and am leaving comments for those, I'll come back for Link and Tooltip later!

- `.spectrum-TagGroup-actionButton`
- `.spectrum-TagGroup-helpText`
- `.spectrum-TagGroup-label`
- `.spectrum-TagGroup-tag`
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The template adds this .spectrum-TagGroup-tag class but we never use it in the CSS. (Therefore when you compare with the metadata.json it's not there.)

No action needed here, just wanted to point it out in case anyone is questioning why it's here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rise-erpelding, it could be a selector possibly used in the future?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Totally! I think that must have been the line of thinking in adding it in the template even though it was never used, and keeping a similar selector in 2nd-gen seems logical to me.

Again, nothing about this needs to be changed! I just wanted to point it out in case anyone else is wondering where it came from.


### SWC

**Note**: In Spectrum Web Components, this component is named `<sp-tags>` (not `<sp-taggroup>`).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to know ✨

Comment on lines +220 to +235
**Component structure:**

- Wrapper element with `spectrum-TagGroup` class and size modifiers (`--sizeS`, `--sizeM`, `--sizeL`)
- Optional `spectrum-TagGroup-label` for field labels (top or side positioning via `--sideLabel` modifier)
- `spectrum-TagGroup-tags` container with `role="list"` and `aria-label` for semantic grouping
- Individual tags receive `spectrum-TagGroup-tag` class for consistent styling
- Optional `spectrum-TagGroup-actionButton` for actions related to the tag group
- Optional `spectrum-TagGroup-helpText` for additional context or validation messages

**Key features:**

- Flexible layout supporting both top and side label positioning
- Semantic HTML structure with proper ARIA roles for accessibility
- Support for custom styles and modifiers for spacing
- Integration with FieldLabel, ActionButton, and HelpText components
- Tag wrapping behavior when horizontal space is limited
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While this isn't hurting anything, comparing to other components we've done usually this ### CSS Spectrum 2 changes is pretty short and sweet, either "no structural changes" or a short list of things that are different.

Copy link
Collaborator

@rise-erpelding rise-erpelding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few comments for Tooltip and Link!

cdransf and others added 10 commits February 12, 2026 16:41
…tton, In-field button and In-field progress circle (#5738)

* chore(docs): barebones analysis for SWC-1218

* chore(docs): address feedback

* chore(docs): address feedback
…roadmap (#5729)

* docs(checkbox): migration roadmap

* docs(fieldgroup): migration roadmap

* docs(radio): migration roadmap

* docs(switch): migration roadmap

* docs(checkbox, field-group): update migration roadmap
- gives clarification on invalid checkbox consideration
- clarifies some of the implementation gaps for field group
… roadmap (#5775)

* docs: add component analysis docs

adds migration roadmap and component analysis docs for
meter, progress bar, slider, illustrated message and drop
zone.
When changing doc structure or headings, point readers to Authoring
contributor docs for running the nav script and link verification.

(Cursor said it would do a better job if I added this to the
documentation.)
- Add content to the components README
- Update broken React links
- Add status note for POC components in migration analysis docs
- Update component status table
- name change "Spectrum 2 migration roadmap" to "Analyze rendering and
styling"
@rise-erpelding rise-erpelding force-pushed the 2nd-gen-component-analysis branch from 48fb02e to dfad5ac Compare February 12, 2026 22:41
@rise-erpelding rise-erpelding force-pushed the 2nd-gen-component-analysis branch 2 times, most recently from 5dece21 to 3a90238 Compare February 17, 2026 14:19
Copy link
Collaborator

@rise-erpelding rise-erpelding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one's really close for me! Just noting a few things that I think need changing, plus a couple of nits.

…github.com:adobe/spectrum-web-components into aramos-adobe/swc1222-link-tag-group-migration-docs
Copy link
Collaborator

@rise-erpelding rise-erpelding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All of my previous comments have been addressed, this looks fantastic! I made one very small suggestion about tooltip, but these are great component analyses!

Copy link
Collaborator

@marissahuysentruyt marissahuysentruyt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to approve! Thank you for sticking with this one!

I left one comment that isn't really blocking- just an enhancement to make the "no tip" thing for the S2 tooltip clearer. 👍

@aramos-adobe aramos-adobe merged commit a11eec5 into 2nd-gen-component-analysis Feb 19, 2026
18 checks passed
@aramos-adobe aramos-adobe deleted the aramos-adobe/swc1222-link-tag-group-migration-docs branch February 19, 2026 17:06
rise-erpelding added a commit that referenced this pull request Feb 19, 2026
* chore: add cursor prompt

* docs: add prompt output files for subset of components

* docs: barebones component analysis docs, prompt updates (#5720)

* chore(docs): barebones analysis for Field label, Help text, Picker button, In-field button and In-field progress circle (#5738)

* chore(docs): barebones analysis for SWC-1218

* chore(docs): address feedback

* chore(docs): address feedback

* docs(switch,radio,checkbox,fieldgroup): component analysis migration roadmap (#5729)

* docs(checkbox): migration roadmap

* docs(fieldgroup): migration roadmap

* docs(radio): migration roadmap

* docs(switch): migration roadmap

* docs(checkbox, field-group): update migration roadmap
- gives clarification on invalid checkbox consideration
- clarifies some of the implementation gaps for field group

* docs: textfield-based component analysis docs (#5741)

* docs(slider,meter,progressbar,dropzone,illustratedmessage): migration roadmap  (#5775)

* docs: add component analysis docs

adds migration roadmap and component analysis docs for
meter, progress bar, slider, illustrated message and drop
zone.

* chore(docs): 2nd gen component analysis for avatar, opacity checkerboard, swatch + swatchgroup, thumbnail (#5740)

* docs(button, buttongroup, actionbutton, actiongroup): component analysis (#5788)

* first docs feedback

* docs(link): WIP

* docs(s2): addressing feedback in link, tag, tooltip

* docs(swc): review feedback pt 3

* chore: add cursor prompt

* docs: add prompt output files for subset of components

* docs: barebones component analysis docs, prompt updates (#5720)

* chore(docs): barebones analysis for Field label, Help text, Picker button, In-field button and In-field progress circle (#5738)

* chore(docs): barebones analysis for SWC-1218

* chore(docs): address feedback

* chore(docs): address feedback

* docs(switch,radio,checkbox,fieldgroup): component analysis migration roadmap (#5729)

* docs(checkbox): migration roadmap

* docs(fieldgroup): migration roadmap

* docs(radio): migration roadmap

* docs(switch): migration roadmap

* docs(checkbox, field-group): update migration roadmap
- gives clarification on invalid checkbox consideration
- clarifies some of the implementation gaps for field group

* docs: textfield-based component analysis docs (#5741)

* docs(slider,meter,progressbar,dropzone,illustratedmessage): migration roadmap  (#5775)

* docs: add component analysis docs

adds migration roadmap and component analysis docs for
meter, progress bar, slider, illustrated message and drop
zone.

* chore(docs): 2nd gen component analysis for avatar, opacity checkerboard, swatch + swatchgroup, thumbnail (#5740)

* docs(button, buttongroup, actionbutton, actiongroup): component analysis (#5788)

* docs(s2): migrating new comments

* docs(s2): addressing more feedback

* docs(s2): addressing tooltip feedback

* docs(s2): update link, tag, group and tt

* docs(s2): updating feedback from marissa

* chore: add cursor prompt

* docs: add prompt output files for subset of components

* docs: barebones component analysis docs, prompt updates (#5720)

* chore(docs): barebones analysis for Field label, Help text, Picker button, In-field button and In-field progress circle (#5738)

* chore(docs): barebones analysis for SWC-1218

* chore(docs): address feedback

* chore(docs): address feedback

* docs(switch,radio,checkbox,fieldgroup): component analysis migration roadmap (#5729)

* docs(checkbox): migration roadmap

* docs(fieldgroup): migration roadmap

* docs(radio): migration roadmap

* docs(switch): migration roadmap

* docs(checkbox, field-group): update migration roadmap
- gives clarification on invalid checkbox consideration
- clarifies some of the implementation gaps for field group

* docs: textfield-based component analysis docs (#5741)

* docs(slider,meter,progressbar,dropzone,illustratedmessage): migration roadmap  (#5775)

* docs: add component analysis docs

adds migration roadmap and component analysis docs for
meter, progress bar, slider, illustrated message and drop
zone.

* chore(docs): 2nd gen component analysis for avatar, opacity checkerboard, swatch + swatchgroup, thumbnail (#5740)

* docs(button, buttongroup, actionbutton, actiongroup): component analysis (#5788)

* chore: add cursor rule for CONTRIBUTOR-DOCS

* docs: add CONTRIBUTOR-DOCSreminder to regenerate nav and verify links

When changing doc structure or headings, point readers to Authoring
contributor docs for running the nav script and link verification.

(Cursor said it would do a better job if I added this to the
documentation.)

* docs: move component analysis docs into CONTRIBUTOR-DOCS

* chore: add cursor prompt

* docs: add prompt output files for subset of components

* docs: barebones component analysis docs, prompt updates (#5720)

* chore(docs): barebones analysis for Field label, Help text, Picker button, In-field button and In-field progress circle (#5738)

* chore(docs): barebones analysis for SWC-1218

* chore(docs): address feedback

* chore(docs): address feedback

* docs(switch,radio,checkbox,fieldgroup): component analysis migration roadmap (#5729)

* docs(checkbox): migration roadmap

* docs(fieldgroup): migration roadmap

* docs(radio): migration roadmap

* docs(switch): migration roadmap

* docs(checkbox, field-group): update migration roadmap
- gives clarification on invalid checkbox consideration
- clarifies some of the implementation gaps for field group

* docs: textfield-based component analysis docs (#5741)

* docs(slider,meter,progressbar,dropzone,illustratedmessage): migration roadmap  (#5775)

* docs: add component analysis docs

adds migration roadmap and component analysis docs for
meter, progress bar, slider, illustrated message and drop
zone.

* chore(docs): 2nd gen component analysis for avatar, opacity checkerboard, swatch + swatchgroup, thumbnail (#5740)

* docs(button, buttongroup, actionbutton, actiongroup): component analysis (#5788)

* chore: add cursor rule for CONTRIBUTOR-DOCS

* docs(s2): re-review docs

* docs: add CONTRIBUTOR-DOCS reminder to regenerate nav and verify links

When changing doc structure or headings, point readers to Authoring
contributor docs for running the nav script and link verification.

(Cursor said it would do a better job if I added this to the
documentation.)

* docs: move component analysis docs into CONTRIBUTOR-DOCS

* chore: clean up component analysis docs

- Add content to the components README
- Update broken React links
- Add status note for POC components in migration analysis docs
- Update component status table

* first docs feedback

* docs(link): WIP

* docs(s2): addressing feedback in link, tag, tooltip

* docs(swc): review feedback pt 3

* docs(s2): migrating new comments

* docs(s2): addressing more feedback

* docs(s2): addressing tooltip feedback

* docs(s2): update link, tag, group and tt

* docs(s2): updating feedback from marissa

* docs(s2): re-review docs

* chore: add cursor prompt

* docs: add prompt output files for subset of components

* docs: barebones component analysis docs, prompt updates (#5720)

* chore(docs): barebones analysis for Field label, Help text, Picker button, In-field button and In-field progress circle (#5738)

* chore(docs): barebones analysis for SWC-1218

* chore(docs): address feedback

* chore(docs): address feedback

* docs(switch,radio,checkbox,fieldgroup): component analysis migration roadmap (#5729)

* docs(checkbox): migration roadmap

* docs(fieldgroup): migration roadmap

* docs(radio): migration roadmap

* docs(switch): migration roadmap

* docs(checkbox, field-group): update migration roadmap
- gives clarification on invalid checkbox consideration
- clarifies some of the implementation gaps for field group

* docs: textfield-based component analysis docs (#5741)

* docs(slider,meter,progressbar,dropzone,illustratedmessage): migration roadmap  (#5775)

* docs: add component analysis docs

adds migration roadmap and component analysis docs for
meter, progress bar, slider, illustrated message and drop
zone.

* chore(docs): 2nd gen component analysis for avatar, opacity checkerboard, swatch + swatchgroup, thumbnail (#5740)

* docs(button, buttongroup, actionbutton, actiongroup): component analysis (#5788)

* chore: update cursor rule for CONTRIBUTOR-DOCS

* docs: add CONTRIBUTOR-DOCS reminder to regenerate nav and verify links

When changing doc structure or headings, point readers to Authoring
contributor docs for running the nav script and link verification.

(Cursor said it would do a better job if I added this to the
documentation.)

* docs: move component analysis docs into CONTRIBUTOR-DOCS

* chore: clean up component analysis docs

- Add content to the components README
- Update broken React links
- Add status note for POC components in migration analysis docs
- Update component status table
- name change "Spectrum 2 migration roadmap" to "Analyze rendering and
styling"

* docs(s2): updating file structure

* docs(s2): addressing rise feedback

* docs(s2): updating tooltip docs

---------

Co-authored-by: Marissa Huysentruyt <marissa.huysentruyt@heysparkbox.com>
Co-authored-by: rise-erpelding <54716846+rise-erpelding@users.noreply.github.com>
Co-authored-by: Cory Dransfeldt <hi@coryd.dev>
Co-authored-by: Marissa Huysentruyt <69602589+marissahuysentruyt@users.noreply.github.com>
Co-authored-by: Rise Erpelding <rise@heysparkbox.com>
rise-erpelding added a commit that referenced this pull request Feb 23, 2026
* chore: add cursor prompt

* docs: add prompt output files for subset of components

* docs: barebones component analysis docs, prompt updates (#5720)

* chore(docs): barebones analysis for Field label, Help text, Picker button, In-field button and In-field progress circle (#5738)

* chore(docs): barebones analysis for SWC-1218

* chore(docs): address feedback

* chore(docs): address feedback

* docs(switch,radio,checkbox,fieldgroup): component analysis migration roadmap (#5729)

* docs(checkbox): migration roadmap

* docs(fieldgroup): migration roadmap

* docs(radio): migration roadmap

* docs(switch): migration roadmap

* docs(checkbox, field-group): update migration roadmap
- gives clarification on invalid checkbox consideration
- clarifies some of the implementation gaps for field group

* docs: textfield-based component analysis docs (#5741)

* docs(slider,meter,progressbar,dropzone,illustratedmessage): migration roadmap  (#5775)

* docs: add component analysis docs

adds migration roadmap and component analysis docs for
meter, progress bar, slider, illustrated message and drop
zone.

* chore(docs): 2nd gen component analysis for avatar, opacity checkerboard, swatch + swatchgroup, thumbnail (#5740)

* docs(button, buttongroup, actionbutton, actiongroup): component analysis (#5788)

* first docs feedback

* docs(link): WIP

* docs(s2): addressing feedback in link, tag, tooltip

* docs(swc): review feedback pt 3

* chore: add cursor prompt

* docs: add prompt output files for subset of components

* docs: barebones component analysis docs, prompt updates (#5720)

* chore(docs): barebones analysis for Field label, Help text, Picker button, In-field button and In-field progress circle (#5738)

* chore(docs): barebones analysis for SWC-1218

* chore(docs): address feedback

* chore(docs): address feedback

* docs(switch,radio,checkbox,fieldgroup): component analysis migration roadmap (#5729)

* docs(checkbox): migration roadmap

* docs(fieldgroup): migration roadmap

* docs(radio): migration roadmap

* docs(switch): migration roadmap

* docs(checkbox, field-group): update migration roadmap
- gives clarification on invalid checkbox consideration
- clarifies some of the implementation gaps for field group

* docs: textfield-based component analysis docs (#5741)

* docs(slider,meter,progressbar,dropzone,illustratedmessage): migration roadmap  (#5775)

* docs: add component analysis docs

adds migration roadmap and component analysis docs for
meter, progress bar, slider, illustrated message and drop
zone.

* chore(docs): 2nd gen component analysis for avatar, opacity checkerboard, swatch + swatchgroup, thumbnail (#5740)

* docs(button, buttongroup, actionbutton, actiongroup): component analysis (#5788)

* docs(s2): migrating new comments

* docs(s2): addressing more feedback

* docs(s2): addressing tooltip feedback

* docs(s2): update link, tag, group and tt

* docs(s2): updating feedback from marissa

* chore: add cursor prompt

* docs: add prompt output files for subset of components

* docs: barebones component analysis docs, prompt updates (#5720)

* chore(docs): barebones analysis for Field label, Help text, Picker button, In-field button and In-field progress circle (#5738)

* chore(docs): barebones analysis for SWC-1218

* chore(docs): address feedback

* chore(docs): address feedback

* docs(switch,radio,checkbox,fieldgroup): component analysis migration roadmap (#5729)

* docs(checkbox): migration roadmap

* docs(fieldgroup): migration roadmap

* docs(radio): migration roadmap

* docs(switch): migration roadmap

* docs(checkbox, field-group): update migration roadmap
- gives clarification on invalid checkbox consideration
- clarifies some of the implementation gaps for field group

* docs: textfield-based component analysis docs (#5741)

* docs(slider,meter,progressbar,dropzone,illustratedmessage): migration roadmap  (#5775)

* docs: add component analysis docs

adds migration roadmap and component analysis docs for
meter, progress bar, slider, illustrated message and drop
zone.

* chore(docs): 2nd gen component analysis for avatar, opacity checkerboard, swatch + swatchgroup, thumbnail (#5740)

* docs(button, buttongroup, actionbutton, actiongroup): component analysis (#5788)

* chore: add cursor rule for CONTRIBUTOR-DOCS

* docs: add CONTRIBUTOR-DOCSreminder to regenerate nav and verify links

When changing doc structure or headings, point readers to Authoring
contributor docs for running the nav script and link verification.

(Cursor said it would do a better job if I added this to the
documentation.)

* docs: move component analysis docs into CONTRIBUTOR-DOCS

* chore: add cursor prompt

* docs: add prompt output files for subset of components

* docs: barebones component analysis docs, prompt updates (#5720)

* chore(docs): barebones analysis for Field label, Help text, Picker button, In-field button and In-field progress circle (#5738)

* chore(docs): barebones analysis for SWC-1218

* chore(docs): address feedback

* chore(docs): address feedback

* docs(switch,radio,checkbox,fieldgroup): component analysis migration roadmap (#5729)

* docs(checkbox): migration roadmap

* docs(fieldgroup): migration roadmap

* docs(radio): migration roadmap

* docs(switch): migration roadmap

* docs(checkbox, field-group): update migration roadmap
- gives clarification on invalid checkbox consideration
- clarifies some of the implementation gaps for field group

* docs: textfield-based component analysis docs (#5741)

* docs(slider,meter,progressbar,dropzone,illustratedmessage): migration roadmap  (#5775)

* docs: add component analysis docs

adds migration roadmap and component analysis docs for
meter, progress bar, slider, illustrated message and drop
zone.

* chore(docs): 2nd gen component analysis for avatar, opacity checkerboard, swatch + swatchgroup, thumbnail (#5740)

* docs(button, buttongroup, actionbutton, actiongroup): component analysis (#5788)

* chore: add cursor rule for CONTRIBUTOR-DOCS

* docs(s2): re-review docs

* docs: add CONTRIBUTOR-DOCS reminder to regenerate nav and verify links

When changing doc structure or headings, point readers to Authoring
contributor docs for running the nav script and link verification.

(Cursor said it would do a better job if I added this to the
documentation.)

* docs: move component analysis docs into CONTRIBUTOR-DOCS

* chore: clean up component analysis docs

- Add content to the components README
- Update broken React links
- Add status note for POC components in migration analysis docs
- Update component status table

* first docs feedback

* docs(link): WIP

* docs(s2): addressing feedback in link, tag, tooltip

* docs(swc): review feedback pt 3

* docs(s2): migrating new comments

* docs(s2): addressing more feedback

* docs(s2): addressing tooltip feedback

* docs(s2): update link, tag, group and tt

* docs(s2): updating feedback from marissa

* docs(s2): re-review docs

* chore: add cursor prompt

* docs: add prompt output files for subset of components

* docs: barebones component analysis docs, prompt updates (#5720)

* chore(docs): barebones analysis for Field label, Help text, Picker button, In-field button and In-field progress circle (#5738)

* chore(docs): barebones analysis for SWC-1218

* chore(docs): address feedback

* chore(docs): address feedback

* docs(switch,radio,checkbox,fieldgroup): component analysis migration roadmap (#5729)

* docs(checkbox): migration roadmap

* docs(fieldgroup): migration roadmap

* docs(radio): migration roadmap

* docs(switch): migration roadmap

* docs(checkbox, field-group): update migration roadmap
- gives clarification on invalid checkbox consideration
- clarifies some of the implementation gaps for field group

* docs: textfield-based component analysis docs (#5741)

* docs(slider,meter,progressbar,dropzone,illustratedmessage): migration roadmap  (#5775)

* docs: add component analysis docs

adds migration roadmap and component analysis docs for
meter, progress bar, slider, illustrated message and drop
zone.

* chore(docs): 2nd gen component analysis for avatar, opacity checkerboard, swatch + swatchgroup, thumbnail (#5740)

* docs(button, buttongroup, actionbutton, actiongroup): component analysis (#5788)

* chore: update cursor rule for CONTRIBUTOR-DOCS

* docs: add CONTRIBUTOR-DOCS reminder to regenerate nav and verify links

When changing doc structure or headings, point readers to Authoring
contributor docs for running the nav script and link verification.

(Cursor said it would do a better job if I added this to the
documentation.)

* docs: move component analysis docs into CONTRIBUTOR-DOCS

* chore: clean up component analysis docs

- Add content to the components README
- Update broken React links
- Add status note for POC components in migration analysis docs
- Update component status table
- name change "Spectrum 2 migration roadmap" to "Analyze rendering and
styling"

* docs(s2): updating file structure

* docs(s2): addressing rise feedback

* docs(s2): updating tooltip docs

---------

Co-authored-by: Marissa Huysentruyt <marissa.huysentruyt@heysparkbox.com>
Co-authored-by: rise-erpelding <54716846+rise-erpelding@users.noreply.github.com>
Co-authored-by: Cory Dransfeldt <hi@coryd.dev>
Co-authored-by: Marissa Huysentruyt <69602589+marissahuysentruyt@users.noreply.github.com>
Co-authored-by: Rise Erpelding <rise@heysparkbox.com>
rise-erpelding added a commit that referenced this pull request Feb 23, 2026
* chore: add cursor prompt

* docs: barebones component analysis docs, prompt updates (#5720)

* chore(docs): barebones analysis for Field label, Help text, Picker button, In-field button and In-field progress circle (#5738)

* chore(docs): barebones analysis for SWC-1218

* docs(switch,radio,checkbox,fieldgroup): component analysis migration roadmap (#5729)

* docs: textfield-based component analysis docs (#5741)

* docs(slider,meter,progressbar,dropzone,illustratedmessage): migration roadmap  (#5775)

* chore(docs): 2nd gen component analysis for avatar, opacity checkerboard, swatch + swatchgroup, thumbnail (#5740)

* docs(button, buttongroup, actionbutton, actiongroup): component analysis (#5788)

* chore: update cursor rule for CONTRIBUTOR-DOCS

* docs: move component analysis docs into CONTRIBUTOR-DOCS

* docs(link, tag, taggroup, tooltip): component analysis (#5980)

---------

Co-authored-by: Marissa Huysentruyt <marissa.huysentruyt@heysparkbox.com>
Co-authored-by: Cory Dransfeldt <hi@coryd.dev>
Co-authored-by: Marissa Huysentruyt <69602589+marissahuysentruyt@users.noreply.github.com>
Co-authored-by: aramos-adobe <abdulr@adobe.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2nd gen These issues or PRs map to our 2nd generation work to modernizing infrastructure. Component:Documentation Issues or PRs involving changes to docs or docs website. Component prefix is for Jira integration. Status:Addressing feedback PR owner is addressing review comments and will change label back to "Ready for review" when ready.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants