@bane_killgrind@slrpnk.net
@sylver_dragon@lemmy.world @JASN_DE@feddit.org @jonathan@lemmy.zip @jackalope@lemmy.ml
It can be, but a large percentage of WP installs aren’t even blogs that manage posts over time. They are basic 20-30 brochure-ware sites that use WP as a page builder.
WP is popular with .edu sites where they are managing thousands of structured content types; faculty profiles, academic programs, events, etc.
Drupal is also a popular solution for that type of project where managing a large amount of structured data is a key feature.
My experience has been that WP needs to “built up” to handle large site while Drupal needs to “burned down” to be a good fit for small, page building projects.
Though Drupal’s new preconfigured Drupal CMS installer with “recipes” for different use cases is making it a better option for smaller site projects.
@Cris_Color@lemmy.world
@abeorch@friendica.ginestes.es @pastermil@sh.itjust.works
Many years ago I worked on a project with some FSF staff who refused to use non-FOSS solutions to coordinate or conduct meetings. While the developers involved where all prolific contributors to open source projects used by millions of people, they were all willing to compromise on some of the tools we use to develop and communicate for “the greater good”. The FSF staff weren’t willing to make those compromises. At the time I was frustrated by this. As Slack ownership changed, costs increased and policies around what they could do with “our” data evolved, I now have a lot more respect for the FSF staff who are “holding the line”.