Conversation
Signed-off-by: René <snooz@posteo.de>
Signed-off-by: René <snooz@posteo.de>
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-72.surge.sh/robotframework-RFCP-syllabus/ |
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-72.surge.sh/robotframework-RFCP-syllabus/ |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-72.surge.sh/robotframework-RFCP-syllabus/ |
Signed-off-by: René <snooz@posteo.de>
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-72.surge.sh/robotframework-RFCP-syllabus/ |
2025-12-06_00-21-54.mp4I implemented the glossary terms to be hovered and a dynamic glossary. The glossary is based on a json file. {
"term": "Named-Only Argument",
"aliasses": ["Named Argument"],
"abbreviation": "",
"definition": "An argument that must be provided by name (never positionally); typically defined after a \"Variable Number of Positional Arguments\" or explicitly marked with a label icon in docs, and can be mandatory or optional."
},the usage is like this in Markdown: Except for "Positional-Only Arguments", which are not part of this syllabus,
all arguments that are positioned before :term[Variable Number of Positional Arguments], :term[Named-Only Arguments]{term="Named-Only Argument"}, or :term[Free Named Arguments]{term="Free Named Argument"} in the argument interface of a keyword are :term[Positional or Named Arguments]{term="Positional or Named Argument"}.so either if the exact term is used: or in case a different grammatical form is used: |
Signed-off-by: René <snooz@posteo.de>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 18 out of 20 changed files in this pull request and generated 2 comments.
Files not reviewed (1)
- website/package-lock.json: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-72.surge.sh/robotframework-RFCP-syllabus/ |
Signed-off-by: René <snooz@posteo.de>
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-72.surge.sh/robotframework-RFCP-syllabus/ |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-72.surge.sh/robotframework-RFCP-syllabus/ |
Signed-off-by: René <snooz@posteo.de>
- [x] Revert to useMemo approach for entries and aliasToCanonicalSlug - [x] Remove unnecessary purifyRef and purifyReady state - [x] Simplify sanitization logic while maintaining security - [x] Ensure proper SSR handling - [x] Test and validate changes (TypeScript passes, dev server runs) - [x] Clean up build artifacts from repository - [x] Code review and security checks passed (CodeQL found no issues) <!-- START COPILOT CODING AGENT TIPS --> --- 💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey). --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: Snooz82 <41592183+Snooz82@users.noreply.github.com> Co-authored-by: René <snooz@posteo.de> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-72.surge.sh/robotframework-RFCP-syllabus/ |
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-72.surge.sh/robotframework-RFCP-syllabus/ |
Signed-off-by: René <snooz@posteo.de>
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-72.surge.sh/robotframework-RFCP-syllabus/ |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-72.surge.sh/robotframework-RFCP-syllabus/ |
|
Based on some of the feedback during community day, I wanted to raise two more points of interest before we merge this: 1. A Term should exist as 'a term', aliases should not have their own entry 2. Describe in the description if alternate word is an Alias or Abbreviation 3. (Optional) Allow for a 'backlink' generated solution in Glossary / linking. We could keep the current :term[...] notation and extend it only for the special cases where we want a glossary backlink. Examples: Proposal:
4. (Optional) Support for Rabbit Holes |
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-72.surge.sh/robotframework-RFCP-syllabus/ |
GerwinLaagland
left a comment
There was a problem hiding this comment.
Feedback will be raised as separate issues at a later date.
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-72.surge.sh/robotframework-RFCP-syllabus/ |


This PR implements a dynamic glossary with search and alias.
The glossary is stored in a JSON file (
website/static/glossary/glossary.json), so that the glossary definition can be used by dynamic glossary tool tips in all MarkDown documents.2025-12-06_00-21-54.mp4
I implemented the glossary terms to be hovered and a dynamic glossary.
The glossary is based on a json file.
{ "term": "Named-Only Argument", "aliasses": ["Named Argument"], "abbreviation": "", "definition": "An argument that must be provided by name (never positionally); typically defined after a \"Variable Number of Positional Arguments\" or explicitly marked with a label icon in docs, and can be mandatory or optional." },the usage is like this in Markdown:
so either if the exact term is used:
or in case a different grammatical form is used: