One of the main draws of markdown is that it’s readable and legible even in a text-only view, without being rendered to HTML or another display format. This seems like it’s specialized for a particular JS library, which means it’s less of a markdown dialect than a library-specific DSL that happens to have built on top of markdown. But if it’s library-specific, then there’s not much value in trying to be an open standard like markdown.
The ultimate goal of Nue is to build a significantly easier, yet more powerful alternative to Vercel, Gatsby, and Netlify.
I don’t know what any of these are, so I think I’m just not the target audience.
One of the main draws of markdown is that it’s readable and legible even in a text-only view
Yet it seems mostREADME.md files should be renamed RENDERME.md with all sorts of HTML, images that don’t add any value to the reading, & misuse of elements due to the severe limitations of elements Markdown maps too (such as blockquotes for anything not quoting any sources).
Author here. Nuemark indeed adds a small DSL on top of Markdown. It is meant to build rich web pages so it should be compared to how they are done with other mechanisms. One popular way today is to use Next.js together with Tailwind. Here’s what the code looks like for tailwind.com front page:
Nuemark aims to simplify the above by extracting all content from the logic, layout, and styling resulting to a more readable/easier development experience.
I’m at the “I know some of those words” stage instead since I host some stuff on Netlify. I am still missing the connection with frontend frameworks. Or perhaps it’s because frontend frameworks, cloud hosting and serverless are melting in a sort of reactive, batteries-included blob that redeploys your every keystroke.
That aside though, this seems like quite an interesting project although I imagine there’s going to be a long tail as far as tooling (syntax highlighting, file extension recognition, linting etc) that personally I’d be waiting for
Haha. Fair point. I changed it to “hard to break things up”. The main idea there is that you can break a page that has JavaScript imports and logic, but when there is only content the issues are less severe, like typos or styling issues. Thanks.
Is Nuemark formally specified yet? I’d like to see something like MyST’s https://mystmd.org/spec. If Nuemark is great, I’ll want to use it with other tools.
I don’t care about all the JS integration, but the syntax looks nice. It’s always annoying to hop off markdown to HTML just to add some aside. And then you have to keep everything in HTML now.
One of the main draws of markdown is that it’s readable and legible even in a text-only view, without being rendered to HTML or another display format. This seems like it’s specialized for a particular JS library, which means it’s less of a markdown dialect than a library-specific DSL that happens to have built on top of markdown. But if it’s library-specific, then there’s not much value in trying to be an open standard like markdown.
I don’t know what any of these are, so I think I’m just not the target audience.
Yet it seems most
README.mdfiles should be renamedRENDERME.mdwith all sorts of HTML, images that don’t add any value to the reading, & misuse of elements due to the severe limitations of elements Markdown maps too (such as blockquotes for anything not quoting any sources).Author here. Nuemark indeed adds a small DSL on top of Markdown. It is meant to build rich web pages so it should be compared to how they are done with other mechanisms. One popular way today is to use Next.js together with Tailwind. Here’s what the code looks like for tailwind.com front page:
https://github.com/tailwindlabs/tailwindcss.com/blob/master/src/pages/index.js
Nuemark aims to simplify the above by extracting all content from the logic, layout, and styling resulting to a more readable/easier development experience.
I’m at the “I know some of those words” stage instead since I host some stuff on Netlify. I am still missing the connection with frontend frameworks. Or perhaps it’s because frontend frameworks, cloud hosting and serverless are melting in a sort of reactive, batteries-included blob that redeploys your every keystroke.
bold claim 🤨
It’s a bit ironic considering that one of the documentation pages appears to have messed up a directive at the top: https://nuejs.org/docs/concepts/nuemark.html :)
That aside though, this seems like quite an interesting project although I imagine there’s going to be a long tail as far as tooling (syntax highlighting, file extension recognition, linting etc) that personally I’d be waiting for
Thank you! Now fixed. It looked bad indeed
Haha. Fair point. I changed it to “hard to break things up”. The main idea there is that you can break a page that has JavaScript imports and logic, but when there is only content the issues are less severe, like typos or styling issues. Thanks.
Is Nuemark formally specified yet? I’d like to see something like MyST’s https://mystmd.org/spec. If Nuemark is great, I’ll want to use it with other tools.
Isn’t this what reStructuredText is for? Markup with directives?
I don’t care about all the JS integration, but the syntax looks nice. It’s always annoying to hop off markdown to HTML just to add some aside. And then you have to keep everything in HTML now.
This is exactly the goal of Nuemark: offer a good set of primitives so you have fewer reasons to jump to HTML and JavaScript.