PeakZebra

You are a request classifier for a local-first AI router. Your job is to classify the user’s incoming request into exactly one of three categories: 1. local_model Use this when the request can likely be handled well by a small local language model. Examples: – Simple explanation or rewriting – Brainstorming – Summarization of short provided text – Drafting simple prose – Low-stakes coding help – General reasoning that does not require current facts or frontier-level capability 2.

You are helping me design and build a [[personal AI operating system]] and a public-facing media project documenting it. Context: I am building a local-first system that stores my decisions, rules, preferences, constraints, and open questions in a portable format (primarily Markdown). This system is intended to be used by AI tools to assist with reasoning and decision-making, but not to take uncontrolled actions.

A common mistake: designing your WordPress experience based on someone’s job title, company size, or industry. It feels intuitive—but it’s often misleading. As often as not, it’s what vendors offering personalization are focused on, but that’s misleading too. My ground rule is that you should never define a segment unless someone in the segment is trying to solve a different problem or will potentially buy for another reason, compared to people in other segments.

This is my truth for 2026, I think. Maybe the strongest aspect of WordPress in this moment is the ability to group blocks together into patterns that can be stored, shared, reused, and all the while these patterns can seamlessly inherit site configurations like typefaces and color palettes. For most people, the best way to put a new website together is to work with a coordinated set of patterns.

Some developers think they need to ditch WordPress for Vue, Laravel, or Next.js to build “real apps.” But most of what people call “apps” comes down to a few behaviors: Remembering user state Responding to interactions without a full page reload Showing dynamic content based on logic Guess what? WordPress can do all of that. (And so can Vue, and Laravel, and Next.js). Right now. No need to migrate your whole stack just to create a dashboard or client tool.

When people talk about newsletters, they often mean a specific thing: a personal note, a predictable structure, a sense of cadence and continuity. But some of the most interesting newsletters today quietly ignore that playbook. They use email not as a genre, but as a delivery channel—and the result is work that feels closer to essays, research logs, memos, or living documents than to “issues.” Here are a few concrete examples, and what they reveal about where newsletters are headed.

Over the past couple of months I’ve been neck-deep in PeakZebra’s product work—refining PZForms, testing microsite workflows, and building out the managed WordPress stack that will eventually underpin everything. But as often happens when you’re talking to customers, exploring integrations, and shipping features, a bigger pattern started to emerge. Thank god for that, by the way. It’s very hard to keep grinding when you’re not entirely sure what the big picture is. It’s a motivation downer.

When I first started using InstaWP, I was interested to see that their sites don’t set you send email. They absolutely expect you to add in an SMTP provider or point to your own mail server. There are reasons for this, but one of them is very probably that they just aren’t impressed with the deliverability of email from a WordPress site straight out of the box. Stuff doesn’t actually send, or sends and winds up thrown out by a spam filter somewhere between you and the intended reader.

That’s a start. But real personalization goes further. Personalization responds to the user’s salient facts. It almost isn’t personalization to just paste in the first name, because every user gets that exact same treatment, just with a different name thrown in. It means showing different flows based on a user’s data and behavior. It means reordering priorities based on past actions, adjusting CTAs based on what the person hasn’t done yet, and updating what appears based on role, tag, or interaction.

Most websites act like goldfish. Every time you return, it’s like the first time. Shortest memory in the natural world (at least according to Ted Lasso). But a good site feels familiar. Recognizable. Maybe even a little empathetic. That doesn’t require a complex recommendation engine. It just means: Remembering a user’s name Showing the next logical step Adjusting copy or layout based on past choices WordPress is more than capable of this kind of memory.