Jswope00/educator hanbook reorg

[jswope00]

Two commits here:

Rework the home page
One reworks the home page. Added Core Contributor Handbook. Eliminated several redundancies with roles. Most concepts, how-to's etc were showing up twice via the User Role dropdown and as their own TOC entry:

In the case of translators, had to move concepts and how-tos index pages to the appropriate Translators home page, since those were only on the main home page. They belong on Translators home page.

Merge redundant Getting Help Pages
We had two getting help pages. One was older and had some dead links and outdated information. Merged into one page and made sure internal docs point to that page.

[openedx-webhooks]

Thanks for the pull request, @jswope00!

This repository is currently maintained by @openedx/docs-openedx-org-maintainers.

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.

[sarina]

Acknowledging review request, I have some PTO next week but I'll get to this the week after next.

[cassiezamparini]

@jswope00 Awesome! Thank you! Reviewed and approved on my end.

cc. @mphilbrick211

[mphilbrick211]

all set!

[jswope00]

This is a screenshot of the main changes to the homepage where Handbook and Release guides are now added below the existing Role guides. And the left sidebar mimics the structure of the homepage:

[cassiezamparini]

Thanks @jswope00. Exciting! I appreciate the screenshot. We'll just wait on Sarina's review.

Looking forward to populating the content!

[cassiezamparini]

@sarina Any way you could possibly review this this week or next? 😄

[sarina]

Can we get in the habit of setting up redirects when we delete a file? source/site_ops/install_configure_run_guide/front_matter/getting_help.rst was deleted.

[sarina]

Here's where to set up redirects: https://github.com/openedx/docs.openedx.org/blob/main/source/conf.py#L60-L63