Just a complement to the main thread, I’d also like to mention another class of Jupyter using Github users, and that’s folk who use Github primarily for sharing outputs either as publishers or readers/consumers; for that class of user, good previewing of notebooks and the ability to easily publish via Github Pages is a key consideration.
I note that Github Pages provides first class support Jekyll and wonder if an official Jupyter Book publishing via Github Action would be appropriate.
Seeing how users make use of MyST eg as part of a publishing strategy may further inform MyST development and also reveal insights about end-user readers consume pages output. It might also throw up examples of folk who are not (yet) Github repo users but who do want to be able to comment on published pages. Using services such as Hypothesis to annotate notebooks (related discussion) is one way, but another way might be to encourage folk to comment / question as part of repo comments. If that is appropriate, what would the on-ramp to that be? If it’s not appropriate, is there another level of commenting that Github support. (I also note for example that Github is adding Discussions as well as Issues. Could there similarly be a split between code comments and Pages comments?)