Out of curiosity: does the support for automatic JSX incur any startup or deployment penalty? I'd assumed Deno didn't have a "build step" per se, but maybe I'm mistaken.
https://github.com/denoland/fresh/blob/main/www/routes/docs/...
Using MDX is a little trickier as the .mdx file needs to be compiled to a javascript file which is then interpretted. When running Deno yourself this isn't hard as you can use a dynamic import, but if you're planning on using Deno Deploy you'll be out of luck as it doesn't support dynamic imports currently.
https://github.com/denoland/fresh/issues/640
Deno Deploy has an open issue asking for support if you want to give it a star. ;)
https://github.com/denoland/deploy_feedback/issues/1
As a workaround, you can always setup a watcher and preprocess MDX files before deploying to Deno Deploy, but that seems against the spirit of what Fresh is trying to accomplish by getting rid of preprocessors.
Let me know if you figure out a way to get MDX on Deno Deploy working without precompile as I'd like to use it myself!
Was Twind chosen to stay true to the "no build step" idea?
The only thing I'm missing to try it out is some sort of SASS support.