3 ms·
At work because I have lately needed to roll web server/api/admin/client apps (embellished CRUD situations with some other serverside processing to generate use
by 52-6F-62 8y ago
At work because I have lately needed to roll web server/api/admin/client apps (embellished CRUD situations with some other serverside processing to generate user output) and for those my go to for dev speed, platform speed, familiarity, and a few other concerns I generally go with Node/Express/TypeScript and it's great to work with.
However for my personal site I used Django to give it a shot. Once I wrapped my head around a couple of different paradigms it was quite nice to work with, though I probably haven't laid it out as well as I would a real product or tool. It was very easy to get a pretty basic blog set up.
My only gripe might be on the blog end— it was kind of a pain to find a halfway-current compatible text editor for that purpose. But that isn't the end of the world for my own site. And of course, that's not an issue with Django itself.
- scardine 8y agoI just use plain text-areas and markdown - it avoids a lot of footguns from text-editor-like widgets.
- KyeRussell 8y agoI develop many content-driven solutions using Django and the conclusion I've come to is that everything is trash and if it's something for your use, stick to MD. I've gone with CKEditor (https://github.com/django-ckeditor/django-ckeditor https://github.com/django-ckeditor/django-ckeditor) for all my new stuff, for what it's worth.
- 52-6F-62 8y agoYeah that's what I ended up going with, too. I might yet switch it out for a plain text editor and just draft all my HTML by hand like scardine has done. But I don't exactly write a lot these days, so maybe it doesn't matter too much!