feat: add card in Pages and Resources to allow hiding the dates tab

[Anas12091101]

Description

This PR adds a Date Course App card to the Pages and Resources page, enabling course authors to hide the Dates tab from learners using the authoring MFE.

Useful information to include:

• Which user roles will this change impact? "Learner", "Course Author"
• Include screenshots for changes to the UI (ideally, both "before" and "after" screenshots, if applicable).

Screen.Recording.2026-01-21.at.7.36.57.PM.mov

Supporting information

openedx/platform-roadmap#392

Testing instructions

• Checkout to this branch in edx-platform.
• Make sure to restart your CMS once you switch to this branch; otherwise, the changes won't be reflected.
• Enable the ENABLE_DATES_COURSE_APP toggle in your settings.
• Navigate to the Pages and Resources page for any course in Studio.
• Confirm that the Dates card appears, as shown in the screen recording above.
• Disable the Dates app as demonstrated in the video.
• Verify that the Dates tab is no longer visible on the Learning MFE and themed pages.

Other information

Related edx-platform PR: openedx/openedx-platform#37923

Best Practices Checklist

We're trying to move away from some deprecated patterns in this codebase. Please
check if your PR meets these recommendations before asking for a review:

• Any new files are using TypeScript (.ts, .tsx).
• Avoid propTypes and defaultProps in any new or modified code.
• Tests should use the helpers in src/testUtils.tsx (specifically initializeMocks)
• Do not add new fields to the Redux state/store. Use React Context to share state among multiple components.
• Use React Query to load data from REST APIs. See any apiHooks.ts in this repo for examples.
• All new i18n messages in messages.ts files have a description for translators to use.
• Avoid using ../ in import paths. To import from parent folders, use @src, e.g. import { initializeMocks } from '@src/testUtils'; instead of from '../../../../testUtils'

[openedx-webhooks]

Thanks for the pull request, @Anas12091101!

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

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.45%. Comparing base (815b80a) to head (ac3e9ef).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2834   +/-   ##
=======================================
  Coverage   95.45%   95.45%           
=======================================
  Files        1330     1330           
  Lines       30573    30573           
  Branches     6949     6931   -18     
=======================================
  Hits        29182    29182           
- Misses       1323     1335   +12     
+ Partials       68       56   -12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bradenmacdonald]

Let me know when you'd like this reviewed and merged!

[Anas12091101]

Thanks @bradenmacdonald, the PR is now ready for review

[bradenmacdonald]

Sorry for the delay. I tested this and it's working fine.

I confirmed that:

• Putting ENABLE_DATES_COURSE_APP = True into edx-platform/cms/envs/private.py will show this new app, and otherwise it's hidden.
• Toggling the setting will hide the dates tab.

However, we need to fix the wording here.

Also, I will hold off on merging this PR until the platform PR is merged. But once it's merged, ping me anytime and I'll merge this one.

[bradenmacdonald]

This says that the toggle will control whether we "Allow learners to access the Dates page", but it actually only hides the tab. If learners have the URL, they are still "allowed" to access it. I think we need to clarify the wording.

[bradenmacdonald]

Suggested change

"yup": "*"

No need to mention yup if you're not using it.

[bradenmacdonald]

Please rebase this PR and make sure you are using the correct (latest?) version of NPM. It should not be showing all these "peer": true changes to package-lock.json. There should be < 30 lines changed from adding the new course-app-dates plugin. You'll need to reset the changes, upgrade NPM, and run npm install again.

[bradenmacdonald]

@Anas12091101 I merged your platform PR. Can you please rebase this PR and address my comments? Then I'll approve and merge it for you. Thanks for your patience with my slow reviews.

[bradenmacdonald]

Looks great! Thanks.