Similar to laravel it’s important for django to offer developers a beautiful full-stack experience, including powerful approaches for building your application’s frontend. Its very teduous and cumbersome to add tailwindcss or other css framework, its need to be part django templating engine. Meaning we need to be able to build beautiful component driven UIs just with django as well. If this not happen django to suffer from adoption.
Welcome @NedyalkoKr !
Have you looked at the Django-Tailwind project?
(I don’t know about tailwind, but I don’t find it tedious at all to use Crispy + Bootstrap. Can you be more specific about what the problems are you are encountering?)
Can you clarify exactly what you mean by this?
Part of the beauty of Django is that all the components involved in the front-end production (template engines, template language, template files) can be replaced.
And what you should also keep in mind here is that Django is a completely community-driven project. There is no “Django company” doing the development. Features get added as community-members develop them.
For something completely new like this, it’s generally recommended to be developed as a third-party package first, to be able to get community input and a wider adoption before (possibly) being added to core.
If you’ve got an idea for an enhanced template engine that simplifies the integration of tailwind, I’d suggest you build it as a third-party package.
I disagree. I think you’re over-stating the case. Django has been around for about 20 years. I’ve been using Django regularly for more than 12, and have seen these sorts of predictions since the beginning. I find it just as inaccurate now as I did then.
Django fits into a lot of use-cases where the degree of integration you seem to desire simply isn’t necessary to be done in Django core. (DRF is probably the prime example of that, where Django serves as the backend-only interface to a front end created in React, Vue, Angular, etc.)
- Can you clarify exactly what you mean by this?
I am talking for somethink like this
Blade
- Have you looked at the Django-Tailwind project?
yes i know about this package but i have to run npm separately as dedicated process and there is a steep learning curve i need simple easy to plop UI modules with built in modern styling supported by the template langauge. I dont want to write any css or integrate tailwind or bootstrap, or use form widget tweaks to add the styles to the elements. I want consitent easy to build UI.
I also think is good for django to comes bundle with payment integration(s) and some sort of CMS.
I love django.
I’m a bit harsher than Ken.
You “dont want to write any css or integrate tailwind or bootstrap”? Tough! You’re making a website. You either need to know how to write HTML and – at a minimum – use a CSS framework or else collaborate with someone who does.
If I was teaching someone how to make websites with Django I’d start with how to write HTML and CSS. It’s the web. You’re making a website.
Then go ahead and build it! If you’re so inclined, you could also contribute it back to the community like so many other third-party package authors do.
Nope, not at all.
Payment integration is a minority function, and there are at least two excellent Django-based CMSs available.
Not everything needs to be in core. Not everything deserves to be in core.
One of Django’s strengths is the third-party package ecosystem - it serves a vital function in allowing the pace of development of those packages to proceed without being tied to Django’s release schedule.
The general rule-of-thumb that I’ve heard expressed is that Django core targets the “80% case”. (That’s not an “official standard”, or even a stated policy or objective - it just seems to be an informal guideline I’ve seen mentioned when talking about what should or shouldn’t be in core.)