fix: remove unnecessary help urls tokens

[DeimerM]

Description

This PR is intended to remove the help tokens that are no longer referenced within the Open edX repositories. Specifically, a search was conducted across the openedx organization to find references to the functionalities of the help tokens tool.

It is important to note that this PR is part of a commitment made in the following PR: #37493, where these tokens were updated to use articles from the official Open edX documentation.

Research Summary

After searching for these tokens across the openedx organization, we obtained the following results, which show the tokens that were found and the location (repository) where they were identified:

• CMS

Token	Location
home	frontend-app-authoring
certificates	frontend-app-authoring, openedx-platform - legacy template
textbooks	frontend-app-authoring
content_highlights	frontend-app-authoring
import_course	frontend-app-authoring, openedx-platform - legacy template
social_sharing	frontend-app-authoring
default	frontend-app-authoring
export_course	frontend-app-authoring
visibility	frontend-app-authoring
grading	frontend-app-authoring, openedx-platform - legacy template
outline	frontend-app-authoring
group_configurations	frontend-app-authoring, openedx-platform - legacy template
enrollment_tracks	frontend-app-authoring, openedx-platform - legacy template
content_groups	frontend-app-authoring
team_course	openedx-platform - legacy template
team_library	openedx-platform - legacy template
export_library	openedx-platform - legacy template
import_library	openedx-platform - legacy template
welcome	openedx-platform - legacy template
schedule	openedx-platform - legacy template
container	openedx-platform - legacy template
advanced	openedx-platform - legacy template
video	openedx-platform - legacy template
unit	openedx-platform - legacy template
content_libraries	openedx-platform - legacy template
course_rerun	openedx-platform - legacy template

• LMS

Token	Location
progress	openedx-platform - legacy template
instructor	openedx-platform - legacy template
discussions	openedx-platform - legacy template
course	openedx-platform - legacy template
learnerdashboard	openedx-platform - legacy template
notes	openedx-platform - legacy template
programs	openedx-platform - legacy template

The criteria used for removal was straightforward: any token not found referenced within a repository was marked for deletion.

[openedx-webhooks]

Thanks for the pull request, @DeimerM!

This repository is currently maintained by @openedx/wg-maintenance-openedx-platform.

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.

[DeimerM]

Hi @sarina, @felipemontoya , As part of the commitment made in PR #37493, I have created this PR to remove the tokens for which I couldn't find any references within the openedx organization repositories.

[sarina]

@DeimerM thanks for this! Could you take a look at the failing tests?

[DeimerM]

@DeimerM thanks for this! Could you take a look at the failing tests?

Thanks a lot for pointing this out, @sarina. I have fixed the error, and now all the tests are passing.

[sarina]

@DeimerM I'm curious what it means when you've identified a token was used on "openedx-platform - legacy template" - does that mean that there are legacy templates that exist that still call these tokens?

[DeimerM]

@DeimerM I'm curious what it means when you've identified a token was used on "openedx-platform - legacy template" - does that mean that there are legacy templates that exist that still call these tokens?

Yes @sarina, that's correct. An example can be found here, where the schedule token is called:

openedx-platform/cms/templates/settings.html

Line 3 in 2248575

<%def name="online_help_token()"><% return "schedule" %></%def>

[sarina]

@DeimerM I'm wary about removing tokens that are still called in legacy pages, in case people are still using those legacy pages. I think we're safe to remove any tokens that are not being called at all in the platform, but for the ones that are still being called by legacy pages we should wait for the legacy pages to be removed. @feanil does that make sense?

[DeimerM]

@DeimerM I'm wary about removing tokens that are still called in legacy pages, in case people are still using those legacy pages. I think we're safe to remove any tokens that are not being called at all in the platform, but for the ones that are still being called by legacy pages we should wait for the legacy pages to be removed. @feanil does that make sense?

@sarina In this case, I am only removing the ones for which I found no references at all in the platform; for those that are still being called—even on legacy pages—I have left them intact.