CodeTriage VS JS Bin

3. Open Source Contribution

I wrote a book with a chapter on how to write docs for other people’s code https://howtoopensource.dev

I also wrote an open source tool for writing and testing tutorials https://github.com/zombocom/rundoc and another that will email you undocumented methods of open source code so you can practice writing documentation https://www.codetriage.com/.

CodeTriage helps you contribute to open source by “picking a handful of open issues and delivering them directly to your inbox”. (Source: CodeTriage)

Here are open source projects listed https://www.codetriage.com/ You can filter for "C".

The biggest untaped potential (IMHO) is not one company funding 1 full time maintainer, but EVERY company allowing and encouraging EVERY developer to help and work with open source. This was the basis of my web app https://www.codetriage.com/. I have a chapter on it in my book How to Open Source (https://howtoopensource.dev/), and I talked to Yehuda about it for about an hour after my last talk at Philly ETE.

You can also use websites like up-for-grabs, goodfirstissue, or CodeTriage to find projects with open issues. Find one that looks easy or interesting to you and comment on it, asking if you can take a shot at it.

I recommend these resources to help you contribute https://www.codetriage.com/ (free) and https://howtoopensource.dev/ (paid). DM if you can’t afford a copy.

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)