Paragon without bootstrap

[bradenmacdonald]

This is a Claude-generated version of Paragon that doesn't use Bootstrap at all.

▶️ Preview it using the new Storybook site

Concern	Old	This prototype
Behavior	react-bootstrap	React Aria (useButton, useFocusRing)
Styling	Bootstrap 4 SCSS, global classes	CSS Modules over the same --pgn-* tokens
Theming API	style-dictionary → CSS vars	Unchanged — imported verbatim (src/tokens.css)
Types	mixed .jsx/.tsx	100% TypeScript
Build	Babel + tsc + Makefile	Vite library mode + vite-plugin-dts
Tests	Jest	Vitest + Testing Library
Docs	Gatsby + react-docgen v5	Storybook 10 (props from TS types)

Features:

• Goal is to be fully compatible with the React component API and design tokens API.
• Better accessibility than before, since it's based on react-aria-components instead of Bootstrap
• 100% typed with TypeScript
• Docs site matches the old docs site in functionality, but has a way simpler architecture using Storybook
• Storybook provides a typed UI form that updates both the example JSX code and live preview. You can also edit the JSX code in any of the examples like you could on the old docs site.
  
  

[netlify]

✅ Deploy Preview for paragon-openedx-v23 ready!

Name	Link
🔨 Latest commit	c4e9625
🔍 Latest deploy log	https://app.netlify.com/projects/paragon-openedx-v23/deploys/6a6135308994c80007dbc317
😎 Deploy Preview	https://deploy-preview-4384--paragon-openedx-v23.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[openedx-webhooks]

Thanks for the pull request, @bradenmacdonald!

This repository is currently maintained by @openedx/committers-paragon.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Update the status of your PR

Your PR is currently marked as a draft. After completing the steps above, update its status by clicking "Ready for Review", or removing "WIP" from the title, as appropriate.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.