Update wcss type class utilization

[rmenner]

Resolves AlaskaAirlines/WebCoreStyleSheets#245 Created via auro cli migration tool.

Testing

Design approved ✅

• https://auro-accordion-pr184-7.surge.sh
• https://auro-accordion-pr184-7.surge.sh/api

Summary by Sourcery

Update demo HTML pages to align with revised CSS class utilization and theming structure for wcss.

Enhancements:

• Revise page titles to reflect "Demo" context for auro-accordion.
• Replace existing token stylesheet links with structured includes for Prism.js, legacy design tokens, and Alaska theme.
• Add Webcore Stylesheet Alaska theme bundle and retain demo-specific stylesheet references.
• Add comments clarifying legacy token usage and include minified CSS files.

[sourcery-ai]

Reviewer's Guide

Refactored demo HTML to update titles, enhance head section documentation, and replace CSS imports with legacy and theme-specific minified token and webcore stylesheet references.

File-Level Changes

Change	Details	Files
Updated HTML page titles for consistency	Replaced generator-focused title with demo-oriented title Standardized title element text across demo files	demo/api.html demo/index.html
Reorganized and documented CSS link imports	Inserted comments before each stylesheet block (Prism.js, legacy tokens, theme tokens, webcore, demo-specific) Standardized link tag attributes and structure	demo/api.html demo/index.html
Replaced CSS imports with legacy, theme-specific, and bundled stylesheet references	Switched design token paths to legacy and themes/alaska minified CSSCustomProperties Added webcorestylesheets Alaska theme bundle import Removed old unminified CSSCustomProperties links	demo/api.html demo/index.html

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @rmenner - I've reviewed your changes - here's some feedback:

• Consider extracting the repeated head section into a shared template or partial to reduce duplication across both demo files.
• Pin design token and webcore stylesheet versions explicitly instead of using @latest to avoid unexpected breaking changes in downstream consumers.
• Add Subresource Integrity (SRI) attributes to the external CDN link tags to improve security and ensure the resources haven't been tampered with.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments
- Consider extracting the repeated head section into a shared template or partial to reduce duplication across both demo files.
- Pin design token and webcore stylesheet versions explicitly instead of using @latest to avoid unexpected breaking changes in downstream consumers.
- Add Subresource Integrity (SRI) attributes to the external CDN link tags to improve security and ensure the resources haven't been tampered with.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[github-actions]

Surge demo deployment failed! 😭

[jordanjones243]

There is something I see in the DOM that is a little confusing. The button in which the trigger text is contained in has body-default class on it, but the trigger slot ends up having heading-2xs on it. I think the heading class is being applied, but it's hard to tell without digging deep into the DOM.

Happy to jump on a call if we need to look at it together.

[chrisfalaska]

There is something I see in the DOM that is a little confusing. The button in which the trigger text is contained in has body-default class on it, but the trigger slot ends up having heading-2xs on it. I think the heading class is being applied, but it's hard to tell without digging deep into the DOM.

Happy to jump on a call if we need to look at it together.

That DOM deep-digging has been a challenge in general with this component. The body-default is coming from the auro-button component default and the slot classes are coming form Accordion:

const triggerSlotClass = this.variant === 'sm' ? 'body-default' : this.variant === 'lg' ? 'heading-xs' : 'heading-2xs';

[blackfalcon]

🎉 This PR is included in version 5.2.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀