3 ms·

I wouldn't even really call it that. I only think Wordpress is easier if one of two things is true: 1. You are actually building a dynamic site; eg WooCommerc

I wouldn't even really call it that. I only think Wordpress is easier if one of two things is true: 1. You are actually building a dynamic site; eg WooCommerce is much easier than building your own storefront. 2. Your users refuse to use Markdown, and are paying you enough to double the overhead and put it all on you. It gives me a good chuckle when I see posts on here like "We use Wordpress and then scrape the static assets and serve it as a static site from S3". I won't denigrate those people; I'm sure there are good contextual reasons to do that. I just think it's a pretty damning indictment for it to be downgraded from "the software that runs the website" to "a web-hosted WYSIWIG editor for people who can't/won't do Markdown".

cj 2y ago
In my experience, Markdown isn't the barrier. It's the: - Plugin ecosystem. Marketing people want to use specific plugins for SEO, automatic internal linking, etc. Those plugin only work with wordpress. - Marketing people want to deploy to production. They hate waiting for dev to do anything (which brings us back to the importance of the plugin ecosystem, to add functionality without developers). - It's a familiar system that doesn't need to be "learned" by end users (the same way VS Code, VIM, or whatever is your preferred code editor) If it weren't for the first 2 barriers, I think the 3rd (learning markdown) is the easiest to overcome. Especially with side-by-side realtime markdown rendering, which itself is a form a WYSIWYG. Edit: FWIW, we moved to Webflow at my company, used to be on Wordpress, and before that used to have a Markdown-compiled site, help docs, and blog. Markdown-compiled was my favorite as a developer (and also the most performant), but it was everyone else's least favorite because it required me to deploy and make code changes, and they weren't patient enough to put a ticket in for every change request. They also understandably didn't want to login Github to make updates to markdown files.
- theyknowitsxmas 2y ago
  Not really. Weird syntax is intimidating, GitHub for CMS is intimidating, people want nice goowies.
  - cj 2y ago
    Asking your dev team to prioritize deploying updates to your markdown site is also intimidating. In most companies, everyone outside of engineering has a view of engineering that “Developers hate to be interrupted and need everything scheduled in a sprint 2 weeks in advance” - when marketing teams decide between Wordpress and a markdown system managed by the dev team, the choice is obvious (avoid anything that requires dev getting involved) Easy GUI for writing and publishing to production, with no-code installable plugins that extend functionality, is exactly what Wordpress offers that markdown does not. Webflow has a very similar value prop.
deleted 2y ago
[deleted]

cj 2y ago

In my experience, Markdown isn't the barrier. It's the: - Plugin ecosystem. Marketing people want to use specific plugins for SEO, automatic internal linking, etc. Those plugin only work with wordpress. - Marketing people want to deploy to production. They hate waiting for dev to do anything (which brings us back to the importance of the plugin ecosystem, to add functionality without developers). - It's a familiar system that doesn't need to be "learned" by end users (the same way VS Code, VIM, or whatever is your preferred code editor) If it weren't for the first 2 barriers, I think the 3rd (learning markdown) is the easiest to overcome. Especially with side-by-side realtime markdown rendering, which itself is a form a WYSIWYG. Edit: FWIW, we moved to Webflow at my company, used to be on Wordpress, and before that used to have a Markdown-compiled site, help docs, and blog. Markdown-compiled was my favorite as a developer (and also the most performant), but it was everyone else's least favorite because it required me to deploy and make code changes, and they weren't patient enough to put a ticket in for every change request. They also understandably didn't want to login Github to make updates to markdown files.

theyknowitsxmas 2y ago
Not really. Weird syntax is intimidating, GitHub for CMS is intimidating, people want nice goowies.
- cj 2y ago
  Asking your dev team to prioritize deploying updates to your markdown site is also intimidating. In most companies, everyone outside of engineering has a view of engineering that “Developers hate to be interrupted and need everything scheduled in a sprint 2 weeks in advance” - when marketing teams decide between Wordpress and a markdown system managed by the dev team, the choice is obvious (avoid anything that requires dev getting involved) Easy GUI for writing and publishing to production, with no-code installable plugins that extend functionality, is exactly what Wordpress offers that markdown does not. Webflow has a very similar value prop.

deleted 2y ago

[deleted]