-
-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: Better explanations of how things work #35
Comments
This comment was marked as outdated.
This comment was marked as outdated.
I'm in the same spot here! Migrating from Django to Litestar and while the Litestar docs are great at the moment, there isn't a lot on how to structure an application. This repo is helpful so far but I would find it more helpful if there was more explanation, so we can understand why things are being done the way they are. Articles like this one were very helpful to me learning Django in the first place. |
+1 here. Not necessarily Django migration, but an article explaining how things work and why certain choices were made would be very useful. Thanks! |
Absolutely! An article explaining the directory structure, why certain choices were made, and how to make changes would be amazing! Funding this issue with 100$ @JacobCoffee for some reason, the 100$ bounty I placed doesn't show up on https://polar.sh/litestar-org |
I can confirm we can see this in polar. Watch the issue for updates - thanks for your pledge! |
Hi, I'm looking for a cross of Diango and FastAPI (read "Django building experience but lean and with first class pydantic and openapi support). Litestar and this repo in particular look like a great start but as somebody spoiled by Dingo abstracting away a lot of the backend, I'm wondering whether there can be a simple guide for how to use this repo coming from Django without having to learn all about SQLAlchemy etc. Or maybe you'd recommend a different stack? I assume many people looking to migrate from django to litestar will aim to do so via this repo.
Thanks
Note
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh Litestar dashboard
The text was updated successfully, but these errors were encountered: