31–40 of 49 posts
Django has a CMS called Wagtail, which has some really nice features including custom content blocks which allow you to easily create unique looking pages. Wagtail has over 15,000 stars on GitHub, is heavily supported and was created in 2014. It has since been adopted by organizations such as NASA, Google, and the National Health Service. Below is a comparison between Wagtail and Wordpress. https://wagtail.org/wagtai…
[flagged]
The core is fine but the attraction of WP is not so much the core but the huge number plugins and many plugins are not fine (but they dont say so on the label).
You cannot go wrong with Wagtail, but its learning curve is steeper. It doesnt come much out of the box.
WordPress is incredibly bloated and has a terrible security history, mainly due to insecure plugins but not only. I can't imagine ever choosing it over Django with Wagtail. It's a little bit more work to implement and maybe maintain, but the payoffs are well worth the investment.
Django has a CMS called Wagtail, which has some really nice features including custom content blocks which allow you to easily create unique looking pages. Wagtail has over 15,000 stars on GitHub, is heavily supported and was created in 2014. It has since been adopted by organizations such as NASA, Google, and the National Health Service. Below is a comparison between Wagtail and Wordpress. https://wagtail.org/wagtai…
[flagged]
https://docs.djangoproject.com/en/4.2/topics/security/
Not to mention security through obscurity, Wagtail is a lot less common than Wordpress. Therefore, not as many attack vectors exist for Wagtail as they do for Django / Wagtail, especially if you keep on top of the security patches.
https://www.djangoproject.com/weblog/2023/sep/04/security-re...
Earlier quoted context omitted.
Worth noting that it also has Django-CMS although having used it, I wouldn’t advise adopting it as a lot of QoL things are not really well developed. Doing a migration into it by creating pages in a programmatic way for e.g. was not straightforward.
I have used both Django-CMS and Wagtail. Wagtail is much more user-friendly and extensible. You can create Wikis, Blogs and regular content pages with models and maintain it all through a friendly CMS interface that rivals Wordpress.
I've tried to ditch laravel so many times, I really like sveltekit and the idea of plugging it into Postgrest or firebase or just use prisma, but I always end up back at laravel.
Wagtail almost had me because Django has a nice migration system but I don't like how it creates special tables for polymorphism and special sauce like for content types etc, in laravel I always know what the data schema is and there's no gotchas or unexpected things.
WordPress is incredibly bloated and has a terrible security history, mainly due to insecure plugins but not only. I can't imagine ever choosing it over Django with Wagtail. It's a little bit more work to implement and maybe maintain, but the payoffs are well worth the investment.
You can use the one hosted in wordpress and change the domain, so you don't have to worry about hackers or anything. This one is a plug a play, so unless you want to do a custom template/plugin you don't need to learn to code.
* Django is like a wordpress but less popular and less SEO friendly (or less popular for them).
* Flask will require you to learn a lot of html, python, etc.. it will consume you a lot of time to get to the same point to the other 2. Flask can get better results than the previous two but for your use case I don't think it really matters.
WordPress is incredibly bloated and has a terrible security history, mainly due to insecure plugins but not only. I can't imagine ever choosing it over Django with Wagtail. It's a little bit more work to implement and maybe maintain, but the payoffs are well worth the investment.
WordPress is a lot better now that you can set the plugins to automatically update.
WordPress is incredibly bloated and has a terrible security history, mainly due to insecure plugins but not only. I can't imagine ever choosing it over Django with Wagtail. It's a little bit more work to implement and maybe maintain, but the payoffs are well worth the investment.
WordPress core does not have a terrible security history. If you install a plug-in made by Billy from his mom’s basement, that’s on you.
Yes, it does[0]. Crappy plugins just made it much worse.
[0]https://www.cvedetails.com/product/4096/Wordpress-Wordpress....
> build a website for them plus a bit of marketing stuff, and maybe a remote desktop and a platform for invoicing for their personnel.
This is a shoe-in for Django, especially the invoicing part.
Wordpress is a blog engine. It's great for letting a bunch of people log in and submit news but every feature you implement beyond that is going to be through plugins, and those are routinely compromised. All sites I've deployed that used only the major plugins (Yoast, Jetpack, WooCommerce, etc.) are still running. All third-party ones have since been compromised, which is embarrassing for me. I wouldn't deploy Wordpress for a business again unless the alternative was Magento.
Django isn't bulletproof, but it will stop you from making amateur mistakes as you build it out. There is no convenient plugin architecture with a friendly UI, which makes it harder for yourself (and the client) to change themes/plugins every week and introduce code that can be exploited.