Skip to content

feat(elements): add cms.v2-bridge-for-v3-users stylesheet + doc - #685

Open
wesleyboar wants to merge 1 commit into
TACC:epic/v3from
wesleyboar:docs/cms-v2-bridge-for-v3-users
Open

feat(elements): add cms.v2-bridge-for-v3-users stylesheet + doc#685
wesleyboar wants to merge 1 commit into
TACC:epic/v3from
wesleyboar:docs/cms-v2-bridge-for-v3-users

Conversation

@wesleyboar

@wesleyboar wesleyboar commented Aug 6, 2026

Copy link
Copy Markdown
Member

Overview

Adds a HOWTO note for core-styles.cms.v2-bridge-for-v3-users.css — for v3 sites whose CMS content still uses <h2> as an intro paragraph (instead of <p class="h2">) and needs that look restored after upgrading.

Related

Changes

  • added a HOWTO.md tip under "1. Base" showing how to load core-styles.cms.v2-bridge-for-v3-users.css

Notes

The stylesheet itself is intentionally not added here — it'll arrive via the merge of main after #683 lands, rather than being hand-ported to this branch's .postcss convention ahead of that.

No CHANGELOG entry and no version bump, per current release-via-GitHub-Releases process.

@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

Show how to append core-styles.cms.v2-bridge-for-v3-users.css atop
core-styles.cms.css for v3 sites whose CMS content still uses <h2> as an
intro paragraph.

The stylesheet itself isn't added here — it'll arrive via the merge of
main after TACC#683 lands, rather than being hand-ported.
@wesleyboar
wesleyboar force-pushed the docs/cms-v2-bridge-for-v3-users branch from 36aa2bb to aff86fa Compare August 6, 2026 23:50
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