But for general structure, using your end-user's user experience path (from start to end) as a guide and avoiding buzzwords as much as you can usually help. Think of Stripe's documentation, you want something as easily digestible as that.
The sign-up requirement is a big onboarding hiccup.
Like yo, I don't even know what it really does yet, why are you asking me to create an account? Do you really expect your users to capture your value prop based on just screenshots alone?
I'd also suggest a top-down approach where you start with a flexible end goal you'd want to achieve (e.g. be a full-stack dev), in which case you can start by babystepping a hands-on approach (e.g. learning javascript, learning client-side and server-side of things). Complimentary fundamental course outlines can also help, e.g. Comptia A+ gives you hardware fundamentals, Comptia Network+ gives you networking fundamentals, CloudAcademy can get you started on working with cloud providers like Azure/GCP/AWS, and so on and so forth.
It's easy to get lost in the theoretical side of things, being able to test them out in action as soon as you can could give you quite an ideal balance.
Totes this. I got no degrees too fam but the way I approached it was to do side gigs in making websites for small businesses while making small github contributions.
Higher-paying gigs want some bit of track record and those small websites and github stuff are the lowest hanging fruits for me imo.
If the server got an issue with your request it can return 400 (Bad Request), which means that the server has received it successfully before acknowledging it as a bad one.
Even then, if the server returns 400 (Bad Request) the server can still attach a response body to that, in plain text/plain, application/octet-stream or even application/json, which could contain elaborate information.
Yo if you can't solve a problem for now, then temporarily focus on other things. Even Einstein (or whoever that person be) once said that you can't solve problems in the same headspace you've came up with them.