[1] https://github.com/mickael-kerjean/filestash
[2] https://www.mysqltutorial.org/mysql-sample-database.aspx
Great for small stuff, but far too often one end up using it for too much. Extending it with more widgets, custom logic, fine grained access. Quick in the beginning, very hard to maintain in the end compared to a custom made view.
In scope operation and extension: - Incredibly smooth and effortless
Slightly out of scope: - F U, buddy.
It’s amazing for so much stuff that it’s honestly a superpower for a tech or tech leveraged company, and great for prototyping internal process automation.
The trick is knowing when to throw in the towel and go purpose built. I’ve definitely missed that boat at least once in my career.
It's definitely in my top 5 most valuable skills, and seems like an open secret in the industry.
Use the admin more where it's most useful. Use it less where it's not. You don't have to go cold turkey.
A Django-specific skillset I found very important is to know where that limit/line of the admin sits - you can push it very far, but there's absolutely a point where it becomes unmaintainable and more costly than building it yourself. The line itself can be a bit of a moving target depending on the project though.
The Django admin is simultaneously one of the greatest tools of the past two decades while also being a massive footgun if you're not careful.
I'd like to see Django gradually redesigning parts of the Admin to allow for more modular extensibility in future versions.
But it's not a substitute for being comfortable working with forms, templates, urls, requests and building custom views. Time spent learning the django-admin DSL would be better spent here, or learning the CBV DSL...
I'm kind of at a spot where I want to replace all admin with custom but this comes up against an important rule. Dont fix what's not broken.
To all designers reading this: We are not printing those screens to frame them. We're using admin tools to do real work and we want to see lots of information there to be fast. Maybe we created those models ourselves. We know what to look for. I'm sure that Django admin could be made to look better and some UX could be improved. It's in part theming and in part redesigning the control flow. Taking on the latter would be really interesting.
Edit: actually a problem with the home page of Django admin is that it doesn't show enough information. A full screen browser window displays a column of models and a lot of useless white space. A multi columnar layout would speedup navigation by displaying more models in one screen. And a search filter.
I can see that some people would prefer this aesthetic, even though i'd agree that having an admin panel with low information density is kinda pointless
username: preview password: preview
Just like Calibre for book management. Looks super old, but does everything so well.
I would take functional over pretty any time of the day.
That said, great work by OP.
Other than that, it's a really cool project and could be pretty useful for projects you want to churn out where the client is expecting heavy admin usage
[0] https://docs.wagtail.org/en/v2.8.1/topics/streamfield.html
But I don't think most people will use this instead of the default because the admin is only used by the internal development team anyway.
Django makes it so easy to add CRUD to models that using the admin doesn't make much sense in most cases.
Djolie.
And there's nothing I can do to keep
From crying when he calls your name
Jolene
