Migrate to myst engine (#183)

Author: choldgraf

.gitignore

@@ -1,2 +1,4 @@
 .venv
+.nox
+__pycache__/
 docs/_build

README.md

@@ -4,6 +4,17 @@ the Jupyter Executive Council.
 
 Please see the [official rendered version](https://executive-council-team-compass.readthedocs.io) of this repo.
 
+## Build the docs locally
+
+This documentation is built with [the MyST Document Engine](https://mystmd.org/guide).
+To preview it locally, install `mystmd` and start a live preview from the `docs/` folder:
+
+```bash
+pip install mystmd
+cd docs
+myst start
+```
+
 ## Code of Conduct
 As an official part of Project Jupyter, all communication across all
 repositories in this organization should adhere to the

build.sh

@@ -7,7 +7,7 @@ This page explains how grants and other funds flow through the LF structures tha
 
 Two LF entities can receive and hold Jupyter funds:
 
-- **[The Jupyter Foundation](https://jupyterfoundation.org/)** is a directed fund of [The Linux Foundation 501(c)(6)](https://projects.propublica.org/nonprofits/organizations/460503801). This is the main pool of Jupyter money and is governed by the Jupyter Foundation's governing board.
+- **[The Jupyter Foundation](https://jupyterfoundation.org/)** is a directed fund of [The Linux Foundation 501(c)(6)](https://projects.propublica.org/nonprofits/organizations/460503801). This is the main pool of Jupyter money and is governed by the [Jupyter Foundation's governing board](xref:foundation).
 - **[LF Charities Inc](https://lf-charities.org/)** hosts Project Jupyter as an open-source project and is a [501(c)(3) nonprofit](https://projects.propublica.org/nonprofits/organizations/841730246). Project Jupyter is governed by the Jupyter Executive Council, a community-elected group that also sits on the Jupyter Foundation governing board.[^509a3]
 
 [^509a3]: LF Charities is a 509(a)(3) "supporting organization" for the LF 501(c)(6). That legal relationship is what lets Project Jupyter receive funds in LF Charities and later move them into the Jupyter Foundation to save on G&A overhead.
@@ -39,7 +39,7 @@ There is a tradeoff between moving money into the Jupyter Foundation for the low
 When LF Charities transfers money into the Jupyter Foundation, it goes in without conditions.
 This is deliberate: attaching conditions would make the money "restricted funding" under IRS rules and trigger extra reporting requirements. The cost of avoiding that is that the money becomes part of the Jupyter Foundation's single pot rather than a separately tracked bucket.
 
-The Jupyter Foundation's governing board then allocates that money. It can steer funds toward the priorities the Executive Council has laid out, so the EC's intent can still be honored in practice. What it cannot do is make an explicit written commitment tied to the transfer, since that would be the kind of condition that creates restricted funding.
+The Jupyter Foundation's governing board then [allocates that money](xref:foundation#budget-allocation). It can steer funds toward the priorities the Executive Council has laid out, so the EC's intent can still be honored in practice. What it cannot do is make an explicit written commitment tied to the transfer, since that would be the kind of condition that creates restricted funding.
 
 If keeping funds under the Executive Council's governance matters more than the lower overhead, the money can instead stay in LF Charities. However, until the yearly income there for Jupyter passes 1 million USD (regardless of any funds that are in the 501(c)(6)), the overhead rate will be the higher 9% rate.
 

docs/Makefile

@@ -23,15 +23,3 @@ EC members allocate time during our weekly scheduled meetings to review new issu
 **Other Channels:**
 * [Issues on the main Governance Repository](https://github.com/jupyter/governance): offer a space for broader discussion about Governance with the entire community, and are better suited for conversations where input from bodies like the [Software Steering Council](https://jupyter.org/governance/software_steering_council.html), project teams and individuals are sought. **If you need to flag an issue specifically for input by the EC, please tag the team with `@executive-council`**.  The EC will move issues between this general Governance repo and the EC team compass when appropriate.
 * [The Governance category on Discourse](https://discourse.jupyter.org/c/meta/governance/23): is _not formally monitored by the EC_, due to limited bandwidth. It is OK for the community to discuss governance topics there and EC members may occasionally post, but we can not commit to actively monitoring it.
-
-## Table of Contents
-
-```{toctree}
-:titlesonly:
-operations
-accounts
-finances
-meeting_notes/index
-office_hours/index
-reports/communitybuilding/readme
-```

docs/_static/custom.css

@@ -1,11 +1,3 @@
 # Meeting Notes
 
 The Jupyter Executive Council meets privately each week. A summary of meeting notes is posted below. We follow [this process in updating minutes](#process-minutes).
-
-```{toctree}
-:titlesonly:
-2023
-2024
-2025
-2026
-```