Add automated glossary linking with complete term coverage#88
Add automated glossary linking with complete term coverage#88solzlivinglife wants to merge 1 commit into
Conversation
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-88.surge.sh/robotframework-RFCP-syllabus/ |
cbec970 to
2a4cb0d
Compare
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-88.surge.sh/robotframework-RFCP-syllabus/ |
|
There should not happen any renumbering of Learning Objectives and please do not use the glossary technique in Learning Objectives. |
|
In the glossary it not says everywhere However, that should be: This is part of a docusaurus plugin, which makes for the right formatting |
535f752 to
1d20cd1
Compare
|
@Snooz82 and @leeuwe, I've updated the PR to use the :term[] directive format as requested. -: Switched from custom component to Docusaurus :term[] directive Note on CI failure: |
1d20cd1 to
f2ab7ed
Compare
f32d6ff to
d77ac4c
Compare
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-88.surge.sh/robotframework-RFCP-syllabus/ |
- Changed glossary_linker.py to output :term[] format instead of <GlossaryTerm> - Removed GlossaryTerm React component and CSS (no longer needed) - Added learning_objectives.md to exclusion list - ~210 glossary links using Docusaurus :term[] directive - Rebased on latest upstream/main Per reviewer feedback, using existing Docusaurus :term[] plugin instead of custom component.
0a39ff2 to
731e592
Compare
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-88.surge.sh/robotframework-RFCP-syllabus/ |
Features: