Fixes for XBlock Editors, Frontend Architecture, and Unit Navigation Tabs (#2690, #2688, #2687)

[bhanu2006-24]

🎯 Context

This PR addresses multiple open issues in openedx/frontend-app-authoring:

• Pluggable XBlock React Editors #2688: Pluggable XBlock React Editors
• Authoring Frontend Arch Improvements #2687: Authoring Frontend Architecture Improvements
• Unit Navigation Tabs have ugly rounding/borders #2686: Unit Navigation Tabs have ugly rounding/borders

🔧 What I Did

• Implemented adjustments for the Pluggable XBlock React Editors to improve flexibility.
• Applied improvements to the authoring frontend architecture for cleaner structure and maintainability.
• Updated the Unit Navigation Tabs styling to resolve the rounding/border inconsistencies.

⚠️ Important Note

I tried to fix these issues with my knowledge and some help from AI.
I was not able to run or test the app locally, so these changes are unverified.
I hope this does not break existing code, but please review carefully.

🚀 Highlights

• Consolidates fixes for three related issues.
• Provides a straightforward attempt to improve editor integration, architecture, and UI consistency.
• Ready for review and further refinement by maintainers.

[openedx-webhooks]

Thanks for the pull request, @bhanu2006-24!

This repository is currently maintained by @bradenmacdonald.

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

🔘 Submit a signed contributor agreement (CLA)

⚠️ We ask all contributors to the Open edX project to submit a signed contributor agreement or indicate their institutional affiliation.
Please see the CONTRIBUTING file for more information.

If you've signed an agreement in the past, you may need to re-sign.
See The New Home of the Open edX Codebase for details.

Once you've signed the CLA, please allow 1 business day for it to be processed.
After this time, you can re-run the CLA check by adding a comment below that you have signed it.
If the CLA check continues to fail, you can tag the @openedx/cla-problems team in a comment for further assistance.

🔘 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.

---

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.

[bradenmacdonald]

Hi @bhanu2006-24,

Thanks for this contribution! Before we can review your PR, we'll need you to please sign the contributor license agreement. Please also take a look at the AI policy - we'll need you to specify which AI tool(s) were used in creating this PR.

Finally, reviewing and finishing up a large PR is slow for everyone involved. Would it be possible for you to split this into three separate PRs, one for each issue? If the issues or the fixes don't depend on each other, it's much easier for us to review small, focused PRs.

Thanks! Let me know if you have any questions and you can ask here or on Slack for help as needed.

[bhanu2006-24]

Hello @bradenmacdonald,

I’m very new to open-source contributions and am trying to learn the correct process. For this work I used Antigravity IDE along with Gemini 3 and Claude as AI assistance, combined with my own understanding.

Could you please guide me on how to properly sign in under the Contributor License Agreement (CLA) and complete the required steps? I want to make sure I follow the right procedure and contribute in the correct way.

Thank you for your time and support!

[mphilbrick211]

Hi @bhanu2006-24 - thank you for this contribution! Please let me know if you have any questions regarding submitting a CLA form. Once that is complete, we can get this reviewed. Thanks!