- Why Astro and not WordPress?
- Static beats dynamic for security maths: no PHP runtime to exploit, no database to dump, no plugin CVEs to track, no admin panel to brute-force. The site you're reading right now is built this way. WordPress has its place, but for a brochure or marketing site it's an unnecessary attack surface — and it's the #1 source of failed security scans we see.
- Can I update the content myself, or do I need to call you for every typo?
- Both options. The brochure tier gives you Markdown files anyone can edit (think: a Word doc with simple formatting); changes go live by pushing to a git repo, which we can teach a non-technical user in 20 minutes. The CMS-integrated tier adds a web admin UI (Decap CMS or similar) for editing pages and blog posts in your browser without touching code.
- What about SEO? Won't a static site rank worse than WordPress?
- Other way around — static sites typically rank better. They load faster (Core Web Vitals), have cleaner HTML, and don't drag the bloat that WordPress themes and plugins add. We bake in JSON-LD structured data, sitemaps, security.txt, robots.txt, and llms.txt by default. Migrations from WordPress almost always see ranking improvements once redirects are mapped.
- Can you do e-commerce?
- Hosted Stripe Checkout works well for simple product catalogues — we integrate it with the static site. Full Shopify/WooCommerce stores aren't in scope for this service; that's a different engagement. If you need 'a contact form, a few products, and Stripe at checkout', we've got you covered.
- What's included in 'security-first by default'?
- Strict CSP (with nonces, no unsafe-inline), HSTS preload, MTA-STS, DMARC enforcement, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, CORP/COOP/COEP where appropriate, sensitive-path blocking at the edge, no admin panels exposed, no PHP runtime. Day-one A grade on the standard security scans.
- How does migration from WordPress work?
- We extract content (pages, blog posts, images) into Markdown, rebuild the site in Astro, and map every old URL to the new one — including 410 (Gone) responses for dead pages so search engines drop them quickly instead of treating them as 404 noise. Your old WordPress server stays up during the build; we cut over once you sign off on the new site.
- Where does it get hosted?
- Your existing infrastructure usually works fine — static HTML runs anywhere with a web server. We typically recommend nginx behind Cloudflare with strict CSP, but it's flexible. If you don't have hosting, we set it up as part of the build (usually a VPS or a static-hosting platform like Netlify/Cloudflare Pages).