tag
ai
8 entries.
-
The Paragraph You Clicked Is Not in the File
Click-to-edit is easy to build and hard to make safe. Here is the rule that decides which paragraph a click means, and why the editor sometimes refuses to guess.
-
Your AI Agent Shouldn't Read 5,000 Tokens to Change One CSS Value
Giving an agent access to your project is half the problem. If changing one CSS value means rewriting a whole file, its context goes on learning nothing.
-
Your MCP Server Can Edit Your Website. Who Is Allowed to Talk to It?
An MCP server that edits templates and opens pull requests is not just another dev endpoint. The moment it listens on HTTP, authentication is not optional.
-
AI in Your Content, at Build Time — Not in the Browser
Ask an AI a question from inside a Markdown file and bake the answer into the page — once, at build time, cached. No key in the browser, no spinner.
-
Tell the Designer What You Want: the ssg mcp Development Server
ssg mcp turns your AI assistant into two coworkers: a designer that edits templates and a content manager for Markdown. Each knows what it may not touch.
-
SSG 1.8.16: Content That Thinks, Announces Itself, and Links Itself
1.8.16 is about the edges of publishing: build-time AI answers, announcements that never double-post, related articles, and an MCP development server.
-
How to Use the [ai …] Shortcode: A Practical Walkthrough
Step by step: configure a model, keep the key out of your repo, drop your first [ai …] into a post, and commit the cache so CI needs no key at all.
-
Legible to Machines: What Landed in SSG 1.8.14
1.8.14 is about the readers you never see: social scrapers, AI agents and your own tooling. Structured data, social images that work, build-time contracts.