Astro developer - fast websites with island architecture

7 min read
Guide

#Astro developer for content-led websites

I am Mariusz Szatkowski and I have been building websites since 2006. I use Astro when a site is mostly content: a company site, a blog, documentation, a service catalogue. Astro renders components to HTML and CSS by default and ships JavaScript only for the parts that react to the visitor. A search box, a form or a pricing toggle becomes an island. Navigation, headings and body text stay plain HTML.

This site is built the same way: Astro 7, MDX, Tailwind CSS 4, a static build on Cloudflare Pages, six languages. The wppoland.com rebuild case study shows the stack and the rules behind it, and the WordPress to Astro migration report walks through the move itself.

Who: Mariusz Szatkowski (Wikidata), developer since 2006. WPPoland is the name I work under. I work alone: no team, no subcontractors.

What: Astro sites with island architecture, typed content collections, MDX, headless CMS integration, migrations from WordPress and Next.js, static deployment on Cloudflare.

Where: remotely from Gdynia, Poland. Decisions are made by email, in written documents and in the repository.

How much: every project gets an individual written quote with scope, assumptions and timeline, after you send a brief.

You bring the graphic design and wireframes, for example as a Figma file or a filled-in template that says which element goes where on each view. I turn that into Astro components that work on phones and desktops. For React front ends on the App Router, see Next.js development; for integrations and internal tools outside the front end, see software developer.

#What I build in Astro

#New sites

Work starts with a written specification: content types, page templates, URL structure, languages and deployment. Then I build Astro components to your design, content collections with schemas and the deployment pipeline. The code lives in a repository you own.

#Content collections and MDX

I define build-time collections in src/content.config.ts with defineCollection(), a glob() or file() loader from astro/loaders, and a schema built with z from astro/zod. An entry with a missing title or a malformed date stops the build and names the file. MDX comes in through the @astrojs/mdx integration and lets an author drop a component, such as a comparison table, into the middle of an article.

#Islands and client directives

Each island carries a directive that decides when its script loads: client:load, client:idle, client:visible, client:media or client:only. Islands from React, Svelte and Vue can sit on the same page. When I audit an existing Astro site, the first thing I look for is client:load used where client:visible would do.

#Server islands

A component marked server:defer becomes a server island: it renders on demand, separately, while the rest of the page shows straight away. That needs on-demand rendering and an adapter, so I only use it where a page genuinely has per-visitor content.

#Analytics on a static site for UK visitors

A static build does not set cookies by itself. The analytics, chat widgets and embeds you add do, and for UK visitors regulation 6 of the Privacy and Electronic Communications Regulations 2003 applies to any storage of or access to information on their device. Since 5 February 2026 the regulation, as substituted by the Data (Use and Access) Act 2025, points to Schedule A1, which lists the exceptions to the consent requirement.

Paragraph 5 of that schedule covers storage whose sole purpose is collecting statistics about how your own service is used, provided the visitor gets clear information and a free, simple way to object. Anything outside that, such as advertising pixels, still needs consent. In an Astro project I load third-party scripts only after the consent or objection state is known, and I list every script that touches visitor data so you can check it against your privacy notice.

#Migrating from WordPress or Next.js to Astro

A migration should carry over what the current site has earned in search: URLs, backlinks, structured data and indexed content.

  1. Inventory. Every URL, redirect, content type, media file and third-party integration goes on a list that later serves as the acceptance checklist.
  2. Content export. Posts and pages become Markdown or MDX files with frontmatter that matches the collection schema. Images are converted and stored with the content.
  3. Redirect map. Every changed URL gets a 301 redirect at the hosting level.
  4. Structured data. I carry over schema.org markup and fix it, because SEO plugins in WordPress often emit generic markup.
  5. Before and after. I measure the old site and the staging build with the same tool under the same conditions and share both results.
  6. Launch. After your sign-off on staging the domain switches over, and I watch Google Search Console for crawl errors.

Timelines depend on the number of pages, content types and integrations. You get one in the quote after I have looked at the site.

#Which headless CMS fits Astro?

WordPress as the content source. If your team has years of content in WordPress and knows the editor, WordPress can stay. Astro reads it through the built-in REST API under /wp-json/wp/v2/; WPGraphQL is an optional alternative. Editors keep their screen, visitors get static HTML.

Sanity suits new projects with structured content types defined in code. Storyblok fits marketing teams that want to see changes in the page layout while they edit. Contentful fits organisations that need roles and approval steps. Local MDX in the repository is the simplest option when the people writing content also work in Git; this site works that way.

#When I keep WordPress

Astro is not the answer to every brief. WordPress stays when editors publish daily without access to a repository, when a shop runs on WooCommerce, or when a plugin already covers the feature you need. Then I work on it as a WordPress developer. A middle path is WordPress as the content source with an Astro front end, keeping the cart and checkout in WooCommerce.

#Deployment on Cloudflare

A static Astro build is a dist folder of HTML, CSS and assets. It needs no adapter and no PHP server or database. wppoland.com is served this way from Cloudflare Pages.

If some pages must render on demand, the @astrojs/cloudflare adapter is required. According to the Astro docs it no longer supports Cloudflare Pages and deploys to Cloudflare Workers, which Cloudflare recommends for new projects. Every deployment comes from a commit, so you can see what changed in production and roll back to the previous version.

#AI search and plain HTML

Crawlers that do not run JavaScript see an Astro page in full, because the HTML arrives complete in the first response. I add schema.org structured data (Organization, WebSite, Service, Article), consistent entity names and an llms.txt file that indexes the main pages. Whether a given AI assistant cites a page is decided by its provider, so I do not promise citations.

#Maintenance after launch

Astro ships new releases regularly. I update the framework and npm dependencies on staging first and release to production only after the build checks out. A static site has no login screen or database to patch, but DNS, security headers and third-party scripts still need review. I do not offer 24/7 on-call or guaranteed response times.

Send me a description of the site, what should change and your deadline through the contact form. You get a written quote with the assumptions it rests on.

The shorter Astro developer service page summarises the same offer. For a PHP back end behind an Astro front end, see PHP developer.

Explore other WordPress services and knowledge base

Recommendations from LinkedIn

Recommendations and reviews of working with WPPoland

Recommendations from people in the WordPress, WordCamp and e-commerce communities. They write about delivery on time, technical depth and a business-minded approach to site development.

Karolina Czapla

Karolina Czapla

Marketing Strategist, Performance & Digital Strategy

“Working with Mariusz on WordCamp has shown me how rare it is to combine deep technical skill with genuine leadership. He plans, coordinates and delivers with precision, while giving the team space to grow and contribute. When others say 'it can't be done', he quietly finds a way.”

Co‑organiser, WordCamp Gdynia 2024 & 2025

Anna Kamińska

Anna Kamińska

Talent Acquisition Specialist / HR People Partner

“Mariusz's portfolio speaks for itself. It reflects his precision, versatility and sense of responsibility. You can trust him to guide a project from idea to delivery, keep stakeholders informed and make sure things are done properly and on time.”

Worked on the same team

Sarah‑Luisa Kwolek

Sarah‑Luisa Kwolek

IT Project Management & Product Owner, Web/App

“For over two years I could always rely on Mariusz to handle WordPress tasks calmly and professionally, from styling and templating to third‑party integrations. He brings steadiness to the team and keeps the frontend side of projects under control.”

Mariusz was her client for WordPress work

Argert Boja

Argert Boja

Senior Full‑Stack Developer

“Mariusz is the teammate everyone hopes for: strong full‑stack WordPress skills, clear explanations and a positive attitude even under pressure. He moves easily between custom plugins, performance work and Gutenberg layouts while keeping the bigger picture in mind.”

Worked alongside Mariusz on WordPress projects

Varun Patil

Varun Patil

Growth & CRM Lead

“Beyond development, Mariusz understands SEO, analytics and growth. He talks directly with stakeholders, asks the right questions and ships solutions that move business metrics, from AMP to tracking to performance.”

Managed Mariusz on growth initiatives

Rafał Osiński

Rafał Osiński

Founder @ EasyTrips.pl, Senior WordPress Dev

“I've known Mariusz through the WordPress community for many years. He's reliable, deeply involved and consistently shows up, at meetups, WordCamps and in projects. If you care about long‑term collaboration and someone who treats your site like his own, he is the right person.”

WordPress community co‑organiser

Daniel Blossfeld

Daniel Blossfeld

Process Optimization & Digitalization Consultant

“I had the pleasure of working with Mariusz for almost three years. During that time, his WordPress development skills proved invaluable across a range of projects, from website builds to online member areas and even Shopify integrations. He's a reliable and capable developer.”

Mariusz was his client for WordPress work

Natalie Wiszczor

Natalie Wiszczor

CRM & E-Mail Marketing Manager

“I had the great pleasure of working with Mariusz for over 4 years in the technical field. During this time, he proved to be a competent and reliable colleague. What stood out in particular was his friendly nature and his remarkable perseverance in solving complex technical challenges. Even in stressful situations, he always kept a clear head and contributed significantly to a positive and productive working atmosphere with his upbeat attitude. 🙏🏻🚀”

Worked with Mariusz on different teams

Mark Chalklen

Mark Chalklen

Head of Design & Build at Itineris Limited

“Mariusz is a great member of the team, always happy to get stuck into any task and happy to learn new things. A great communicator and all round nice guy to work with. Hard to beat on our weekly Strava leader board though!”

Managed Mariusz directly

Jessica Di Pasquale

Jessica Di Pasquale

Leading SEO initiatives with data-driven growth strategies.

“Mariusz is a very skilled, patient and expert guy. Always ready to help and to fix errors, I really appreciated working with him. He is such a great colleague!”

Managed Mariusz directly

Biki John

Biki John

Content Marketing Aficionado & SEO Enthusiast

“It was great to work with Mariusz. I really appreciated his extensive knowledge of WordPress and how that came in handy whenever I needed support navigating the CMS. I commend Mariusz totally for his patience, good nature and expertise in his craft, he will be thoroughly missed by all.”

Worked with Mariusz on different teams

Rafal Borowiec

Rafal Borowiec

Software Developer, Consultant, Manager and Lecturer

“I had an opportunity to work with Mariusz for 7 months. He excels in technical optimization for search engines (SEO). Mariusz has also strong expertise in AMP development, GTM, and GA. Mariusz feels very comfortable with WordPress - he worked on a variety of WordPress related projects and tasks, including landing pages development, performance improvements and much more. If you are looking for a solid WordPress expert specializing in SEO, tracking, performance, and development - don't hesitate to get in touch with Mariusz.”

Managed Mariusz directly

Belinda Koch

Belinda Koch

Web-Tracking Analyst at TUI

“Mariusz is a great person to work with. He is extremely motivated to learn new things and share his knowledge, and is very knowledgeable on a wide range of topics. We worked together on digital analytics and tracking topics and I am very grateful for all the energy, support, and insights he brought to the projects.”

Worked with Mariusz on digital analytics and tracking topics

Ali Nezamolmaleki

Ali Nezamolmaleki

Growth, SEO, Analytical thinking, AMP

“Mariusz is an extremely talented person in his field of work. He is always capable of giving a new perspective to solve problems and to think out of the box in situations where everything seems to be locked. Working with him is always a pleasure because of his positive personality and can-do attitude.”

Worked with Mariusz on the same team

Karol Jakubcewicz

Karol Jakubcewicz

Front-end / JavaScript Developer

“Mariusz is an incredibly experienced WordPress developer and SEO/SEM specialist I've had the pleasure to work with for almost two years. As a pilot of the team responsible for AirHelp's website development, he's been one the key figures in charge of constant load time and page rank improvement. I admire his skills and knowledge vital for such complex, multilingual and highly customized WordPress project. Lots of experience, tons of positive attitude - I highly recommend cooperating with Mariusz in any web development project.”

Worked with Mariusz on the same team

Paweł Lewczuk

Paweł Lewczuk

Front-end developer, WordPress developer

“I collaborated with Mariusz on several projects and our cooperation was always exemplary. I believe there are many more joint projects ahead of us. Highly recommended!”

Mariusz was Paweł's client

Przemek Wroblewski

Przemek Wroblewski

Software Developer with 20+ years of experience

“I found Mariusz as someone with great expertise and profound knowledge of frontend solutions. Powerful, knowledgeable and accountable WordPress developer. Has an easiness to build interpersonal relations with others. He had vision to see the benefits and the passion to turn that into measurable results for AirHelp. Absolutely someone I'd want to have on my team.”

Worked with Mariusz on different teams

All recommendations on LinkedIn

Frequently asked questions

Questions about scope, delivery, pricing, and execution quality.

Astro developer, what does WPPoland actually ship?#
WPPoland is me, Mariusz Szatkowski. I build Astro sites with island architecture, move sites from WordPress and Next.js to Astro and deploy static builds to Cloudflare. I work alone from Gdynia. WordPress stays where editors need its admin screen. You get a written quote after a short brief.
What is Astro and when should I choose it over WordPress?#
Astro is a web framework that renders components to HTML and CSS by default and ships JavaScript only for interactive islands. It suits company sites, blogs and documentation where content is edited in a repository or a headless CMS. If your editors publish daily in an admin screen, rely on plugins or sell through WooCommerce, I keep WordPress.
Can you migrate my existing WordPress site to Astro?#
Yes. I inventory every URL, export content to Markdown or MDX, map 301 redirects, carry over structured data and compare measurements before and after on staging. How long it takes depends on the number of pages, content types and integrations, so the timeline is in the quote after I have looked at the site. WordPress can also stay as the content source through its REST API.
Do Astro websites work with a CMS for content editing?#
Yes. Content can live in Markdown and MDX files in the repository, in a headless CMS such as Sanity, Storyblok or Contentful, or in WordPress, which Astro reads through the REST API. The choice depends on who edits content and how often.
Is Astro good for SEO?#
Astro sends finished HTML in the first response, so search engines and crawlers that do not run JavaScript see the whole page. Hreflang tags, canonical URLs and structured data still have to be built into the templates. A sitemap comes from the @astrojs/sitemap integration, which you install.
How much does an Astro website cost?#
I quote each project individually, based on the number of templates, integrations and the size of any content migration. Send a description of the site and what should change through the contact form and you get a written quote with its assumptions.
Can Astro handle multilingual websites?#
Yes. Astro's i18n configuration sets the locales, the default locale, URL prefixes and fallbacks, and helpers such as getRelativeLocaleUrl build correct links. Hreflang link tags in the page head are template work; @astrojs/sitemap can add alternate language entries to the sitemap through its i18n option. wppoland.com runs this way in six languages.
What happens with hosting and deployment for Astro sites?#
A static Astro build is a folder of HTML, CSS and assets that can be served from Cloudflare without an adapter. If some pages render on demand, you need the @astrojs/cloudflare adapter, which deploys to Cloudflare Workers because it no longer supports Pages. Each build comes from a commit, so going back to a previous version is straightforward.