Not only are screenshots often missing, but I’m also surprised by how many projects fail to describe the purpose and goals of their project in short, simple sentences. Many mistakenly assume that only users and developers visit the website or repository, not decision-makers. More ELI5 ("Explain Like I'm 5") can never hurt.

Writing good documentation is extremely hard. Even 10x engeneers can be basically illiterate.

> Even 10x engeneers can be basically illiterate.

I see what you did there

There's certainly a persistent issue of typos: (34 here that we found: https://triplechecker.com/s/689196/electrobun.dev).

Screenshots are harder to produce, maintain and publish.

I also suspect many technical authors are less “visual” so to speak, putting less emphasis on visual presentation.

Not the best thing for a desktop application framework maybe.

> Screenshots are harder to produce, maintain and publish

What, really? What am I missing? If you tell me video, yes, but a screenshot...

I don't think it's that hard, but it's easier for screenshots to drift and become out of date compared to just written text documentation.

You’re just trying to give us the gist of things with images. It’s basically selling your thing to me as something I would want to try out. Usually if I connect with something I see in first few moments then my likelihood of trying the thing out is higher.

We don’t need it to be updated on every commit. Or illustrated docs but some idea of what I’m getting myself into is nice to have.

It is literally a few minutes of effort

If you cant do such basic thing, which would significantly improve an ability to understand your product, then wtf

i mean in this case it would be a window with any web app in it… not sure that would be particularly helpful.