We’ve still been working with Django on a redesign of a site’s blog module. Still liking the tool- it’s a bit tricky to figure out initially (the url routing in urls.py took me way too long to wrap my head around- and I wouldn’t say I’m fully clear on most of it), but overall it’s so useful.
But in any bargain, there are downsides. We were customizing the log in screen to get away from the default Django scheme (to try not to scream “We used a template for this!”). Got the template overriding process down, but ran into an issue on something that should have been real simple.
We wanted to add placeholder text to the username/password fields (we were trying to create a slick, no-label login form). But the actual input fields are generated ‘behind the scenes’ by Django. Usually very useful, as then we don’t have to do it ourselves, but if there’s something it doesn’t include by default (like placeholder text), it can be tough to add it in (at least for a Python newbie like me).
Sometimes it’s best to fall back on your strengths (at least, that’s what they tell me- and I tell myself JS is my strength!).