@sylver_[email protected] @JASN_[email protected] @[email protected]
The amount of design elements (HTML beyond text markdown like divs) and pseudocode (elements that only render when parsed before delivering to the browser) that end up in the content is something to consider. Enabling a text editor alone does not tell you much. You can support easier bold, italic and ~~strike though~~ with a structured data approach.
It's when you get into creating layouts in the editor that really differentiants a page builder from a content management solution.
@bane_[email protected]
@sylver_[email protected] @JASN_[email protected] @[email protected] @[email protected]
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.
https://new.drupal.org/drupal-cms