Alright let's settle this once and for all 👀

Team WordPress: flexible, huge plugin ecosystem, been around forever

Team Webflow: clean visual builder, faster to design, no plugin hell

If you had to pick ONE for a client project today, which are you going with and why?

Bonus points for horror stories 😅

I spent a while stacking caching plugins and wondering why things weren't as fast as they should be. The thing that fixed it wasn't a plugin, it was understanding that the three caching layers do completely different jobs and you build them from the bottom up.

OPcache is the foundation. It caches compiled PHP bytecode so the interpreter isn't recompiling your code on every request. It helps every single PHP app, it operates independently of everything else, and you basically never turn it off. In production I set validate_timestamps=0 and just flush it on deploy.

Object caching (Redis or Memcached) sits above that. It stores the results of expensive database queries so WordPress isn't making dozens of DB round trips per page. This is the layer that matters most for logged-in users and anything dynamic, because those requests skip page caching entirely.

Page caching (Nginx FastCGI cache for me) is the big hitter for anonymous traffic. A cached page never touches PHP or MySQL, it just serves HTML. Massive for traffic spikes, but useless for logged-in users, so you set proper bypass rules for wp-admin, carts, checkout and logged-in cookies.

The lightbulb moment was realizing they don't compete, they cover for each other. Page cache handles anonymous hits, object cache carries the cache misses and logged-in users, OPcache speeds up all the PHP underneath both. The mistakes I'd been making were running two page cache solutions at once and expecting object cache to help on pages that were already fully page-cached (it doesn't, page cache bypasses WordPress completely).

The other thing that clicked: the right strategy depends on your site. Marketing sites lean hard on page caching. Membership and ecommerce lean on object caching because everyone's logged in. Frequently updated content sites need shorter TTLs and smart invalidation.

I wrote the full guide up with the actual php.ini, wp-config and Nginx config snippets in this article Understanding WordPress Caching Layers: A Developer's Configuration Guide. Curious how you guys handle cache invalidation on fast-moving sites, that's the part I still tweak most.

I run an excavation/demolition company and have been trying to find a service-based CRM that actually fits the way we operate. I’ve looked into Workiz, Jobber, QuoteIQ, and a few others, but none seem to check all the boxes.
What I like about Jobber is the simplicity and ease of use, but I’m looking for something that can handle more of the operational side of a heavy equipment contractor.
Ideally, I want one system that can handle:
Clients, leads, estimates, jobs, invoicing, and billing
Job photos, documents, and notes
Calendar/scheduling with crews and individual employees assigned to jobs
Non-consumable equipment assigned to jobs the same way you would assign an employee or crew
Equipment availability so we can see where everything is scheduled and avoid double-booking it
Employee time tracking tied to specific jobs
Employees being able to log equipment hours/mileage
Pre-trip/pre-use inspections
Damage reports and maintenance issues
Individual history for each piece of equipment
The equipment side is where most CRMs seem to fall apart for us. We’re not talking about tracking consumable inventory. We have excavators, skid steers, dump trucks, trailers, attachments, ring saws, industrial pressure washers, specialized tools, etc.
I’d like to be able to assign something like an excavator + trailer + truck + operator to a project on the calendar and have all four treated as resources. Then, while it’s assigned, employees could record hours, inspections, damage, maintenance issues, etc., against that specific piece of equipment.
Right now, we’re basically using four different systems: a calendar/scheduling app, equipment management app, CRM, and billing/accounting app. It works, but there’s a ton of duplicated information and bouncing between apps.
Has anyone found something that can actually bring all of this together without becoming an overly complicated enterprise system?
I’m basically looking for Jobber-level simplicity with legitimate fleet/equipment management built into it.
Would especially like to hear from excavation, demolition, grading, concrete, trucking, or other equipment-heavy contractors about what you’re actually using day-to-day.

Been doing wp work and my setup feels stuck in 2018. laragon for local, vscode, wp-cli, and a terminal open just to watch debug.log lol.

Is everyone on localwp / ddev now or does that not matter much? and the php version thing across older sites drives me nuts, curious if you just keep separate stacks or something smarter

whatever you're using, even if it's ugly, I want to hear it...

Hi,

I need to change the attached header to include two seperate images in the middle.

The website uses Avada and I understand I need to create a new Layout section to replace this.

The problem is that it's proving difficult to apply the style of the red contacts/ social row at the top and the Nav section at the bottom to the new header.

Is there an easier way of doing this in Avada?

The client understandably assumes this is a simple change!

Thanks