Docs for v1.5.1: glossary links in story step text + case-insensitive matching#2
Merged
Conversation
…ing (v1.5.1) Note that [[term]] resolves in a story step's answer text, not only in layer panels, and that term matching is case-insensitive. Bump documented version to 1.5.1.
There was a problem hiding this comment.
Pull request overview
Updates the Telar documentation to reflect v1.5.1 glossary behavior changes: glossary [[term]] links now work in story step answer text (not only in layer panels), and glossary term matching is case-insensitive.
Changes:
- Clarifies where glossary auto-links are applied (including story step answer text) and notes that step questions intentionally remain plain text.
- Documents case-insensitive glossary term resolution with examples (EN/ES).
- Bumps the documented Telar version/release date to v1.5.1 and adds a 1.5.1 changelog entry.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| docs/6-2-glossary.md | Updates glossary linking scope and adds a case-insensitive matching note (English). |
| docs/6-2-glossary.es.md | Mirrors the glossary documentation updates in Spanish. |
| CHANGELOG.md | Adds a 1.5.1 entry describing the documentation updates. |
| _config.yml | Updates telar_version and telar_release_date to 1.5.1 / 2026-06-10. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| If a `term_id` is not found in the glossary, a warning icon and error message appear in the build output and in the story panel. | ||
|
|
||
| {: .note } | ||
| > Term matching is case-insensitive. `[[loom]]`, `[[Loom]]`, and `[[LOOM]]` all resolve to the same entry, so you can write a term however reads best — for example an acronym as `[[IIIF]]`. |
| Si un `term_id` no se encuentra en el glosario, un ícono de advertencia y un mensaje de error aparecen en la salida de la *build* y en el panel de la historia. | ||
|
|
||
| {: .note } | ||
| > Los términos se reconocen sin distinción de mayúsculas. `[[loom]]`, `[[Loom]]` y `[[LOOM]]` resuelven a la misma entrada, así que puedes escribir un término como mejor se lea —por ejemplo, una sigla como `[[IIIF]]`. |
This file contains hidden or 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
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.
Documents the v1.5.1 glossary fixes:
[[term]]links now work in a story step's answer text (the main scrolling prose), not only in layer panels. The question line is a heading and is left as plain text.[[loom]],[[Loom]],[[IIIF]]all resolve).Changes:
6-2-glossary.md(+.es.md) "Where Links Work" and intro; case-insensitive note;telar_version-> 1.5.1; CHANGELOG entry. English and Spanish updated together.