This is the home for the user-facing documentation and related infrastructure for ValidMind. If you want to make updates to our external docs site, you're in the right place!
We believe in the power of collaboration and welcome contributions from the community. If you've noticed an issue or have ideas for improvement, please create a pull request or submit an issue. A member of ValidMind's documentation team will review your suggestions and support you in contributing to the docs.
-
Follow the Quickstart for a 15-minute introduction to the ValidMind Library and ValidMind Platform.
-
Read the ValidMind Library docs for more information about ValidMind's open source tests and Jupyter notebooks.
-
Join the Community Slack to ask questions, get support, and connect with Model Risk Management (MRM) practioners.
We use Quarto to develop our docs site, an open-source docs framework based on Pandoc that supports multiple input formats such as Quarto Markdown, Jupyter notebooks, and Markdown.
You need:
- Quarto CLI
- The Quarto extension for your IDE, such as VS Code
- For Windows operating systems, install the
make
command via Cygwin
First, read through and familiarize yourself with our ValidMind style guide.
- Our core user guides are sourced in Quarto Markdown under
site/guide
. - If you create new documentation, make sure to add it to the
_quarto.yml
file.
If you are creating a pull request, test your changes by rendering or previewing the site. Note that if this is your first time contributing, you will be asked to sign a contributor license agreement (CLA).
cd site
quarto preview
To render the site:
cd site
quarto render
The rendered static HTML output lives in:
site
└── _site ...
└── *.html, *.css, *.png, *.js ...
Core files you manipulate live under site
in these key directories that more or less correlate to the sections of the docs site reachable via the top navigation bar:
about
developer
faq
get-started
guide
support
These directories may have sub-directories depending on their size and grouped sub-topics contained within.
releases
— Correlates to the "Releases" section under About.training
— Correlates to the "Training" section under Get Started.
_site
— This is where static files rendered byquarto render
get placed.assets
— This is where general shared assets live (stylesheets, promotional images, all videos, etc.).internal
— For internal testing only.notebooks
— This is where notebooks retrieved from thevalidmind-library
repo live.tests
— This is where test descriptions generated from the Python source in thevalidmind-library
repo live.
templates
— You can find generic structural templates in this folder here to help you build your guides.testing
— When tests are complete, they get moved here fromsite/internal
.
Files for the docs site are created using Quarto Markdown (.qmd
). These, along with any Jupyter Notebooks pulled in from validmind-library
, get rendered into HTML files.
When constructing links, refer to the .qmd
file as Quarto will properly render these into .html
links on your behalf and check to see if the destinations are able to be resolved:
Correct | Incorrect |
---|---|
[Get started with JupyterHub](get-started/developer/try-with-jupyterhub.qmd) |
[Get started with JupyterHub](get-started/developer/try-with-jupyterhub.html) |
When constructing filepaths, including while using Quarto's Includes (single-sourcing feature), you'll also want start with the root directory whenever possible as this minimizes usage of unclear relative paths:
Correct | Incorrect |
---|---|
[Register models in the inventory](/guide/model-inventory/register-models-in-inventory.qmd) |
[Register models in the inventory](../../register-models-in-inventory.qmd) |
Use the installed Tachyons Extension For Quarto to build column layouts so that they are properly mobile responsive.
Refer to the tachyons-flexbox.qmd
template for an example.
If there are additional files that Quarto does not copy over automatically, place them into /assets
. These files might include:
- Videos
- Stylesheets
- Font files
Notebooks (.ipynb
files) are NOT edited via this documentation
repo, as any changes will be overridden.
Changes need to be made in the root repository validmind-library
and pulled into this one with:
make get-source
After you pull in the changes, commit them to this repo as part of the release notes process.