Blog

News, tutorials and release notes for Canvasly Web Studio, Sidcraft and VidCellar.

Showing posts tagged “WordPress”. Show all posts

· Suhaib Siddiqi · blog

The Evolution of Canvasly Web Studio

Canvasly Web Studio did not start as a grand plan. It started as a small annoyance: I wanted to edit my WordPress pages without opening WordPress. Every feature since has come from the same place, a real problem I kept running into, solved one step at a time. This is that story, told in the order it happened.

Read the post The Evolution of Canvasly Web Studio →

· Canvasly Web Studio · Tutorials

Migrate WordPress to Astro or Next.js With AI: Step by Step

"I moved my WordPress site to Astro in a weekend with AI." You see a post like that on X every few days. Sometimes it is true. More often the weekend produced the home page, and the other 80 pages, the contact form, the redirects and the search rankings were still waiting on Monday. AI is genuinely useful for this job. It is not a magic button, and the posts that say so leave out the boring half. This guide shows how to migrate a WordPress site to Astro, Next.js, Vercel or plain static HTML using the Canvasly AI chat, the MCP server and Bind to WordPress, and where you still have to check the work yourself.

Read the post Migrate WordPress to Astro or Next.js With AI: Step by Step →

· Canvasly Web Studio · Announcements

Coming Soon: Canvasly Client Mode for WordPress, and How It Differs from Bind to WordPress

Coming soon to Canvasly Web Studio: Client Mode for WordPress. It's a WordPress plugin that makes the sites you design in Canvasly client-proof. Your clients get a short, branded admin and change their text, photos and prices right on the page, while your design stays locked. The first question we hear is: "Doesn't Bind to WordPress already do that?" Not quite. They solve two different problems, and they work best together. Here is the difference.

Read the post Coming Soon: Canvasly Client Mode for WordPress, and How It Differs from Bind to WordPress →

· Canvasly Web Studio · AI

When the MCP Server Says "Done" Too Early: Preventing Duplicate Writes from AI Agents in WordPress

AI agents don't get tired, and they don't hesitate. That's what makes them useful, and it's also what makes them dangerous when a tool gives them the wrong signal. Ask an agent to create a post, give it a stale answer when it checks its work, and it will happily create the post again, as many times as it takes to "fix" a problem that never existed. This article started as a discussion on X about WordPress and the Model Context Protocol (MCP). It turned into a good, practical lesson about building tools that AI agents can safely retry.

Read the post When the MCP Server Says "Done" Too Early: Preventing Duplicate Writes from AI Agents in WordPress →

· Canvasly Web Studio · Development

How to Set Up a Local Database, Step by Step (PostgreSQL and MariaDB with Docker)

In our Local development setup guide we said every layer of your environment should be written down, so a new machine needs one command. This tutorial does exactly that for the layer that causes the most trouble: the database. By the end you'll have a PostgreSQL database that starts in seconds, is reachable only from your own computer, comes with realistic test data, and can be backed up, restored or wiped clean with a single command. A MariaDB + WordPress version follows, for headless WordPress work.

Read the post How to Set Up a Local Database, Step by Step (PostgreSQL and MariaDB with Docker) →

· Canvasly Web Studio · Strategy

SaaS Vendor Lock-in & Data Ownership: How to Build Digital Products Without Getting Trapped in Closed Proprietary Ecosystems

Nobody signs up for lock-in. You sign up for a tool that saves you a week of work. Then you add your content, your customers, your design, your automations and your domain settings. A year later the price doubles, a feature you rely on disappears, or the company is acquired, and you discover that leaving would mean rebuilding everything. That is vendor lock-in: not a contract clause, but the cost of leaving, which quietly grows every month you stay. This guide explains where lock-in comes from, what it really costs, and how to build websites and digital products that use great services without being owned by them.

Read the post SaaS Vendor Lock-in & Data Ownership: How to Build Digital Products Without Getting Trapped in Closed Proprietary Ecosystems →

· Canvasly Web Studio · Architecture

Headless CMS vs. Monolithic CMS: Choosing the Right Architecture for Performance, Scalability and Long-Term Maintenance

Every website runs on an architecture, whether you chose it or not. For most of the web's history, that meant a monolithic CMS: one system that stores your content, lets your team edit it, and builds the pages visitors see. A headless CMS splits those jobs apart: the CMS only manages content, and a separate front end turns it into a fast website. Neither is "better" in general. This guide helps you choose the right one for your site, and plan for the years after launch.

Read the post Headless CMS vs. Monolithic CMS: Choosing the Right Architecture for Performance, Scalability and Long-Term Maintenance →

· Canvasly Web Studio · Development

Local Development Setup Guide: Portable, Fast and Isolated Environments

"It works on my machine" is the most expensive sentence in software. It means a bug that only shows up for one person, a new developer who loses their first week to setup, or a release that breaks because production runs a different version than your laptop. A good local development environment fixes all three. It's portable (it runs the same on every machine), fast (it doesn't slow you down), and isolated (projects don't interfere with each other or with your computer). Here's how to build one.

Read the post Local Development Setup Guide: Portable, Fast and Isolated Environments →

· Canvasly Web Studio · Performance

Database Performance Tuning 101: How to Identify, Isolate and Fix Slow or Duplicate SQL Queries in Production

Most slow websites aren't slow because the server is too small. They're slow because a handful of database queries do far more work than they need to, or run far more often than they should. This guide walks through a simple, repeatable loop for finding those queries in production, understanding why they're slow, fixing them safely, and proving the fix worked. Examples cover MySQL / MariaDB (which WordPress uses) and PostgreSQL.

Read the post Database Performance Tuning 101: How to Identify, Isolate and Fix Slow or Duplicate SQL Queries in Production →