I've been dabbling with axum as of late and I agree the docs are relatively good.
I think 2 things that are missing.
- What you mention, "use this for that" sorts of guides. The ecosystem is pretty good, but when you pull down axum you aren't getting something like Java's Spring framework. Instead, you are getting something more like Javascript's expressjs. That makes it a bit tricky to go through and track down which tower plugins you should be using.
- "How to structure your app" sorts of guides. Axum doesn't really force any sort of layout of design, which is good, but it's also not great in that it leaves that actual design up to the beginners imagination. Something like "Here's an example of a todo app with multiple users" would do wonders in showing a recommended layout. Covering how you should do DI, input validation, error handling, session management, module layout, testing. All that sort of stuff would be really useful to have/see.
They actually have quite a few examples in the axum repo and linked from their docs. Something a bit more use-friendly and approachable like Bevy's website would be beneficial, though.
There are examples, but they are fairly focused and not really full applications.
For example, you can find an example of error handling and an example of login flow. You won't see an example of the two put together.
Also importantly, the examples for simplicity are likely to lump everything into `main.rs`. A great way to show off specifically how to do something. Not a great way to show off "apps should look like this".
I think 2 things that are missing.
- What you mention, "use this for that" sorts of guides. The ecosystem is pretty good, but when you pull down axum you aren't getting something like Java's Spring framework. Instead, you are getting something more like Javascript's expressjs. That makes it a bit tricky to go through and track down which tower plugins you should be using.
- "How to structure your app" sorts of guides. Axum doesn't really force any sort of layout of design, which is good, but it's also not great in that it leaves that actual design up to the beginners imagination. Something like "Here's an example of a todo app with multiple users" would do wonders in showing a recommended layout. Covering how you should do DI, input validation, error handling, session management, module layout, testing. All that sort of stuff would be really useful to have/see.