You forgot the enormous learning curve of understanding how browsers work and how to write proper code in Ladybug that doesn't waste the maintainers´ time.

Last time I tried, I couldn't find a website that worked with it. Where do you even begin contributing to such a large, complex, very much WIP project? The barrier to entry is daunting.

When it comes to larger projects, first:

- you don't need to understand the whole in order to help

the kind of bugs you can start with are like :

- this icon is a bit weird, it's off centre by 2px - how do I add 2 pixels to this icon? either by moving it or by changing the underlying image asset? if I'm moving it, what is the subroutine that paints it? if I'm changing the image asset itself, where is it stored? (is it in a packed store? or is it just a plain file, etc)

- when I click this button, trace the pathway - it's supposed to add to history and turn blue. is it doing that?

etc.

For large projects, start super small and work your way out from there.

>Last time I tried, I couldn't find a website that worked with it.

That was the case for me last time I tried it as well, which was a few months ago. Tried it again yesterday and I could load many pages. Could even render complex real life pages like YouTube.

I recommend anyone to build it themselves. It is a very simple and smooth experience.

Pick a site that almost works on it and then fix it to fully work?

You don't have to implement some big new feature. I found a layout rendering problem when I tested it on my own website and could quite easily go and fix it without having any prior experience with browser development.