Everyone loves that WordPress editor.
Whitehouse.gov Chooses WordPress, Again
41–50 of 371 posts
Re: Whitehouse.gov Chooses WordPress, Again
#42In this age where the trend is JAM stack, it is refreshing to see that something battle-tested like WordPress was chosen. There's a reason WP has withstood the test of time. (WordPress developers being a dime a dozen also help make the case)
Are we at the point that creating and editing a page in a JAM stack site is as easy as WordPress for non-technical users?
Not a snarky or leading question, I honestly don’t know. I use Hugo for my own internal design things, because I want partials and such, but I have no idea where the ecosystem is at for the “we need a poli-sci intern to copyedit this” use case.
Re: Whitehouse.gov Chooses WordPress, Again
#43Earlier quoted context omitted.
Is that because WordPress is simple , though? There are similar CMSes you can use with e.g. Gatsby. They’re just a glorified build systems, after all — there’s nothing inherently complex about the content management experience. And on the flip side, it’s possible to load up WordPress with enough plugins that it becomes a nightmare to use. I think we see people choose WordPress because it’s familiar, popular, battle-t…
Yes because Wordpress includes frontend rendering (of both the actual pages and the backend admin) by default. This means you get working HTML powered by dynamic content out of the box, and it keeps working as content changes without needing constant builds for static sites. I see the benefits of modern component-driven frontend systems but I think the better opportunity would be to integrate this cleanly into existi…
Like next.js?
Re: Whitehouse.gov Chooses WordPress, Again
#44In this age where the trend is JAM stack, it is refreshing to see that something battle-tested like WordPress was chosen. There's a reason WP has withstood the test of time. (WordPress developers being a dime a dozen also help make the case)
JAM stack (this term is trademarked by Netlify, FYI) is such an awful trend for anyone but developers. The web runs on WordPress because it's SO easy for anyone to stand up a quality, functional website. I drop in on a local WordPress event a few times a year and many of the people there are 60+ and very much non technical but have put together great sites that benefit humanity.
Re: Whitehouse.gov Chooses WordPress, Again
#45I hope we again see the value of using systems like Wordpress for it’s simplicity in getting a blog/website setup and easily modify content. Lately most of the modern marketing websites I see is built using gatsby and next.js. Having been talking to different content/marketing teams, they hate it so much because of the complexity it brings. Editing content? Sign in to this headless CRM app, want a form? Go sign in to…
From an operations perspective, gatsby and next.js are much simpler though. You are just deploying static content behind a webserver or even something like s3. Horizontal scaling is almost trivial. With wordpress though, you have to worry about a database as well, scaling is more complicated, you need to run php on your webservers (which has security implications), updates that include schema updates frequently require downtime, etc.
Re: Whitehouse.gov Chooses WordPress, Again
#46> Political affiliations aside, I think we can all breathe a bit easier today knowing they didn’t choose Drupal. Strongly disagree. Drupal is a great CMS and there's a reason the government uses it so extensively.
The problem is finding people who actually know how to use it. It's great, but it takes years to learn properly. Before that it can be frustrating as hell.
It seems easy enough at first, like you can just use whatever contributed modules you need, but that only works on simple sites (like the same ones Wordpress is great for). To use Drupal well, you have to actually know the APIs and write your own custom modules, otherwise the site becomes a buggy resource hog.
I like Drupal, I have multiple 8/9 sites I still run and I've used it since 6, but there's some pretty good reasons not to use it.
Re: Whitehouse.gov Chooses WordPress, Again
#47Re: Whitehouse.gov Chooses WordPress, Again
#48I hope we again see the value of using systems like Wordpress for it’s simplicity in getting a blog/website setup and easily modify content. Lately most of the modern marketing websites I see is built using gatsby and next.js. Having been talking to different content/marketing teams, they hate it so much because of the complexity it brings. Editing content? Sign in to this headless CRM app, want a form? Go sign in to…
From an operations perspective, gatsby and next.js are much simpler though. You are just deploying static content behind a webserver or even something like s3. Horizontal scaling is almost trivial. With wordpress though, you have to worry about a database as well, scaling is more complicated, you need to run php on your webservers (which has security implications), updates that include schema updates frequently requi…
[deleted]
Re: Whitehouse.gov Chooses WordPress, Again
#49Good. Wordpress is battle tested, open source and in the right hands, secure. Twitter recently tried to dunk on the last administration's use of Wordpress at the State Dept, claiming they were hacked to show Trump had resigned, but it was just a disgruntled employee and was it never hacked.
Re: Whitehouse.gov Chooses WordPress, Again
#50Earlier quoted context omitted.
Is that because WordPress is simple , though? There are similar CMSes you can use with e.g. Gatsby. They’re just a glorified build systems, after all — there’s nothing inherently complex about the content management experience. And on the flip side, it’s possible to load up WordPress with enough plugins that it becomes a nightmare to use. I think we see people choose WordPress because it’s familiar, popular, battle-t…
Yes because Wordpress includes frontend rendering (of both the actual pages and the backend admin) by default. This means you get working HTML powered by dynamic content out of the box, and it keeps working as content changes without needing constant builds for static sites. I see the benefits of modern component-driven frontend systems but I think the better opportunity would be to integrate this cleanly into existi…
Wordpress also has a really rich ecosystem of mature and widely used plugins that are quite easy to install.
The podcast ones for instance, they'll allow you to schedule the publishing of a new episode, then upload the episode to all the major platforms, format the images, titles and descriptions automatically for the different platforms, cross post to the social media accounts announcing the new episode, allow you to put in show notes for the blog, and embed a way to listen to the show on the site, all built in, for free, using an interface that is clean and well documented.
Of course I could do that myself but come on now, that simplifies my life so much.
I'm ok with my government saving money and not hiring six figure tech workers to custom roll effectively a press release website. Honestly, they could redirect it to a medium blog and save on the hosting fees as well. The real infrastructure is going to be at the departments, NASA, Smithsonian, CDC etc...