Convert to MySTMD

[lundybernard]

Migrate from Hugo to MyST-MD

Fixes: #279

[netlify]

✅ Deploy Preview for learn-scientific-python-org ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	af02bd3
🔍 Latest deploy log	https://app.netlify.com/projects/learn-scientific-python-org/deploys/6a061dc96e091a0009cc8417
😎 Deploy Preview	https://deploy-preview-315--learn-scientific-python-org.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 99 Accessibility: 97 Best Practices: 100 SEO: 100 PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[lundybernard]

I've put together a plan for the migration, including REQUIREMENTS.md, and Architectural Decision Records (ADRs), which need review, and a detailed PLAN.md document.

Recommended Review order:

• Start with REQUIREMENTS.md; a high-level list of goals, and details about how the change will be managed. Any changes to this doc will be top priority.
• Review the ADRs in docs/decisions/0001-myst-migration/; they cover specific decisions that need to be made, and are the most important items to discuss.
• The README files just provide context and an index of the directories, and should be helpful.
• the PLAN.md doc contains a granular specifics, is likely to change as I work through the migration. It is helpful for the process, may be a valuable record of the completed work, but is probably not worth reviewing at this time.

---

Ai Tools Disclaimer:
These docs were generated using Claude Opus-4.7 for planning and review, Sonet-4.6 for edits, and GPT-5.5 for reviews.
I have read, reviewed, and updated the docs myself many times, and feel that they are ready for other humans to review and discuss.
Since scientific-python.org does not have an official Ai use policy, I'm using the SciPy project's policy as a guideline.

[henryiii]

From what I see, the plan looks fine. While I was excited about the Jekyll -> Hugo migration (fast, secure single binary, static easily themeable HTML), I'm not quite as excited about mystmd transition (Frankenstein of nodejs+Python, JS-powered pages). I get several source map loading errors when opening https://mystmd.org/guide. But I do really like it for course material, and some of our material basically is that.

I'd probably not worry about trying to replicate the theme at all at first (which I think matches the decisions made, like the deferred footer).

I'm curious if you've done the basic conversation table for the other subrepos? I'm curious to see what it says about the special stuff in cookie, like our tabs. I know exactly how to do that in Hugo (I maintain a Hugo theme ;) ), I'm curious to know how those would map to mystmd.

I'm very slightly tempted to do Jekyll -> Hugo with cookie, and then look at Hugo -> mystmd.

But yes, plan looks good. What do you feed into the next step, just the PLAN.md?