gitbook VS JS Bin

GitBook is a well-known online platform for developing, sharing, and publishing technical documentation. Although it’s not open source, it offers free and paid plans, with the free plan having limited features and functionalities. The paid plans unlock more features, such as custom domains, team collaboration, and advanced analytics.

GitBook — Platform for capturing and documenting technical knowledge — from product docs to internal knowledge bases and APIs. Free plan for individual developers.

Visit GitBook and sign up for an account.

A buddy of mine started looking at https://www.gitbook.com/

GitBook hasn't been open source since October 2018 (https://github.com/GitbookIO/gitbook) and software is usually judged by its most recent version. GitBook in its current form is a proprietary web service.

VSCodium does exclude the proprietary features of Visual Studio Code, but I don't see how that should disqualify VSCodium from being open source. In fact, I use VSCodium frequently and I am satisfied with its feature set. VSCodium is also maintained by someone who is not employed by Microsoft, so I don't think it's fair to say that it is intentionally designed to be inferior to Visual Studio Code.

GitBook is a collaborative documentation tool that allows anyone to document anything—such as products and APIs—and share knowledge through a user-friendly online platform.

Contributors and collaborators will do PR through code programming or using the design block builder gitbook.com

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)