Blog / Category
Strategy
8 posts in this category.
-
The plugin pile-on: five plugins one DesignSetGo app can replace
Read post →Calculated Fields Form + WPForms + Tasty Pins + a custom CSS plugin + Insert Headers and Footers. That stack is one DesignSetGo app, sandboxed, with a fraction of the admin surface.
-
Ghost, Substack, Hashnode, or WordPress for the blog on your vibe-coded site?
Read post →Four real options for the blog half of a Lovable, v0, Bolt, Claude Code, or Astro site. Which one fits behind a vibe-coded homepage without fighting it, and which one is the lock-in tax you do not want.
-
blog.yoursite.com or yoursite.com/blog? A decision for your vibe-coded site
Read post →Three real ways to add a WordPress blog to a vibe-coded site: subdomain, subdirectory reverse proxy, or one WP install hosting the front-end too. The SEO, cookies, and auth consequences of each.
-
Keep WordPress for the blog, vibe-code the rest? Try one site instead of two.
Read post →You vibe-coded your homepage in Lovable, v0, or Claude Code. You still want WordPress for the blog. The natural plan splits across two hosts; here is the one-site shape that does not.
-
The WordPress plugin I do not want to build anymore
Read post →There is a kind of WordPress plugin I have built too many times. It starts as a small client request: Can we add a little calculator to this page? Or: Can members see a simple dashboard when they log in? Or: Can we make a product selector that recommends the right plan? None of these […]
-
WordPress is the backend your vibe-coded app forgot it needed
Read post →Vibe-coding made front ends feel free. Describe a calculator. Get a calculator. Describe a dashboard. Get a dashboard. Describe a quiz, a planner, a product selector, a lesson browser, a directory, a lead magnet. The first version appears fast enough that it changes what you are willing to try. That part is real. The bottleneck […]
-
DesignSetGo vs headless WordPress
Read post →Headless WordPress assumes the right answer is to put a wall between the front-end and WordPress, then build a glue layer to span it. DSGo says: don’t put up the wall.
-
Why we don’t hold your API keys (and why every other AI WordPress plugin should worry about that)
Read post →WordPress 7.0’s Connectors API made BYOK-through-proxy structurally unnecessary. The plugins that didn’t notice are about to find out their margins were illusory and their compliance was hand-waved.