Documentation

/anglesite:start

I create a new website from scratch.

This is where we begin. I'll walk you through a conversation: what kind of site you need, who it's for, what pages matter, and how it should look. Then I scaffold the project, install tools, set up local HTTPS, and open a live preview.

What to expect

• A few questions about your business or project
• Design choices — colors, typography, layout — or say "design it for me"
• A working site running on your computer within a few minutes
• A .site-config file that records your choices for future sessions

Prerequisites

None. I handle everything, including installing Node.js dependencies and setting up HTTPS certificates.

/anglesite:import

I migrate content from an existing website.

Give me a URL and I detect the platform automatically. I migrate blog posts, pages, and images into your project with redirect mappings so you don't lose search traffic.

Supported platforms

WordPress, Squarespace, Wix, Webflow, GoDaddy, Ghost, Medium, Substack, Blogger, Shopify, Weebly, Tumblr, Micro.blog, WriteFreely, Carrd, and more — 25+ platforms total.

What to expect

• I detect the platform automatically from the URL
• Content converted to Markdoc (my content format)
• Images downloaded and stored locally — no external CDN references
• Redirect mappings for old URLs
• Design tweaks come next — I focus on content accuracy first

Prerequisites

A website URL. I can work in an empty directory — I'll scaffold the project and import in one step. For local SSG projects (Hugo, Jekyll, etc.), use /anglesite:convert instead.

/anglesite:convert

I convert a local static site generator project to Anglesite.

I migrate content from Hugo, Jekyll, Eleventy, Gatsby, Next.js, Nuxt, Docusaurus, VuePress, MkDocs, or Hexo. Posts, pages, and images come over. I preserve your original files.

What to expect

• I detect the SSG automatically from your project files
• Frontmatter mapped to my content schema
• Template syntax stripped, content converted to Markdoc
• Images copied to public/images/
• Original project files left intact alongside the new Anglesite files

Prerequisites

An existing SSG project in the current directory. For hosted websites (WordPress, Squarespace, etc.), use /anglesite:import instead.

/anglesite:deploy

I build, scan, and publish your site to the web.

I build the site, run mandatory security scans (PII, API tokens, third-party scripts, Keystatic admin routes), and deploy to Cloudflare Pages. On first deploy, I also help you create a Cloudflare account and connect your domain.

What to expect

• A build and security scan — if either fails, I block the deployment
• First time: I walk you through account setup and domain configuration (about 5 minutes)
• Subsequent deploys: push to main triggers production, push to draft creates a preview
• A live URL when I'm done

Prerequisites

A Cloudflare account (free). I help you create one if you don't have it.

Security scans

Every deploy is gated by my automated scans. These cannot be bypassed, even if you ask. I check for:

• Customer PII (emails, phone numbers) accidentally left in pages
• API tokens or secrets in the build output
• Third-party scripts (only Cloudflare Web Analytics is allowed)
• Keystatic admin routes (should not be in production)

/anglesite:check

I run a full health audit — or diagnose a specific problem.

If you describe a problem ("my images are broken", "the deploy failed"), I diagnose that first. Otherwise, I run a comprehensive audit covering build health, accessibility, SEO, IndieWeb compliance, and security.

What I check

• Build — TypeScript errors, successful compilation, page metadata
• Accessibility — WCAG AA compliance: color contrast, alt text, heading hierarchy, keyboard navigation
• SEO — Meta descriptions, Open Graph tags, canonical URLs, sitemap
• IndieWeb — Microformats (h-card, h-entry), RSS feed, rel="me" links
• Security — Third-party scripts, CSP headers, exposed secrets

Prerequisites

None. I work on any Anglesite project.

/anglesite:update

I update your site to the latest template and dependencies.

I compare your site against the latest template, apply safe updates (new files, script improvements, dependency bumps), and leave your customizations untouched. I explain everything I changed.

What to expect

• I run a baseline build to verify your site is healthy before changes
• New template files added automatically
• Modified files reviewed carefully — I never overwrite your brand colors, custom pages, or content
• Dependencies updated to tested versions
• A verification build after changes
• A plain-English summary of what I changed and what I left alone

Prerequisites

An existing Anglesite project. First-time updates set up version tracking automatically.

/anglesite:backup

I save your work to GitHub.

I commit all changes with a descriptive message and push to your GitHub repository. I categorize your changes (new blog posts, style updates, config changes) and write a clear commit summary.

What to expect

• If no changes: I tell you everything is already backed up
• If changes exist: a categorized summary and a push to GitHub
• Backup history on request

Prerequisites

A GitHub repository connected to your project. I always push to the draft branch — I never push to main (that's what /anglesite:deploy is for).

/anglesite:domain

I manage DNS records for your domain.

I add, change, or remove DNS records directly — no Cloudflare dashboard needed. Common tasks include email forwarding, Bluesky handle verification, Google site verification, and custom subdomains.

What to expect

• First time: a one-time setup to create a scoped Cloudflare API token (~30 seconds)
• I make DNS changes directly via the Cloudflare API
• I verify that records are working

Prerequisites

A custom domain set up through /anglesite:deploy. If you haven't deployed yet, I'll tell you.

/anglesite:contact

I set up a contact form with spam protection.

I create a /contact page with a working form that forwards messages to your email. I use a Cloudflare Worker as the backend and Cloudflare Turnstile for spam protection. No data is stored — messages are forwarded and discarded.

What to expect

• I ask for your contact email address
• I configure a Turnstile widget for spam protection (invisible to most visitors)
• I deploy a Cloudflare Worker to handle form submissions
• I create a /contact page and /contact/thanks confirmation page
• I update security headers to allow the Turnstile script

Prerequisites

Your site must be deployed at least once (/anglesite:deploy) with a custom domain configured.

/anglesite:stats

I show your site analytics in plain English.

I fetch traffic data from Cloudflare Web Analytics and present it as a readable summary — no dashboard to navigate.

What you'll see

• Total visits for the past 7 days vs. the previous week
• Top pages, traffic sources, and device breakdown
• Busiest day and time patterns
• Actionable suggestions — stale popular pages, content timing, SEO opportunities

Prerequisites

A deployed site with Cloudflare Web Analytics (enabled automatically). First time: a one-time setup to create a scoped API token for analytics access (~1 minute).

Privacy

Cloudflare Web Analytics is cookieless and privacy-respecting. No personal data is collected. It's the only analytics tool I use.