@seo_sitch @natmiletic A good dev can create a much better admin experience without a page builder.
English
WP Editorial ⚡
1.1K posts
WP Editorial ⚡
@wpeditorial
Editorial and news content about all things WordPress.
Katılım Nisan 2020
133 Takip Edilen175 Takipçiler
@wpeditorial @natmiletic I've seen good Elementor sites. The problem is that it's easy to use to the point it's easy to shoot yourself in the foot. A careful dev using it can do it OK, but the bloat is real when you try to use nested containers everywhere.
English
What a lot of people don't realize is that Elementor is bigger than Wix, Squarespace, and Webflow combined!
Jeff@jeffr0
Things I Learned: Elementor practically has its own publishing interface. In fact, the whole thing is like a substitute for everything WordPress offers in the publishing experience. You either love it or you hate it. A lot of people love it.
English
@gridpane @mihai_iova Good devs aren't the problem though in most cases with WordPress... It's the 'builders' that are throwing some Theme Forest WP Bakery monstrosity at it with 10,000 plugins...
English
@wpeditorial @mihai_iova As complexity of the workload increases, the number of plugins required also increases.
But this is also true at Shopify, even though their core deliverable is more end-to-end complete for many shops.
Making either work is totally formulaic.
I sleep great, I promise.
English
Customers churn.
In SliceWP's case the number one reason customers have churned this year is because they've migrated from WooCommerce to Shopify.
I do wonder, do you know of people migrating from Shopify to WooCommerce recently? What's their story?
English
@gridpane @mihai_iova You can say that for most of WordPress. But with Woo more than 'regular' sites there's some key functionality missing that gets filled by plugins, because that's how it's monetized.
English
@wpeditorial @mihai_iova Almost all of these "issues" are actually just skill issues.
Yes, Woo can be an enormous pain in the ass.
It can handle any amount of scale you can throw at it AND it solves issues that Shopify will never solve.
Gray markets and data sovereignty, off the top of my head.
English
@jeangalea ManageWP offers Patchstack at less than $2 per site, per month. That alone is worth it. No matter how often you do updates, Patchstack will always be ahead of the game.
English
WordPress dashboards are dying.
I was paying $100+/mo for one.
Felt “professional.”
Then I realized:
Updates → WP-CLI
Backups → hosting
Uptime → hosting
Security → hosting
Now: WP-CLI + AI agent over SSH.
No dashboard. No fees.
Why do people still pay for dashboards?
English
English
Has anyone tested running Studio at the same time as @LocalWP? I'm pretty much done with Local cause I can't do both, and need Herd running, and WP on Herd works but feels too tedious.
WordPress.com@wordpressdotcom
Early access! WordPress Studio now has an independently installable CLI. One command to install: npm install -g wp-studio And another to run WordPress locally, no desktop app needed: npx wp-studio It works on Mac, Windows, and Linux and makes it easy for your AI coding tools to interact with Studio. Sync, import, export, and more are coming soon. 👀 Free to install and use.
English
@mihai_iova A bit of both, but typically, WooCommerce sites are running on absolute spaghetti of plugins, just waiting to break with the next update.
English
@wpeditorial Is WooCommerce a maintenance headache by itself or is an online store built on WordPress a maintenance headache?
English
@wesbos Of course not, but being rational doesn't make good engagement bait.
English
Are we really gonna let website owners go nuts with ai site builders?
I think back to my wordpress days and i used to strip the WYSIWYG of every unapproved color and font size. Disabled installing plugins.
If I didn’t, they would make a mess. It looked like a MS word doc in 2 days. Maybe AI make it easier for them to not make a mess?
English
@dipakcgajjar @jdevalk At this point it just be engagement bait. Former owner of a bloated SEO plugin suddenly cares about speed...
English
A properly configured WordPress site with object cache and a CDN in front is already near-static in terms of delivery. You just get the CMS on top for free.
Good luck @jdevalk convincing a non-technical client to push markdown files to Git just to publish a blog post. WordPress exists because content management is a real problem. Static tools solve the developer experience, not the client experience.
Joost de Valk@jdevalk
I built Yoast SEO. I ran my blog on WordPress for years. Then yesterday I moved it to static HTML. Everything that matters, SEO, search, schema, is still there. What I dropped was the overhead. Do you actually need a CMS? For quite some sites: no. joost.blog/do-you-need-a-…
English
@EarleDavies_ @cameronjonesweb How big are these clients? Most companies of a reasonable size have a marketing department that want to do the updates...
English
@wpeditorial @cameronjonesweb Where did I say *required*? Nowhere. Every single site I've ever built was extremely easy to update for everyone. Clients in my experience would rather pay someone else to update it still. They want to run their business, not update WP content.
English
This is emblematic of the problem WordPress has had for close to a decade now
The people building for WordPress aren’t building with WordPress
Hands up who thinks it’s a great idea to make their clients update their website content by committing markdown files to GitHub…
Joost de Valk@jdevalk
I built Yoast SEO. I ran my blog on WordPress for years. Then yesterday I moved it to static HTML. Everything that matters, SEO, search, schema, is still there. What I dropped was the overhead. Do you actually need a CMS? For quite some sites: no. joost.blog/do-you-need-a-…
English
@cameronjonesweb @EarleDavies_ Same experience. Only badly built sites require an agency to make updates.
English
@EarleDavies_ Less than 10% of clients I’ve worked with have required the developer or agency to make all their content changes, yes. If you include sites that are almost never updated, maybe another 10-20% at a stretch. Vast majority can and do manage their own content
English
@jdevalk Amazing that the creator of Yoast cares about speed...
English
I built Yoast SEO. I ran my blog on WordPress for years. Then yesterday I moved it to static HTML.
Everything that matters, SEO, search, schema, is still there. What I dropped was the overhead.
Do you actually need a CMS? For quite some sites: no.
joost.blog/do-you-need-a-…
English
@jeffr0 @markjaquith ASE has this built in now, and has a bunch of other uses.
English
Hey @markjaquith do you still maintain this plugin? Any plans on closing it? It seems folks still find it useful.
Anita@TheCre8tiveDiva
I totally forgot about this plugin! It hasn't been updated in 2 years but I have so many uses for this. wordpress.org/plugins/page-l…
English
@PeakZebra @groundworxdev Interesting. How will this work when real time editing come in to play? Keep the old locking system?
English
@wpeditorial @groundworxdev Just as an aside, what I'm talking about are extensions to core blocks that make their content editable on the front end and use REST calls to update the underlying post records at the server.
English
I am curious, what has stopped you or your agency from adopting WordPress FSE yet? What is your biggest challenge you are facing? Or if you don’t even consider it, what works for you right now that FSE is not solving?
English
@groundworxdev @PeakZebra You can definitely run in to performance issues with too many acf fields, but there's lots of optimisations that can be done. I don't think the experience of mixing traditional meta fields with blocks is very good yet, although it's been a while since I touched it on large sites.
English
not at all! FSE is actually ideal for enterprise level solution. I have done plenty of schools/college, governement, banks, homebuilder, and commercial rental space, some of them had quite a bit of posts, events and more. Works beautifully. That is also why I try to avoid ACF because the editor becomes almost unusable because it has to pull in all those previews, it slows down the experience. I use native custom fields instead and build the UI for the editing experience. I also build all my blocks to be modular and easy to customize with little effort. You should give it another try!
English
@cipriangb Would love to hear how this affects the speed and server resources at scale. Have you tested at 1000's of visitors?
English
I have reduced the number of queries on a #WordPress website with Avada theme from 248 to 18!
Lighthouse ships a SQLite3-backed persistent object cache drop-in. When installed, WordPress will use a local SQLite database instead of re-running database queries on every page load.
English
@groundworxdev @PeakZebra That sounds like a reasonable solution, but I'd imagine the front-end gets pretty bloated like most Divi sites. How far have you scaled this? Most sites we manage are 1000+ posts/pages/cpts
English
This is a good question! You can make a block that saves into custom fields of the post you are editing. If you need that data crawlable. You can also set your post type to lock in blocks, so when you create a new page it starts with those blocks. As long as you have one section for inner content, they can add anything in that section
English
@PeakZebra @groundworxdev How do you use data on pages for other things when it's all in the post content?
English
@wpeditorial @groundworxdev Honestly, they need my baby, PeakZebra.com, in which you can (with admin rights, of course) edit text and images on the front end of the site. Everything lives in patterns and a pattern library, and you can add/delete/reorder patterns on the front end as well.
English