3 ms·
I was waiting for someone to mention this as I scrolled from the top to bottom... I have been implementing Drupal consistently since v4.0 and despite it's incre
by winternett 5y ago
I was waiting for someone to mention this as I scrolled from the top to bottom... I have been implementing Drupal consistently since v4.0 and despite it's increasing footprint, I haven't seen anything it really can't do as a CMS and web app platform.
No code on Drupal isn't exactly pretty, it requires a lot of CSS work to look good, but out of the box it's reliable and quite secure and robust. I've also implemented it in some of the most secure settings without problems over years. The ke to stability is scanning code prior to deployment for outbound requests, not building/adding what isn't needed or used, applying updates on time, and designing and maintaining a secure architecture (zero trust if data value warrants it).
I have built a lot of cool and mission critical things and sites with Drupal, and I'm very thankful for finding it years ago. v7.X is still my fave, the modules were so much more thought out and available for it, and still are. One of the best aspects of building with it is that the community never really turned into a money factory for modules like Wordpress did. As far as downsides, the hardest thing is debating other developers on why it should be used over other frameworks or instead of a custom app without burning up valuable project time. As a testament to Drupal's reach, it's implemented on many key web sites to this day, all you have to do is google it.