![]() It's now WAY overkill, but it still works well. Long story short, that's why my online diary (not linked anywhere) runs Drupal 10 to this day. Wordpress still had that "holes, billions of holes" stigma, so I went with Drupal. I had a choice at that stage between Drupal (version 4 it was) and Wordpress. After a while it imploded so I migrated to Drupal. After a while, PHP-Nuke imploded and so I migrated to PostNuke. When I first moved to New Zealand, I started a diary (before the term blog existed!) using PHP-Nuke. It turns out the average website doesn't need to maintain a lot of custom CMS code/workflow/logic they just need to track a handful of blobs of text/image content. That's not a bad thing, that's just product differentiation. Ultimately, Drupal focused more on its core strength. The current community of the Drupal world has kept focusing on improving the UX of the site builder/maintainer role with its current initiatives (auto-updates, project browser) to self-correct. ![]() Unsurprisingly, it became more WP-like as it tilted more toward PHP CMS as a product. ![]() It has always focused on open-source PHP CMS as a framework.īackdrop happened for those who wanted a good off-ramp for those who were happy to keep the current Drupalisms of D7 and didn't need more PHP-web-dev tools. That decision caused the casual site-builder who knew little PHP code to say "no thanks". It has always focused on open-source PHP CMS as a product.ĭrupal has always been an engineer-first CMS D8 doubled down on that: focus on long-term maintainability with OOP/Symphony/Composer/etc. Wordpress has always been a more product-focused blog/site-builder that works out of the box and simplifies code concepts for an average user who doesn't need to know much PHP to get everything they want to be done. The Drupal community made a pivotable decision that ensured it would never "win" a CMS battle with WP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |