Unify the dev guide + dev glossaries #433
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The change makes sense to me. Let's get it to green. |
sarina
force-pushed
the
unified-dev-glossary
branch
from
9b127c1 to
bbb2c11
Compare
|
Fixed it. Ended up having to rewrite the old glossary in the RST format, but on the plus side it looks better and |
salman2013
approved these changes
Nov 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the developer guide has a pretty comprehensive glossary (https://docs.openedx.org/en/latest/developers/references/developer_guide/glossary.html) and the developer section glossary is lean (https://docs.openedx.org/en/latest/developers/references/glossary.html) - here I unify one glossary, in the Developers section. @feanil what do you think? The glossary probably still needs editing as it has a bunch of edx.org specific stuff, but actually I think keeping a lot of that stuff makes sense as the terms do come up from time to time.
Also converted the dev glossary to a real Sphinx glossary : https://sublime-and-sphinx-guide.readthedocs.io/en/latest/glossary.html