up-for-grabs.net VS JS Bin

Up-for-Grabs projects: Find issues specifically marked for beginner contributions.

Up For Grabs maintains a “list of open source projects which have curated tasks specifically for new contributors.” (Source: Up For Grabs)

If you're unsure where to begin, websites like Up For Grabs can be valuable resources. They curate lists of open source projects that actively seek contributions, making it easier for you to find projects that are suitable for your skills and interests. These platforms provide a starting point for your research and help you navigate the vast space of open source projects.

Up For Grabs - Shows you repositories that need your attention , it's quite amazing because it's mostly beginner rated issues that are quite easy to solve

the sidebar links http://up-for-grabs.net/

Up For Grabs - a website that lists beginner-friendly open-source projects

Up For Grabs

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)