Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

While this is a good example of all the good stuff raw django brings to the table, if you build a blog with django, you should go for wagtail in 2023:

https://wagtail.org

- It's incredibly more productive.

- Seamlessly integrates with any django website, or hold your hand to create one from scratch.

- Play nice with the whole django ecosystem.

- Is easy to pick up because under the hood "it's just django". It uses django models, routing, auth, etc. It's uses standards, best practices, and is a good citizen.

- The blog admin and the provided block editor are good out of the box.

- It still gives you all the flexibility you want: it doesn't force any template on you, any page structure, workflow, nothing. You get to decide how simple or complex you blog is.

- The team behind it is super nice.



We moved away from wagtail and it was a bit of a mess to maintain after using it for a couple of years for our marketing website. I think I'd have stayed with native Django if I had gone back in time. In the meantime the team that manages this switched to next.js instead and it's been the most stable / productive setup so far for our marketing website. This being the 4th tool in 8 years (marketing people change their minds a lot).


Thanks for the comments. Did not know much about wagtail until now. Looks worthy of consideration for a side project I am considering.

If you don't mind answering a couple of questions:

- I have a requirement for basically a CMS with the capability of serious extensibility, built in either python or javascript (I considered ghost but it does meet my requirments). Main job is for a membership based cms but to potentially add functionality outside of standard cms stuff. Would you say wagtail / django combo would meet that requirement? (Sounds like "yes")

- How does wagtail compare to django cms? (Less interested in feature comparisons, more interested in your developer experience with both)

Thx in advanced!


Wagtail is not your usual CMS is that unlike the competition (such as django cms), it doesn't come with any kind of structure.

On one hand that means you have to do more work: define exactly what you want, then declare it in code, then build the templates.

On the other hand it means you can do exactly what you want, including the requirements you just mentioned.


Will wagtail work in 10 years from now? Being Python and Django, it just might. In the node ecosystem, things are broken after 10 weeks or 10 months.

The benefits of static site generations...


Wagtail first shipped 9 years ago in 2014. It's already old/boring, and great!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: