Per Søderlind soderlind

Enable WordPress Customizer Preview on Mapped Domain

If you are using the WordPress MU Domain Mapping plugin to map domains on your WordPress Multisite, the preview feature in the WordPress Customizer will not function. To resolve this issue, save enable-customizer-preview-mapped-domain.php, as must-use plugin, in wp-content/mu-plugins.

prompt

I want to create a script that retrives all stats from all site at my plausible account:

APIs:
   https://plausible.io/docs/sites-api
   https://plausible.io/docs/stats-api

1. Find all sites in my plausible account using the site api

Plausible roll-up for WordPress

Also available, Plausible Stats Aggregator

If you have multiple sites and need a roll-up view, you can use the plugin below.

Prerequiste

Plausible Analytics for WordPress activated on each site.
A roll-up domain

To make this the default in Local, please vote

Local (localwp.com) + direnv + VS Code

This guide wires up Local (localwp.com) with direnv so your terminal & VS Code always use the correct WordPress environment for each Local site. It includes:

Installing the Local direnv add‑on from the 1.0.0 release tarball.
Shell hook instructions for macOS, Windows, and Linux.
Configure VS Code to inherit environment variables from the current Local shell session

Constitution: Spec‑Driven Development for WordPress Projects

Non‑negotiable principles that every specification, plan, task, and implementation MUST follow. Words MUST/SHOULD/MAY are to be interpreted per RFC 2119 semantics.

1) Purpose & Scope

This constitution governs WordPress plugins, themes, blocks, and headless integrations developed in this repository.
It constrains the /speckit.specify, /speckit.plan, /speckit.tasks, and /speckit.implement outputs. When in doubt, follow this constitution over any generated content.

⠀⠀⠀⠀⠀⠀⣀⣤⣶⡶⢛⠟⡿⠻⢻⢿⢶⢦⣄⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⢀⣠⡾⡫⢊⠌⡐⢡⠊⢰⠁⡎⠘⡄⢢⠙⡛⡷⢤⡀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⢠⢪⢋⡞⢠⠃⡜⠀⠎⠀⠉⠀⠃⠀⠃⠀⠃⠙⠘⠊⢻⠦⠀⠀⠀⠀⠀⠀
⠀⠀⢇⡇⡜⠀⠜⠀⠁⠀⢀⠔⠉⠉⠑⠄⠀⠀⡰⠊⠉⠑⡄⡇⠀⠀⠀⠀⠀⠀
⠀⠀⡸⠧⠄⠀⠀⠀⠀⠀⠘⡀⠾⠀⠀⣸⠀⠀⢧⠀⠛⠀⠌⡇⠀⠀⠀⠀⠀⠀
⠀⠘⡇⠀⠀⠀⠀⠀⠀⠀⠀⠙⠒⠒⠚⠁⠈⠉⠲⡍⠒⠈⠀⡇⠀⠀⠀⠀⠀⠀
⠀⠀⠈⠲⣆⠀⠀⠀⠀⠀⠀⠀⠀⣠⠖⠉⡹⠤⠶⠁⠀⠀⠀⠈⢦⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠈⣦⡀⠀⠀⠀⠀⠧⣴⠁⠀⠘⠓⢲⣄⣀⣀⣀⡤⠔⠃⠀⠀⠀⠀⠀
⠀⠀⠀⠀⣜⠀⠈⠓⠦⢄⣀⣀⣸⠀⠀⠀⠀⠁⢈⢇⣼⡁⠀⠀⠀⠀⠀⠀⠀⠀

How I do vibe coding in 3 steps (plus a Step 0)

Start with domain expertise
Vibe coding works best when you have enough domain expertise to set direction, ask precise questions, and validate the output.
Jam with an AI chat — then “lock in” a single strong prompt
I start by brainstorming with ChatGPT (or another chat model): goals, constraints, edge cases, and what “done” looks like.
I end by asking the AI to produce one clean prompt that includes:
- problem statement + scope (what to do / not do)

assumptions and constraints

Benchmark report: WordPress ticket #64863

Branch: benchmark/64863
PR: #11257 — Eliminate switch_to_blog() from multisite option/post functions
Environment: PHP 8.3.30 · WordPress 7.0-beta5-61991-src · MySQL 8.4 · Docker (linux/amd64 via Rosetta on arm64)
Method: 200 iterations × 3 runs per function, median taken. Cold = cache flushed before each run. Warm = cache intact.

	<?php
	$redis_config = [
	'token' => '••••••••',
	'host' => 'tls://MY-REDIS.norwayeast.redis.azure.net', // enterpriseCluster = host mode
	'port' => '10000',
	'username' => 'default',
	'password' => '••••••••',
	'database' => 0,
	'client' => 'phpredis',
	'serializer' => 'igbinary',

	# ── Oh My Zsh ────────────────────────────────────────────────
	export ZSH="$HOME/.oh-my-zsh"
	IS_VSCODE=$([[ "$TERM_PROGRAM" == "vscode" ]] && echo true \|\| echo false)

	if [[ "$IS_VSCODE" == "true" ]]; then
	ZSH_THEME=""
	# Reduce title/prompt noise before Oh My Zsh initializes.
	DISABLE_AUTO_TITLE=true
	COMPLETION_WAITING_DOTS=false
	DISABLE_UNTRACKED_FILES_DIRTY=true