Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Created modular glossary & key concepts#181

Merged
validbeck merged 16 commits intomainvalidmind/documentation:mainfrom
beck/sc-4074/create-modular-glossaryvalidmind/documentation:beck/sc-4074/create-modular-glossaryCopy head branch name to clipboard
May 8, 2024
Merged

Created modular glossary & key concepts#181
validbeck merged 16 commits intomainvalidmind/documentation:mainfrom
beck/sc-4074/create-modular-glossaryvalidmind/documentation:beck/sc-4074/create-modular-glossaryCopy head branch name to clipboard

Conversation

@validbeck
Copy link
Collaborator

@validbeck validbeck commented May 3, 2024

Internal Notes for Reviewers

Screenshot 2024-05-03 at 2 44 48 PM
  • I've cleaned up the glossary page and added a few terms and sections, such as "Artificial intelligence"

Changes are live on the demo site: https://docs-demo.vm.validmind.ai/about/glossary/glossary.html

Modular glossary

  • This glossary is also now single-sourcing from the about/glossary folder via Quarto's includes function
  • The associated embed files are structured in _filename.qmd format (e.g. _validmind.qmd)
  • Comments in the code have been left on the relevant source files for instructional posterity

Certain entries in the glossary are "Key concepts" or part of the "Model documentation" and "Validation reports" embeds that are called on other pages (e.g. test suite)

Edit Image
New folder structure Screenshot 2024-05-03 at 2 25 10 PM
Main glossary file with includes Screenshot 2024-05-03 at 2 37 37 PM
Nested includes in the source files Screenshot 2024-05-03 at 2 35 44 PM

Key concepts

Screenshot 2024-05-03 at 2 28 29 PM

  • These live in the about/glossary/key_concepts folder
  • The main _key-concepts.qmd file (in turn sourcing from the folder, and also feeding into the main glossary) that gathers all these concepts togethers is in turn embedded in:
Page (demo site) New version Old version
Get started Screenshot 2024-05-03 at 2 46 56 PM Screenshot 2024-05-03 at 2 52 25 PM
Guides Screenshot 2024-05-03 at 2 47 57 PM Screenshot 2024-05-03 at 2 52 32 PM
Get started with the VM DevFramework Screenshot 2024-05-03 at 2 48 06 PM Screenshot 2024-05-03 at 2 52 39 PM
Run tests & tests suites Screenshot 2024-05-03 at 2 50 00 PM Screenshot 2024-05-03 at 2 52 44 PM

This enables us to edit the files in about/glossary/key_concepts instead of editing 4 pages each time!

Model documentation

Screenshot 2024-05-03 at 2 59 04 PM

  • In Guides > Working with model documentation the "Key concepts" section has been replaced with modular includes from the about/glossary/model_documentation folder
  • The associated embed files are structured in _filename.qmd format (e.g. _doc-intro.qmd)
New working with docs Old working with docs
Screenshot 2024-05-03 at 2 55 25 PM Screenshot 2024-05-03 at 2 55 34 PM

Validation reports

Screenshot 2024-05-03 at 2 57 41 PM

  • In Guides > Preparing validation reports the "Key concepts" section has been replaced with modular includes from the about/glossary/validation-reports folder
  • The associated embed files are structured in _filename.qmd format (e.g. _report-intro.qmd)
New validation reports Old validation reports
Screenshot 2024-05-03 at 2 56 51 PM Screenshot 2024-05-03 at 2 56 47 PM

Other weirdness

integrate_external_test_providers.ipynb notebook

For some reason the broken link in this notebook to implementing_custom_tests.ipynb has been overwritten even though I fixed it in another PR in the developer-framework repo even though I ran make get-source — likely my bad, I will open a new PR to fix this quirk.

Off-set anchor links

@validbeck validbeck added the internal Not to be externalized in the release notes label May 3, 2024
@validbeck validbeck self-assigned this May 3, 2024
@validbeck validbeck requested a review from nrichers May 3, 2024 22:02
@nrichers nrichers requested a review from noosheenv May 6, 2024 19:49
site/about/glossary/glossary.qmd Outdated Show resolved Hide resolved
Copy link
Collaborator

@nrichers nrichers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! This is a fantastic leap forward for our glossary. I really like how modular this is, to the point where you can assemble almost anything on a term-by-term basis. 🚀🚀🚀

There are a few comments to address but good to merge afterwards.

site/about/glossary/_developer-tools.qmd Outdated Show resolved Hide resolved
site/about/glossary/_ai.qmd Outdated Show resolved Hide resolved
site/about/glossary/_ai.qmd Outdated Show resolved Hide resolved
site/about/glossary/_ai.qmd Outdated Show resolved Hide resolved
site/about/glossary/_developer-tools.qmd Outdated Show resolved Hide resolved
site/about/glossary/_mrm.qmd Outdated Show resolved Hide resolved
site/about/glossary/_mrm.qmd Outdated Show resolved Hide resolved
site/about/glossary/_mrm.qmd Outdated Show resolved Hide resolved
site/about/glossary/_mrm.qmd Outdated Show resolved Hide resolved
site/about/glossary/_validmind.qmd Outdated Show resolved Hide resolved
validbeck and others added 4 commits May 6, 2024 16:12
Co-authored-by: Nik Richers <nik@validmind.ai>
Co-authored-by: Nik Richers <nik@validmind.ai>
Co-authored-by: Nik Richers <nik@validmind.ai>
Co-authored-by: Nik Richers <nik@validmind.ai>
site/about/glossary/key_concepts/_test-suite.qmd Outdated Show resolved Hide resolved
validbeck and others added 6 commits May 6, 2024 16:15
Co-authored-by: Nik Richers <nik@validmind.ai>
Co-authored-by: Nik Richers <nik@validmind.ai>
Co-authored-by: Nik Richers <nik@validmind.ai>
Co-authored-by: Nik Richers <nik@validmind.ai>
Co-authored-by: Nik Richers <nik@validmind.ai>
Co-authored-by: Nik Richers <nik@validmind.ai>
Copy link
Collaborator Author

@validbeck validbeck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Committed some suggested changes and asked some clarifying questions

site/about/glossary/_mrm.qmd Outdated Show resolved Hide resolved
site/about/glossary/key_concepts/_test-suite.qmd Outdated Show resolved Hide resolved
site/about/glossary/_developer-tools.qmd Outdated Show resolved Hide resolved
site/about/glossary/_mrm.qmd Outdated Show resolved Hide resolved
@nrichers
Copy link
Collaborator

nrichers commented May 7, 2024

Maybe also put this into a Shortcut story? Definitely an issue that should be resolved at some point.

FWIW, I checked the open Quarto issues for anything related to anchors, but nothing stood out: https://github.com/quarto-dev/quarto-cli/issues?q=is%3Aissue+is%3Aopen+anchor+.

@nrichers
Copy link
Collaborator

nrichers commented May 8, 2024

@validbeck I helped out a little bit with this PR while you were out, I hope that is OK.

Changes:

  • Merged main into your branch to fix merge conflicts
  • Changed single bullet points into paragraph text, addressing this comment.

@validbeck
Copy link
Collaborator Author

Thank you! I was going to need to make those changes anyway, so that saves me the work. :)

  • Merged main into your branch to fix merge conflicts

How do I do this? Can you show me briefly? I guess I can also Google for docs...

Should we take a look at instances of e.g. and i.e. in the docs when I change the variables as well?

@validbeck validbeck merged commit 92590b1 into main May 8, 2024
@nrichers
Copy link
Collaborator

nrichers commented May 8, 2024

  • Merged main into your branch to fix merge conflicts

How do I do this? Can you show me briefly? I guess I can also Google for docs...

Happy to demo but the basic workflow from your working branch is:

  1. git pull origin main
  2. Manually fix any merge conflicts that are NOT in the HTML output files
  3. quarto render to fix the HTML output file conflicts
  4. git add --all to add the fixed files for committing in the next step
  5. git merge --continue (git pull is a fetch & merge; the conflicts you see happen during the merge)
  6. Complete the merge (vim commands: Esc > : > wq)
  7. git push to update your branch on GitHub

The same basic process also applies to updating your working branch with the latest changes from main.

Should we take a look at instances of e.g. and i.e. in the docs when I change the variables as well?

The *.qmd files should be largely free of Latin abbreviations but there quite a few occurrences in content we pull out of the developer-framework repo. We should fix those at some point but it's probably more of a nice-to-have right now? Maybe just capture that in an editing story — we should look into using ChatGPT to cover 85% of our text editing, similar to what we can now do for the release notes.

@nrichers nrichers deleted the beck/sc-4074/create-modular-glossary branch May 8, 2024 16:43
@validbeck
Copy link
Collaborator Author

Manually fix any merge conflicts that are NOT in the HTML output files

I think I might need to see this process in action to understand it fully, but thank you for the detailed breakdown!

@validbeck
Copy link
Collaborator Author

Maybe also put this into a Shortcut story? Definitely an issue that should be resolved at some point.

Done: sc-4381

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Not to be externalized in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.