utilitarianism.net VS MyST-Parser

Check out the pinned post : ) Understanding [utilitarianism]((https://www.utilitarianism.net/) is a prerequisite for understanding negative utilitarianism, else if you're already familiar, proceed to the Negative Utilitarianism FAQ Those two are the most important. The rest can be skipped in the meantime. In the additional resources, I also added some articles that represent recurring topics in this subreddit.

The linked video briefly introduces utilitarianism.net, an open-access textbook on utilitarianism, endorsed by leading ethicists, that offers clear and accessible explanations of the key concepts in utilitarian ethics, as well as surveying the major arguments for and against the view. Supplemental resources include study guides and guest essays by experts in the field. We hope the site will prove a useful resource to anyone interested in learning more about the topic!

I've been loving Hugo. I built https://utilitarianism.net/ with it https://github.com/whyboris/utilitarianism.net

For my personal and dev sites I used to use Gatsby, but migrated to Hugo just this month: https://github.com/whyboris/homepage & https://github.com/whyboris/homepage-dev

I'm pleased with how little boilerplate Hugo actually needs. My personal websites have so few files to maintain / worry over :)

Sphinx along with MyST-parser to write documentation in markdown. I recently discovered portray which seems like a nice alternative as it supports markdown by default for both generic documentation and docstring in modules, class, methods and functions.

https://github.com/executablebooks/myst-parser :

> MyST is a rich and extensible flavor of Markdown meant for technical documentation and publishing.

> MyST is a flavor of markdown that is designed for simplicity, flexibility, and extensibility. This repository serves as the reference implementation of MyST Markdown, as well as a collection of tools to support working with MyST in Python and Sphinx. It contains an extended CommonMark-compliant parser using markdown-it-py, as well as a Sphinx extension that allows you to write MyST Markdown in Sphinx.

https://markdown-it-py.readthedocs.io/en/latest/ :

> *Follows the CommonMark spec for baseline parsing;

This project is just the first step towards making Spyder an educational tool. In the future, we hope that we can develop the infrastructure necessary to support in-IDE tutorials, by improving the tools like Jupyter Book, sphinx-thebe, MyST-Parser which will provide better integration to write educational tutorials.