JS Bin VS mdBook

JS Bin is one of the useful JavaScript debugging tools designed for developers working with HTML, CSS, and JavaScript. It gives them the opportunity to test and debug their code snippets in a real-world setting. The fact that this tool is open-source is fantastic.

If I paste both in jsbin.com, the both show all content on 1 line.

A running example in https://jsbin.com/ might be easier to help with

JSBin : Front end playground, Output is not framed, so it allows you to share those snippets that will break inside an iframe.

> What if you want introduce some diagramming or Latex rendering in your blog ?

Then you are starting to step beyond what I was referring to as “a simple blog” (text, formatting, maybe some pictures or SVG).

Though there are options that don't require a CI/CD pipeline. Depending on what Latext you need MathJax may do the trick (just include the JS in your standard page header, and drop the Latex code straight in inline where needed as per their standard example: https://jsbin.com/?html,output. There are similar charting options like mermaid too. I don't know of inline charting options off the top of my head but I expect several exist.

Post your code on codesandbox.io or jsitor.com or jsbin.com or jsfiddle.net or whatever other site you prefer. Then we can look at it and see what is wrong. Otherwise, it's like showing us a picture of your cat and asking whether we think you might be allergic to it.

Important note: do not perform tests with WeakRefs in dev tools. Your objects won't be GCed in it due to DevTools specific behaviour. Instead, use jsbin, codesandbox, runkit or perform tests in Node.js. Localhost is okay when you open files using http:// protocol, as file:// also has specific behaviour.

https://jsbin.com/ (Type in the code; press go)

I'm responsible for a number of Java products. I try to provide high-quality Javadoc for all public library interfaces, library user's guides where appropriate, and development guides for applications. The latter two take the form of MDBook documents (https://rust-lang.github.io/mdBook/), with the document source living in the GitHub repo so that it's tied to the particular software release in a natural way.

My org has used mdBook: https://rust-lang.github.io/mdBook/ (That link is itself a rendered mdBook, so that'll give you an idea of the feature set.)

(While it's definitely a Rust "thing", if you just have a set of .md files, all you need is a "SUMMARY.md" (which contains the ToC) and a small config file; i.e., you don't have to have any Rust code to use it, and it works fine without. We document a large, mostly non-Rust codebase with it.)

If you want the lowest friction, open source, easily extensible Markdown to Web, Kindle, PDF, etc. tool, highly recommend mdBook: https://github.com/rust-lang/mdBook it’s written in Rust, but you don’t have to know any Rust to use it. And then wing is all CSS; for which there are many good (free) themes.

Interesting enough there seems to be an open PR for that: https://github.com/rust-lang/mdBook/pull/1918