Tutorial starting soon by the Turing way!

I would love to brainstorm with you a bit. We are running a scientific content standards workshop at the end of next week. Would you by chance have a small amount of time early next week to chat?

This is a bit of a different expectation though, we use the MyST renderer to get the content from latex, and then create downstream things from there (html, pdf, etc.). So for hard-core latex users, they are not able to style etc. from latex.

Similar to a journal, which often translates it anyways.

We are running all of our journals through it at @curvenote.com.

Can see:

proceedings.scipy.org/2025

Which a few people used latex for. Does all the basics well!

It is full latex understanding. Some big limitations, and the goal is to do the basics for transition purposes, not enable every package.

Our goals are web-native rendering and features.

Blog here:
curvenote.com/blog/how-to-...

I still haven't got my head around the integration with at-proto. We are doing some more wysiwyg editor work on @curvenote.com early next year and I would love to chat with someone with a vision of what this might look like from Curvenote's perspective... !?

@mystmd.org and @curvenote.com supports both latex and markdown submissions!

Thanks @renderg.host — means a lot. 🚀

Very, very, excited by this next part of our journey. And trying to keep the focus... 🔎

This is great - I was searching too narrowly in bibtex land. Thank you!

Thanks. :)

Solution can be applied to those marks for sure. Generally both the shortcuts are the same across apps though, and users know them, so it is less necessary IMO.

🚀🚀