Building a Blog in Django

1

Fly.io

#Cloud Computing #Developer Tools #Cloud Hosting 436 social mentions

2

Wagtail CMS

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.

#CMS #Blogging #Blogging Platform 39 social mentions

3

HedgeDoc

Nice and simple. I feel the only lacking feature for a basic blog is having unlisted blog posts, which is very handy when you want to share it to proof-readers. This can be done on google doc/hedgedoc [0] for sure, but then when porting there are very often typos creeping in. [0] https://hedgedoc.org/.

#Office & Productivity #Tool #Markdown Editor 30 social mentions

4

Directus

The admin is extremely unacceptable for anything beyond trivial borderline trivial use cases, and the modifications you'd have to make are just awful especially the more interactive something needs to be. The extremely tight integration between models and the modeladmin is a blessing and curse. The people who like Django,also tend to overload it to do everything. This makes sense at small companies. The only place I really see Django at large companies is as an api using DRF or something. For internal admins, I've been lobbying to use https://directus.io/ at my company.

#CMS #Blogging #Blogging Platform 118 social mentions

> The only place I really see Django at large companies is as an api using DRF or something. This is not a bad thing. Using Django as an API backend is amazingly fast in terms of development time, especially with modern frameworks such as django-ninja [1]. Just use the built-in ORM to create models, write your endpoints, and use the built-in admin interface to play with the database if you don't have endpoints for everything. There is also a less known feature of Django called admindocs [2], which automatically generates a human readable, hyperlinked documentation for your models and relations between them. [1] https://django-ninja.rest-framework.com/ [2] https://docs.djangoproject.com/en/4.2/ref/contrib/admin/admindocs/.

#Application And Data #Languages & Frameworks #Microframeworks (Backend) 26 social mentions