Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feanil/unify docs #32780

Merged
merged 5 commits into from
Jul 19, 2023
Merged

feanil/unify docs #32780

merged 5 commits into from
Jul 19, 2023

Conversation

feanil
Copy link
Contributor

@feanil feanil commented Jul 18, 2023

Before this there were multiple documentation projects in edx-platform so it was hard to tell where to put information. After this change, the content of the guides project supersedes all the other docs projects and contains all the information they used to contain. So we remove the last other project (edx-platform Technical) and re-organize the docs repo which now contains only a single sphinx project.

  • feat!: Drop the separate technical docs.
  • feat!: Move the docs out of the guides subdirectory.
  • fix: Update openapi yaml location.
  • fix: Update conf paths to match the new docs layout.
  • docs: Update .readthedocs.yml to point to the sphinx config.

feanil added 5 commits July 18, 2023 14:29
BREAKING CHANGE: The technical docs will not be published independent of
the rest of the edx-platform docs.
Now that the content in `guides` is all of the edx-platform docs, move
them all into the top-level docs directory to reduce confusion.

BREAKING CHANGE: Guides are now just docs.  This will require updating
the publishing settings so that RTD looks for the conf in a different
location.
Now that there is only one sphinx project, the RTD config can be more
specific and stop relying on the old style config which is about to be
deprecated.
@feanil feanil requested review from a team July 18, 2023 20:41
Copy link
Contributor

@e0d e0d left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a brief statement of how the world will be different for docs consumers in the PR description would be valuable. Two sentences tops. I approve of the changes.

@feanil feanil merged commit 686cab0 into master Jul 19, 2023
@feanil feanil deleted the feanil/unify_docs branch July 19, 2023 12:39
@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX production environment.

@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX production environment.

@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX production environment.

@sarina
Copy link
Contributor

sarina commented Sep 30, 2024

This broke a link in OEP-50 -

The documentation for the available hooks at any point should be kept in-code at openedx/edx-platform. This location should contain a document that covers the design principles and details that did not land in the OEP as well as the final decisions made in the OEP. Also will index the list of hooks and their current status. It should not cover the history and all the previous states of the framework. It should reflect the latest way of thinking and examples of how to use the framework.

@feanil
Copy link
Contributor Author

feanil commented Nov 4, 2024

openedx/open-edx-proposals#644 should fix the broken link in a resilient way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants