Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Whitehouse.gov Chooses WordPress, Again

pagely.com

Post reply on HN
Print view View original

361–370 of 371 posts

Re: Whitehouse.gov Chooses WordPress, Again

#361

Post by tolstoyswager »

marc_io wrote: post #251
neurostimulant wrote: post #246

Earlier quoted context omitted.

After a decade of dealing with a fleet of wordpress sites (most of our smaller clients has a wordpress site), our team has settled on a workflow when dealing with wordpress sites for our clients: - a custom docker image suitable for use in docker/kubernetes environment. Vanilla wodpress docker image is not suitable for most of our needs, so we build our own images which includes everything we need an nothing more. -…

Just a quick note regarding Beaver Builder: when the Full Site Editor arrive on WordPress this year, we will be able to use native functionality to build the entire website, without relying on a third-party page builder to do this.

When is it scheduled to arrive?

Re: Whitehouse.gov Chooses WordPress, Again

#362

Post by tootie »

arcturus17 wrote: post #235
tootie wrote: post #55

Earlier quoted context omitted.

A pretty standard stack I've done recently is Netlify, Gatsby (I'd lean next at this point) with Prismic, Hubspot and GTM. It's barely more investment to setup than WordPress but lets you build something visually sophisticated really easily and you get user friendly CMS, CRM and all the analytics and user engagement stuff. And running headless means there's almost zero attack surface.

The very point of OP is that this micro-service approach is bound to provide a poorer user experience for non-technical users - the vast majority will reason about and operate a monolithic CMS with much more ease.

Poorer author experience maybe. The end user experience will likely be better. And the business results of using a proper CRM and audience engagement product will be far superior.

Re: Whitehouse.gov Chooses WordPress, Again

#363

Post by marc_io »

tolstoyswager wrote: post #361
marc_io wrote: post #251

Earlier quoted context omitted.

Just a quick note regarding Beaver Builder: when the Full Site Editor arrive on WordPress this year, we will be able to use native functionality to build the entire website, without relying on a third-party page builder to do this.

When is it scheduled to arrive?

They said (1) that there's no fixed date for the launch, as this is an ongoing effort.

But considering that the initial version of the Site Editor is already part of the official Gutenberg plugin (2) – and they usually include features from the current version of the plugin in the main app – it is expected to be released with version 5.7 of WordPress, next March.

(1) – https://make.wordpress.org/core/5-7/

(2) – https://wordpress.org/plugins/gutenberg/

Re: Whitehouse.gov Chooses WordPress, Again

#364

Post by hmillison »

dgb23 wrote: post #225
hmillison wrote: post #197

Earlier quoted context omitted.

I built out a site using headless WP with Next.js as the frontend. With server side rendering of React, we still took advantage of caching the HTML in a CDN like you would with vanilla WP but it was much easier to build our own theme as desired with React. While configuring certain parts of Wordpress was tricky at times, especially because deploying it is at odds with the stateless nature of modern containerized infr…

Have you been using the preview feature of Next for this to allow for a fast feedback loop for content?

We didn't use it initially because the site was built before they launched that feature, but it definitely reduced some of the boilerplate that we had to write ourselves to wire up Next to WP.

We had already setup a preview page that was wired up to the Wordpress Admin's Preview button that used the endpoint provided by WP to preview content in our UI.

Re: Whitehouse.gov Chooses WordPress, Again

#366

Post by hluska »

viraptor wrote: post #327
hluska wrote: post #148

Earlier quoted context omitted.

If your log only shows an exception without any kind of stack trace or location, I’m sorry but Wordpress is not the problem.

It's not the main problem, but it also could do better. A system encouraging drop in additions could have a way of validating them and blocking plugins which fail.

I agree completely and think that’s a great idea!

Re: Whitehouse.gov Chooses WordPress, Again

#367

Post by thayne »

pembrook wrote: post #360
thayne wrote: post #353

Earlier quoted context omitted.

> The “operations” perspective is the least important perspective on any marketing site/blog. It definitely isn't for the marketing sites and blogs I maintain. Site stability and reliability trump how convenient it is for marketing content creators to release changes. Better to have a site that doesn't have the latest change than a site that is completely down, or worse a site hacked because of a vulnerability in the…

> Site stability and reliability trump how convenient it is for marketing content creators You’re optimizing for the wrong thing then. Content creation, driving traffic to the site, and converting that traffic is the harder, more important task. Your role is the easiest, most trivial one. On the spectrum of engineering problems, I’d place self driving cars and sentient AI somewhere on the right side labeled difficult…

> On the other hand, 99% of all websites get little to no traffic. Maybe this is the difficult part you should be optimizing for instead?

Well, the sites I'm talking about get enough traffic that if they are down for a few minutes people notice, and a single wordpress server isn't enough to handle the traffic ;). If you have little to no traffic that's less of an issue.

Re: Whitehouse.gov Chooses WordPress, Again

#369

Post by proyb »

claudiulodro wrote: post #310
proyb wrote: post #269

When I read there are over 55,000 plugins available, someone on reddit manage to find 16,000+ plugins, the rest could be outdated?

The rest are probably on the various marketplaces and websites around the internet, not the official plugin directory.

Probably, we can only get the actual figures of less than 55,000 from sitemap:

https://wordpress.org/plugins/sitemap.xml

Re: Whitehouse.gov Chooses WordPress, Again

#370

Post by illuminea »

hardwaresofton wrote: post #342
ozorOzora wrote: post #185

Earlier quoted context omitted.

Or you can just roll with JAMstack as it's literally about what you're asking for.

The problem I'm saying exists with JAM stack is that it's great for developers but bad for non-technical people -- wordpress is the opposite, and if I could get JAM stack properties out of Wordpress, I wouldn't use JAM stack for any projects which involved having non-technical people modify the site (which is a lot of them).

You could check out Strattic which gives users the best of both worlds - edit your site as usual in WordPress, and click a button to deploy a static, Jamstack version of the site. All the power of WordPress with none of the headache. https://www.strattic.com
Post reply on HN