Introduce courseNavigationBar on header slot

[diana-villalvazo-wgu]

Description

As part of the conversion of MFEs to frontend base, we figured it out that 3 different repos will need Course Navigation Bar (Learning, Discussions and Instructor), so instead of having repetitive code on 3 different repos we come up with the following approach:

• Moving Course Navigation Tab bar to frontend-base as a slot inside the header and adding the roles where this new slot will be active.
• We need to get courseId (now we are grabbing it from current location) and make a request using react-query to gather correct course metadata (contains tabs info).
• We added an slot for extra content in case MFE needs to add it (current use case: Learning MFE, courseware search).

Screenshot

[openedx-webhooks]

Thanks for the pull request, @diana-villalvazo-wgu!

This repository is currently maintained by @openedx/axim-engineering.

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.

Details

---

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.

[brian-smith-tcril]

@arbrandes do you remember which FWG meeting we discussed this in? I think I need to look through our discussion to remember how the "render conditionally based on role" part is supposed to work (IIRC we talked about apps having roles associated?)

[diana-villalvazo-wgu]

@arbrandes do you remember which FWG meeting we discussed this in? I think I need to look through our discussion to remember how the "render conditionally based on role" part is supposed to work (IIRC we talked about apps having roles associated?)

we discussed it on this one https://openedx.atlassian.net/wiki/spaces/COMM/pages/5255593985/2025-10-09+Frontend+Working+Group+Meeting+Notes+Shai-Hulud+Program+Dashboard+etc

For now i didn't introduce anything related to roles and just abstract how is working now (retrieving the enabled tabs from the course-metadata endpoint)

[mphilbrick211]

Friendly ping on this, @brian-smith-tcril @arbrandes

[arbrandes]

Looks good! I do have some questions and comments, but I think this would work, architecturally speaking. I know we discussed having a way to dynamically assign roles, but we can cross that bridge when we get there.

(Also, sorry it took a while to get here.)

[arbrandes]

I think we might want to use activeKey too, here, no? To give the user indication of which one is active.

[arbrandes]

I also just realized that openedx/frontend-app-instruct#32 is not doing the same thing. It's solving a similar problem, though, so we should keep both implementations in sync where it makes sense.

[holaontiveros]

shouldn't this base ID be a constant?

[holaontiveros]

I also just realized that openedx/frontend-app-instruct#32 is not doing the same thing. It's solving a similar problem, though, so we should keep both implementations in sync where it makes sense.

I think it got out of sync because there was extra work that was done in instruct after the decision of just migrating this ones as they were

I would say that it makes sense if we wrap this one up with the current changes and as inmediate followup we do the update so this one is more in sync with instruct dash, what do you think @arbrandes ?

[arbrandes]

@diana-villalvazo-wgu, mind addressing the unresolved comments? Thanks!

[arbrandes]

A few more questions and suggestions, if you don't mind. Thanks!

[arbrandes]

tabId doesn't actually exist, here. It's normalized out in service.ts. It would be best to create an actual type for a tab, so that Typescript would catch the issue for us.

[arbrandes]

This is the only place setCurrentTab is called. This is not going to survive navigation because we're using an href={tab.url} for each tab. The current tab should be derived fromlocation.pathname (or equivalent).

On the other hand, shouldn't we have a way to navigate() to tabs to avoid the full page reload, when possible?