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

docs: add tutor compatibility notes #1122

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

MaferMazu
Copy link
Contributor

@MaferMazu MaferMazu commented Sep 18, 2024

Description

This PR adds the compatibility notes in the README.
Also, it adds information on the initial page for documentation and is referenced on the installation process page.

Context: Sometimes, we need another Open edX release different from the latest. So, by adding this documentation, we can guide what tutor version the person should install for different Open edX releases.

How to test

  • Check it in the readme: https://github.com/eduNEXT/tutor/tree/mfmz/docs-tutor-version?tab=readme-ov-file#compatibility-notes
  • Check the build test in the actions of this PR.
  • Mount and env to see the changes (optional):
    • Create a virtualenv, virtualenv venv
    • Use the env, source venv/bin/activate
    • Install the requirements, pip install -r requirements/docs.txt
    • Enter in docs, cd docs/
    • Watch the doc, make watch
    • Review the docs/_build/html/index.html and see the Compatibility Notes, and review the docs/_build/html/install.html to check the download python package section.

Screenshots

Index page:
image

Install page:
image

@MaferMazu MaferMazu marked this pull request as draft September 18, 2024 16:06
@MaferMazu MaferMazu force-pushed the mfmz/docs-tutor-version branch 3 times, most recently from 804a395 to 35d8f87 Compare September 18, 2024 16:28
@MaferMazu MaferMazu marked this pull request as ready for review September 18, 2024 16:59
@MaferMazu
Copy link
Contributor Author

I also tried this:
image
It is more explicit, but I don't know if it is too much, and the actual version of this PR is enough.

@MaferMazu
Copy link
Contributor Author

@kdmccormick @regisb @sarina, could you help me review this PR?

@MaferMazu
Copy link
Contributor Author

I applied the feedback.

If you have more feedback, please let me know.

Screenshot
image

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.

2 participants