This page contains pointers and links to help you contribute to this project.

The Executable Books Team Compass is a source of truth for our team structure and policy. It also has a lot of information about how to contribute.

We expect all contributors to this project to Code of Conduct.

We do most of our work in GitHub repositories in the jupyter-book/ GitHub organization.

• For chat and real-time conversations: The MyST community Discord server.
• For discussions around work and development: Issues in the mystmd repositories.
• For general discussions and questions: the mystmd community forum.

The mystmd project covers a subset of the jupyter-book/ GitHub organization. It focuses on the Javascript-based MyST Markdown engine and ecosystem, as well as the markdown syntax that MyST uses.

Below is a list of relevant repositories and a brief description of each.

• mystmd: The MyST document engine and functionality not related to specific renderers.
• myst-theme: The web components and themes that are used for either the book or article themes for MyST.
• myst-spec: Questions about the markdown syntax for MyST and standardization efforts for MyST functionality.
• jupyterlab-myst: Questions about the JupyterLab extension for MyST.
• MyST Templates: Repositories that contain templates for rendering MyST documents into various outputs like LaTeX, JATS, Typst, and Docx.

Generally speaking, our contribution workflow looks something like this:

• Conduct free-form conversation and brainstorming in our forum. We have a community forum for general discussion that does not necessarily require a change to our code or documentation. If you have a specific enhancement or bug you would like to propose for resolution, see the next steps.
• Search open issues to see if your idea is already discussed. Use a GitHub search in the jupyter-book/ organization to see if you should add to an existing issue or create a new one. If you don't think an issue exists that covers your idea or bug, go ahead and open one.
• Discuss and propose changes in issues. Issues are a way for us to agree on a problem to solve, and align on a way to solve it. They should invite broad feedback and be as explicit as possible when making formal proposals.
• Make a pull request to implement an idea. We use Pull Requests to formally propose changes to our code or documentation. These generally point to an issue and ideally will close it.
• Iterate on the pull request and merge. Pull Requests should have discussion and feedback from at least one core team member, and ideally from many. Once the PR is ready to merge, a core team member may decide to do so. See our decision-making guide for formal details.

This describes the high-level process that is usually followed. In practice, we recommend attempting a contribution to get a feel for how it works in practice.

Our Team page lists all of the teams in the jupyter-book/ organization and their members. In addition, our Governance page describes the responsibilities and authority that team members have.

Our governance page describes our formal decision-making processes.

These sections help you get started with a development environment for mystmd and learn how to contribute to the codebase.

mystmd is built and developed using:

• TypeScript for static type checking
• ESLint for code linting
• Prettier for code formatting

The mystmd libraries and command line tools are written in TypeScript, and require NodeJS and npm for local development. The mystmd-py package, which is a thin Python wrapper around the mystmd bundle, can be installed by users using pip or conda. If you have already installed mystmd (e.g. via pip or conda), it is recommended that you uninstall it (or deactivate the relevant environment) before using the local development instructions below.

For local development, clone the repository and install the dependencies using npm. You can then build the libraries (npm run build) and then optionally link to your globally installed mystmd in node using the npm run link command.

git clone [email protected]:jupyter-book/mystmd.git
cd mystmd
npm install
npm run build
npm run link

These commands allow you to use the myst CLI in any directory as usual, and updates to the build are picked up when you rebuild. After making changes, you must rebuild the packages (via npm run build in the top-level directory), which is done efficiently depending on how deep your change is in the dependency tree. After the build is complete, you can reuse the myst client.

Tests are also a helpful development tool, which don't require full rebuilding. You can run the entire test suite using npm run test. If you are working in a particular package, change your working directory and run the tests there, to run in watch mode use npm run test:watch.

When contributing code, the continuous integration will run linting and formatting. You can run npm run lint and npm run lint:format locally to ensure they will pass. If you are using the VSCode editor, it can be setup to show you changes in real time and fix formatting issues on save (extensions: eslint and prettier).

We use changesets for tracking changes to packages and updating versions, please add a changeset using npm run changeset, which will ask you questions about the package and ask for a brief description of the change. Commit the changeset file to the repository as a part of your pull request.

Running in live-changes mode: depending on the package you are working in we have also setup live changes which can be faster than the npm run build; this can be run using npm run dev. If your changes aren't showing up, use npm run build as normal.

mystmd uses changesets to document changes to this monorepo, call npm run changeset and follow the prompts. Later, npm run version will be called and then npm run publish.

Our current versioning procedure is a little loose compared to strict semantic versioning; as mystmd continues to mature, this policy may need to update. For now, we try to abide by the following rules for version bumps:

• major: Backwards incompatible change to the underlying supported MyST data. These would be cases where a non-developer MyST user's project or site built with major version N would not work with major version N+1. Currently, we never intentionally make these changes.
• minor: Backwards incompatible change to the Javascript API, for example, changing the call signature or deleting an exported function. These can be a headache for developers consuming MyST libraries, but they do not break MyST content.
• patch: For now, everything else is a patch: bug fixes, new features, refactors. This means some patch releases have a huge, positive impact on users and other patch releases are basically invisible.

All packages for mystmd are included in this repository (a monorepo!). We use npm as a package manager. The mystmd package includes the following packages/apps:

Command Line Tools:

• mystmd this provides CLI functionality for myst start
• mystmd-py a python wrapper over mystmd, to ease install for the Python community. Not recommended for local development.

Core Packages:

• myst-cli this is the package that provides CLI functionality for mystmd, it does not export the CLI directly
• jtex a templating library (see docs)
• myst-frontmater definitions and validation for scientific authorship/affiliation frontmatter (see docs)
• myst-config Validation and reading of configuration files
• myst-templates types and validation for templates (LaTeX, web and word)

Markdown Parsing

• markdown-it-myst markdown-it plugin to handle tokenizing roles and directives.
• myst-directives core directives for MyST
• myst-roles core roles for MyST
• myst-parser converts markdown-it token stream to mdast

Readers

• tex-to-myst convert LaTeX to MyST AST
• jats-to-myst convert JATS xml to MyST AST

Transformers

• myst-transforms a number of transformations for use with myst AST to transform, e.g. links, citations, cross-references, admonitions

Export Tools

• myst-to-docx convert MyST documents to word docs!
• myst-to-jats convert MyST to JATS, for use in scientific archives
• myst-to-tex convert MyST to LaTeX, to be used in combination with jtex to create stand alone LaTeX documents
• myst-to-html convert MyST to HTML

Extensions:

• myst-ext-card: Card directives
• myst-ext-grid: Grid directives
• myst-ext-tabs: Tab directives
• myst-ext-reactive: Reactive directives

Utilities

• myst-common Some common utilities for working with ASTs
• myst-spec-ext Extensions to myst-spec used throughout this repository, before pushing upstream
• citation-js-utils utility functions to deal with citations
• myst-cli-utils some shared utils between jtex, and myst-cli
• simple-validators validation utilities, that print all sorts of nice warnings

Each package is 100% TypeScript and ESM only.