Our great sponsors
-
For a static document markup language, Djot does a rather good job: https://github.com/jgm/djot
It's similar yet much fuller-featured than commonmark, with support for definition lists, footnotes, tables, several new kinds of inline formatting (insert, delete, highlight, superscript, subscript), math, smart punctuation, attributes that can be applied to any element, and generic containers for block-level, inline-level, and raw content. In addition, it resolves ambiguities in the commonmark spec and parses in linear time.
Further discussion lower in this thread: https://news.ycombinator.com/item?id=33553293
Some examples, showing how Djot would be rendered into HTML: https://htmlpreview.github.io/?https://github.com/jgm/djot/b...
-
CommonMark seems like the obvious choice: https://commonmark.org/
It isn't as supported as I'd like, but it does exist and I've encountered it "in the wild" a few times, so it's not just some guy typing away on a website either.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Yes, the article is correct, there is a market for Markdown sites and related products.
Our Zato website is in Markdown: https://zato.io
We have a purpose-built static site generator, which makes sense in our case because:
* The resulting site is very fast, seeing as there is no need for runtime generation of any assets / HTML / any kind of resources
* It is easier for developers to work on documentation because they already know Markdown
* It is easy to statically apply filters such as spell checkers for multiple languages during the build
* Various optimizations can be applied, e.g. incremental builds or on-demand builds
The drawbacks are:
* Non-technical translators may have a difficult time working with anything but either their own specialized tools or MS Word and they consider Markdown to be "advanced"
* Sometimes you work with writers who are not technical at all and who will not understand what a build system is even if they are open to the idea of learning Markdown itself
Thus, there is a market for a lightweight CMS that would enable non-technical people to author Markdown in their browsers, without a need for any command line usage.
-
Website is broken, but I infer from the comments that this would fit the bill:
https://github.com/DannyBen/madness/
My company uses it internally for a load of things. I love writing in MD and pushing to gerrit and when it is submitted the change is live.
-
This convo reminds me of MDX -- https://mdxjs.com/ -- allows you to mix JSX with markdown, popular for making documentation pages for design systems.
A lot of the limitations of MD mentioned here are alleviated by allowing arbitrary JSX, which of course is optional for users who want something more basic.
-
strapdown-zeta
Discontinued Instant and elegant Markdown documents in the browser, Git powered markdown wiki server, mathjax and theme support, and many more features!
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
I like Markdown and use it at work, but I think Asciidoc is a better markup language because it is more consistent and has support for more things than Markdown does (e.g., better table support, callouts, tips, etc.).
I currently use 11ty with the Asciidoc plugin for building websites. This setup is nice because I only have to fiddle with HTML and CSS during the design phase. Once that's done, nearly all my website maintenance is done in Asciidoc. Easy!
I don't think I'd want to directly write an entire website in either Markdown or Asciidoc. I think, eventually, doing so would result in these markup languages becoming as cluttered and weird as the HTML/DOM/JavaScript/CSS mess is now.
I think a better step to improving HTML and CSS would be to have the browsers support Slim (https://github.com/deepin-community/ruby-slim) and Sass out of the box instead. That would make my design phase less wordy and redundant while keeping my Asciidoc experience nice and tidy.
-
I built an ultralight CMS with this philosophy in mind : https://github.com/arnaudsm/raito
Just drop index.html on a static server, and it's live.
-
Disclaimer: I'm biased as I created Scroll, but I can say pretty objectively that at this point it's far better than Markdown and the gap is only going to widen.
Try it out! https://scroll.pub/
-
-
I've create a Hugo blog Template used to create a Hugo blog quickly: