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, and layout, starting from a curated design at freedesignmd.com — 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:design-import

I import a design from a Canva site or a freedesignmd system.

Already have a brand somewhere else? Hand me a published Canva site URL or a freedesignmd.com system URL and I'll extract the design tokens — colors, typography, spacing — and apply them to your project. Figma is on the roadmap.

What to expect

• I detect the source platform from the URL
• Colors are extracted and classified by role (primary, accent, background, text, muted)
• Fonts are mapped to performant system stacks
• Layouts are inferred and applied to your existing pages — I never overwrite your content

Prerequisites

A Canva site that's been published, or a freedesignmd system URL. Works on a fresh project or an existing one.

/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 Workers. 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 — and restore from it.

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. If something gets lost or accidentally overwritten, I can also restore your site from any GitHub snapshot.

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
• Restore: I can roll the local project back to a previous backup if you ask

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:export

I bundle your site into a portable archive.

For when you want to self-host, hand the site to a developer, or move providers without me. I produce a zip with the project source, content, images, build output, and a README explaining the structure.

What to expect

• A clean export with no Anglesite-specific dependencies that block portability
• A README in the archive root that explains how to build, deploy, and re-edit the site without me
• Your .site-config stripped of any tokens or secrets before export

Prerequisites

A site that builds. Run /anglesite:check first if you're unsure.

/anglesite:redirects

I manage URL redirects.

Renamed a page? Migrated from another platform with different slugs? Imported a CSV from your old host? I keep an authoritative redirect map and generate a Cloudflare _redirects file at deploy time so old links keep working.

What to expect

• One-off rename: I add a redirect when you rename a page
• Bulk import: paste or point me at a CSV and I'll add them all
• Conflict detection: I flag redirects that would clash with real pages

Prerequisites

None. Works on any Anglesite site.

/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:forms

I build a custom form — RSVP, lead capture, survey, callback request, anything.

If /anglesite:contact is too generic, this is the next step up. Tell me the fields you need and I'll generate the form, the Cloudflare Worker that handles submissions, and the success page. Submissions land in your Keystatic inbox.

What to expect

• I ask what kind of form and what fields it needs
• I scaffold the form, server route, and confirmation page
• Spam protection via Cloudflare Turnstile
• Submissions stored in your project as .mdoc files for review in Keystatic

Prerequisites

A deployed site (forms run through a Cloudflare Worker, like /anglesite:contact).

/anglesite:inbox

I open your form submissions inbox in Keystatic.

Every submission from /anglesite:contact or /anglesite:forms is stored as a content entry in your project. The inbox is just a Keystatic collection — you read, reply, mark resolved, or archive submissions in the same editor you use for blog posts.

What to expect

• I open the editor focused on the submissions collection
• Filter by form type, status, or date
• Mark messages as read, replied, or archived
• Triage history is in git, like the rest of your content

Prerequisites

At least one form set up via /anglesite:contact or /anglesite:forms.

/anglesite:stats

I show your site analytics in plain English.

I fetch traffic data from Cloudflare Web Analytics and zone HTTP logs, and present it as a readable summary — no dashboard to navigate. I distinguish unique visitors, page views, and total requests, and flag bot-inflated numbers so you don't misread the trend.

What you'll see

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

Prerequisites

A deployed site with Cloudflare Web Analytics (enabled automatically). Works on the free Cloudflare plan. 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.

/anglesite:seo

I audit and fix SEO basics.

Meta descriptions, Open Graph tags, canonical URLs, structured data, sitemap, robots.txt, and (when agents are welcome) llms.txt. I report what's missing and offer to fix it.

What I check

• Per-page title and meta description quality
• Schema.org structured data appropriate to your site type
• Open Graph and social card images
• sitemap.xml, robots.txt, and llms.txt generation, gated by AGENTIC_CRAWLERS in .site-config

Prerequisites

None. Works on any Anglesite site.

/anglesite:search

I add an on-site search box.

Powered by Pagefind — a static, client-side search index built at deploy time. No external service, no API key, no data leaves your visitor's browser.

What to expect

• A search box in your header (or wherever you want it)
• A /search page with a full search UI
• Search index built as part of the normal build

Prerequisites

None. Works on any Anglesite site.

/anglesite:newsletter

I set up an email newsletter.

I integrate Buttondown, Mailchimp, or Ghost so blog posts can be sent to subscribers by email. Signup form on your site, no third-party JavaScript, signups flow to your provider via plain HTTPS.

What to expect

• I help you pick a provider based on cost, scale, and values
• I add a signup form to your site
• I set up the integration so future blog posts can be syndicated to email

Prerequisites

An account with a newsletter provider (or willingness to create one).

/anglesite:consent

I add a cookie / privacy consent banner.

Category-based GDPR/CCPA banner with granular per-category opt-in. Only added when your site actually has third-party scripts that need consent — Anglesite's default zero-third-party-JS posture means most sites don't need one at all.

What to expect

• I check whether you have any scripts that legally require consent
• If yes: I add the banner with categories (essential, analytics, marketing, etc.)
• If no: I tell you a banner isn't required and skip the work

Prerequisites

None.

/anglesite:photography

I generate a photography shot list tailored to your business.

Every site needs photos. I produce a structured shot list — what to capture, why each shot matters, where it'll go on the site — so you (or a hired photographer) can plan a session efficiently.

What to expect

• A categorized shot list (hero, services, team, location, atmosphere)
• Composition and lighting hints for each shot
• Suggested shot count and a rough schedule

Prerequisites

A site with at least the basics filled in (business type, services, location).

/anglesite:booking

I embed appointment booking.

Cal.com, Calendly, Square Appointments, or another provider — I add a booking widget that matches your site's style. No third-party scripts when possible (styled link to the provider's hosted page); minimal embed otherwise.

Prerequisites

An account with a booking provider.

/anglesite:add-store

I add a full ecommerce store.

For multi-product catalogs that need a cart, inventory, and checkout flow. I help you choose between Snipcart, Shopify Buy Button, Lemon Squeezy, Paddle, and Polar based on what you sell, where your customers are, and your tax-handling preference. For a single product, use the Stripe/Polar buy button instead — I'll suggest it.

Prerequisites

An account with the store provider you pick (or willingness to create one).

/anglesite:donations

I accept donations.

One-time, recurring, or fundraising-goal donations via Stripe, Liberapay, or GitHub Sponsors. Includes optional 501(c)(3) tax-receipt template for nonprofits and a fundraising goal widget if you're working toward a specific number.

Prerequisites

An account with at least one donation provider.

/anglesite:membership

I add a paywall or membership tier.

Gate posts, pages, or whole sections behind a Polar or Memberful subscription. Free-tier members, paid tiers, and pay-what-you-want all work. Gated content is generated at build time — no client-side guessing about who's logged in.

Prerequisites

An account with a membership provider (Polar or Memberful).

/anglesite:menu

I create or import a restaurant menu.

Keystatic collections for menu sections, items, and modifiers, plus structured data (Schema.org Menu) so search engines and Maps surface dishes correctly. I can also import a menu from a PDF or photo.

Prerequisites

None. Works on any restaurant or food site.

/anglesite:podcast

I set up a podcast — episodes, RSS, and a player.

Apple Podcasts and Spotify-ready RSS feed, an episode collection in Keystatic, an embeddable player on each episode page, and optional per-episode YouTube video embed for podcasts that publish to YouTube too.

Prerequisites

Audio files for at least one episode (uploaded to your project or to a host like Cloudflare R2).

/anglesite:giscus

I add blog comments via GitHub Discussions.

Comments are stored as GitHub Discussions on a repository you control. No tracker, no ads, no separate moderation dashboard — moderate from GitHub. The Giscus loader is added to the CSP allowlist (it's a sanctioned exception to the no-third-party-JS rule) and only loaded on blog post pages.

Prerequisites

A GitHub repository with Discussions enabled. Visitors need a GitHub account to comment.