# Astro Sites That Ship Less. Astro Development at Workflow Apps. We build content sites in Astro and run them on Cloudflare: fast pages with almost no JavaScript, content in version control, and migrations off WordPress that keep every URL working. [Start a Project](/start/?interest=ai-accelerated-development) ## Why Astro. **HTML First.** Astro renders pages to plain HTML at build time and sends JavaScript only for the parts that need it. Content sites load fast by default, and there's no client-side framework to update, patch, or debug on pages that are mostly text. **Nothing to Patch.** A static site has no database, admin login, or plugins exposed to the internet. That removes the update cycle and most of the attack surface that comes with a traditional CMS, and hosting on Cloudflare costs little to run. **How We Build It.** Content lives in typed collections with schema validation, so a missing field fails the build instead of breaking a page. Images are optimized at build time, fonts are self-hosted, and checks for titles, descriptions, and structured data run before anything deploys. This site is built the same way. ## What We Build With Astro. ### WordPress to Astro Migrations Move a WordPress or Elementor site to Astro without losing content, URLs, or search history. We export the content from WordPress, convert page-builder HTML into clean Markdown, and rebuild the templates as Astro components. Every existing URL either keeps its path or gets a permanent redirect, so links and search rankings carry over. - Content export and HTML to Markdown conversion - URL inventory with redirect mapping for every changed path - Elementor and page-builder layouts rebuilt as components ### Content-Driven Sites Sites built around articles, service pages, and resources, managed as typed content collections. Each content type gets a schema, so authors get validation and the site gets consistent structure. Posts can be scheduled with a future date and publish on the next build, and MDX lets authors drop components into long-form content. - Typed content collections with MDX - Scheduled publishing and draft handling at build time - Reusable components authors can use inside content ### Cloudflare Edge Deployment Static pages served from Cloudflare's network, with server code at the edge where it's needed. Most pages are prebuilt and cached globally. Forms, redirects, and small dynamic features run in Cloudflare Workers next to them, so you get server behavior without running a server. - Static and edge rendering on Cloudflare Workers - Deploys from GitHub on every merge - Redirects and headers managed in the codebase ### Forms & Edge Functions Working forms and small back-end features without a separate server or a plugin. Form submissions are verified with Cloudflare Turnstile, stored in a D1 database, and delivered by email through a transactional provider such as Elastic Email. Spam is filtered before it reaches your inbox, and every submission has a record. - Turnstile bot protection on every form - Submissions stored in Cloudflare D1 - Transactional email delivery with Elastic Email ### Structured Data & LLM Discoverability Machine-readable output built into the site: JSON-LD, Markdown mirrors, and llms.txt. Search engines and AI assistants read sites differently than people do. We generate JSON-LD structured data from the same source as the page, publish a Markdown version of each page, and maintain an llms.txt index, all checked at build time. - JSON-LD schema generated from site data - Markdown mirrors of every page plus llms.txt - Build-time checks for titles, descriptions, and schema ## When Astro Is the Right Call **A strong fit when:** - Your site is mostly content: service pages, articles, case studies, and resources - You're on WordPress and tired of plugin updates, security patches, and slow pages - You want content in version control with reviews before anything goes live - You need forms and a few dynamic features but not a full application **Worth a second look when:** - Astro isn't built for highly interactive application interfaces like dashboards or editors. Those belong in React or Next.js - If non-technical staff need to edit pages daily in a visual editor, plan for a headless CMS alongside Astro rather than editing Markdown directly ## What We Pair With Astro - **Framework:** Astro, TypeScript, MDX, Tailwind CSS - **Platform:** Cloudflare Workers, Cloudflare D1, Cloudflare Turnstile, Elastic Email - **Delivery:** GitHub, GitHub Actions, Wrangler ## How an Engagement Runs 1. **Scope (Week 1):** Audit what exists and define what needs to be built. 2. **Architect (Week 2):** Architecture, stack decisions, and a delivery roadmap. 3. **Build (Weeks 3–8):** AI-accelerated development with something to review every week. 4. **Ship & Support (Week 8+):** Deployment, documentation, and handoff. See [the full process](/process/). ## FAQ ### Can you migrate our WordPress site to Astro? Yes. We export your content, convert it to Markdown, rebuild the templates as Astro components, and map every existing URL so it either keeps its path or redirects permanently. Elementor and other page-builder sites are included. ### Will we lose search rankings when we move off WordPress? Not if the URLs are handled. We inventory every indexed URL before the migration and make sure each one resolves on the new site, either at the same path or through a permanent redirect. ### How do we edit content on an Astro site? Content lives in Markdown files in your repository, and changes publish when they're merged. If your team needs a visual editor, Astro works with a headless CMS that feeds the same content collections. ### Can an Astro site have forms? Yes. We run forms on Cloudflare Workers with Turnstile bot protection, store submissions in a D1 database, and deliver them by email, with no form plugin or third-party form service required. ### How long does an Astro build or migration take? Most projects follow our standard process: scoping in week one, architecture in week two, and production builds with something to review every week through weeks three to eight. Migrations are scoped by the number of content types and templates, not just page count. ### Where are you located? Malvern, PA, near Philadelphia. We work with organizations across the U.S., and most engagements run remotely with weekly reviews. ## Have a Site to Move? Tell us what you're running today and what's getting in the way. You'll hear back within one business day with a yes, a scope estimate, or a better question. [Start a Project](/start/?interest=ai-accelerated-development)