Sorry if that sounded a bit harsh. As I do everything for free in my spare time, I am really trying to use that time efficient. That said, I appreciate very much that you are trying to improve and ask for feedback.

Basically I think it would help to write your documentation from your users perspective (developers that want to publish an app. And app developers are not necessarily nostr experts).

Instead of cramming everything into one page, splitting it on a per platform basis and makeing a clear step by step instruction might help.

Furthermore a developer does not only want to publish an app, he also wants to update it. Not a single word about updating an app is found in the documentation.

Then there is things like blossom servers... do I need them? Does it improve anything if I add some? If yes, is there guidance on how to find a good one?

Or what happens if I don't sign the release? Can I override an unsigned release? Can someone else override my unsigned release?

These are just some examples. In general instead of just writing what can be done, writing why something should or shouldn't be done would be a great help in my opinion.

I know writing docs is annoying, but really thinking it through and spending days! on it instead of a few minutes makes a whole lot of a difference.