-
Notifications
You must be signed in to change notification settings - Fork 11
docs: Rewrite and improve plugin documentation #39
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
Conversation
Updated structure, added version info, improved examples and linked external docs.
|
Thanks for the pull request, @maguilarUXUI! This repository is currently maintained by 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 approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo 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:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere 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: 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:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
|
Assign me |
|
Hi @arbrandes 👋 This PR is ready for review. Let me know if there’s anything I should revise. |
|
Hi @maguilarUXUI! If you haven't already, please make sure your manager reaches out to [email protected] to have you added to our existing agreement with edunext. Thanks! |
…ructure This commit updates the Tutor Paragon Plugin documentation to align with recent code changes and the approach outlined in the original proposal.
|
@Ang-m4 The corresponding changes were applied! |
Ang-m4
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @maguilarUXUI, overall this looks great, thanks for updating the docs for the tutor-mfe integration.
I left a comment regarding the local URLs so they point correctly to the MFE host.
|
|
||
| - **Error: "Expected at least 4 args"** | ||
| This occurs when the build job is invoked directly inside the container. Always run via Tutor: | ||
| * Local LMS: `http://local.openedx.io/static/paragon/themes/light/light.min.css` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| * Local LMS: `http://local.openedx.io/static/paragon/themes/light/light.min.css` | |
| * Local LMS: `http://<MFE_HOST>/static/paragon/themes/light/light.min.css` |
Now that the plugin leverages the tutor-mfe host extra files feature, the local URLs should point to the MFE host (by default: apps.local.openedx.io).
Clarifies when to use tutor config save, tutor dev stop, and tutor dev start when updating theme variables. Adds step-by-step instructions to the documentation under the Static Hosting section.
|
added changes @brian-smith-tcril @Ang-m4 |
|
Commenting to see if that kicks off the CLA check. |
|
Closing/reopening to kick off the CLA check. |
|
Closing/reopening (again) to kick off the CLA check. |
|
|
||
| * **Paragon 23+** | ||
| * **Open edX "Teak" release (or Tutor 20+)** | ||
| * **Tutor 20+** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should these say "greater than or equal to"? Do we think this plugin will stop working on Tutor 21 or Paragon 24?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My read was that the + implied >=, but I can see how someone might read that as 23.x or 20.x.
The pyproject.toml file currently has a tutor version requirement of tutor>=19.0.0,<21.0.0, and a tutor-mfe requirement of tutor-mfe @ git+https://github.com/overhangio/tutor-mfe.git@release.
The tutor-mfe version requirement should be updated once overhangio/tutor-mfe#267 and overhangio/tutor-mfe#264 make it into releases (as of writing the latest tutor-mfe release is v20.0.0 from June 27th).
I think for the README it makes sense to clearly imply >=, as we should expect to support this plugin beyond Paragon 23 and Tutor 20. That being said, major versions can include breaking changes, so it is quite possible this plugin will need to be updated to support any Tutor 21 or Paragon 23 changes.
…ersion compatibility This commit improves the documentation by: - Adding a new section titled “Loading Base Paragon Styles” to guide site operators on how to optimize performance by using shared styles. - Clarifying version compatibility in the “Version Compatibility” section.
|
I added the last changes! @brian-smith-tcril @Ang-m4 @sarina |
brian-smith-tcril
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall this is looking really good!
I left a couple of specific inline comments, and I also noticed a few general things:
- I'm not sure all of the formatting (
.. note::,.. code-block:: text, etc.) is working as expected. I was checking by reading from https://github.com/maguilarUXUI/openedx-tutor-plugins/tree/patch-1/plugins/tutor-contrib-paragon - This plugin isn't in the table on the main README (https://github.com/maguilarUXUI/openedx-tutor-plugins/tree/patch-1?tab=readme-ov-file#purpose)
|
|
|
For codeblock you just use this syntax: See https://raw.githubusercontent.com/overhangio/tutor-mfe/refs/heads/release/README.rst |
brian-smith-tcril
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks wonderful!
One tiny comment about some code block formatting, but once that's resolved this should be good to merge!
|
|
||
| - **Themes are not picked up when using --themes:** | ||
| The value for ``--themes`` must be a comma-separated list (no spaces), e.g. ``--themes theme-1,theme-2``. | ||
| ``https://cdn.jsdelivr.net/npm/@openedx/paragon@$paragonVersion/dist/core.min.css`` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
brian-smith-tcril
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect!
Thank you so much for putting this together!

This commit updates the Tutor Paragon Plugin documentation to align with recent code changes and the approach outlined in the original proposal. Key updates include:
PARAGON_THEME_SOURCES_PATHandPARAGON_COMPILED_THEMES_PATHare consolidated intoPARAGON_THEMES_PATH.PARAGON_ENABLED_THEMESis renamed toPARAGON_THEMES.PARAGON_SERVE_COMPILED_THEMESis replaced by thetutor-mfeplugin'sMFE_HOST_EXTRA_FILESsetting.core/) are placed directly withinPARAGON_THEMES_PATH.PARAGON_THEMES_PATH/<theme>/<theme>.min.css.tutor-mfeplugin'sMFE_HOST_EXTRA_FILESfeature, instead of adding a separate Nginx service.tutor-mfeplugin.