[Project Solar / Phase 1 / Migration] Table & AdvancedTable carbonization

[shleewhite]

📌 Summary

If merged, this PR would carbonize the Table component and adds the relevant component tokens. It also adds a new state for the row that toggles the isSelected class.

• Table carbonization page
• AdvancedTable carbonization page

Note: for reorderable columns, the HTML element to show the preview column as you're dragging is appended to the DOM so it doesn't show as themed on the carbonization page. To validate that it works correctly, check the normal AdvancedTable showcase page and change the theme.

Copilot instructions

Read through similar carbonization pages under showcase/app/components/page-carbonization and compare those to the changes made here to ensure this PR aligns with previous carbonization efforts

🔗 External links

Jira ticket: HDS-6104

---

👀 Component checklist

• Percy was checked for any visual regression
• A changelog entry was added via Changesets if needed (see templates here)

💬 Please consider using conventional comments when reviewing this PR.

📋 PCI review checklist

• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
• If applicable, I've worked with GRC to document the impact of any changes to security controls.
  Examples of changes to controls include access controls, encryption, logging, etc.
• If applicable, I've worked with GRC to ensure compliance due to a significant change to the in-scope PCI environment.
  Examples include changes to operating systems, ports, protocols, services, cryptography-related components, PII processing code, etc.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hds-showcase	Ready	Preview	Jul 17, 2026 7:18pm
hds-website	Ready	Preview	Jul 17, 2026 7:18pm

[didoo]

@shleewhite I had a quick overview of the PR, and I think is better if you do also the AdvancedTable in the same PR (similar to what Kristin is doing with the form controls), not only to avoid back and forth between decisions but more importantly to have a more holistic view of the carbonization of these two very similar components. What do you think?
I know it's a big ask, given this is your first carbonization, but I think it's still something worth to do it in this way, even if it takes longer.

/cc @alex-ju let me/us know if you disagree with my assessment above

[alex-ju]

/cc @alex-ju let me/us know if you disagree with my assessment above

I don’t have strong opinions – if it’s easier for reviewers to compare and contrast both options simultaneously then that would be preferable indeed.

That being said, I see value in seeking early feedback on the Table component first, before replicating some of this work across the AdvancedTable.