Migrate from WordPress to Astro in Ghent
Many businesses in Ghent run WordPress but face performance ceilings, security overhead, and rising hosting costs. Astro solves these with static HTML output, zero JavaScript by default, and edge deployment. I migrate existing WordPress sites to Astro with full SEO preservation, URL mapping, and 301 redirects.
- PageSpeed 95-100
Static HTML with zero JavaScript. Faster than any WordPress solution.
- SEO-safe migration
URL mapping, 301 redirects, Google rankings preserved.
- Cloudflare Pages hosting
Global CDN, free SSL, instant deployments. Hosting costs near zero.
Ghent has grown into Flanders' premier technology and life-sciences engine, anchored by *Tech Lane Ghent Science Park* and the *VIB (Flanders Institute for Biotechnology)* campus in *Zwijnaarde*, the *Wintercircus* startup and scale-up hub in the city center, *UGent* and *imec* research spin-offs, and the cross-border industrial logistics corridor of *North Sea Port* (Ghent, Terneuzen, Vlissingen). Companies across these clusters build sophisticated digital products, yet their public web platforms, multi-language documentation portals, and B2B commerce catalogs often suffer from heavy client-side JavaScript bundles that degrade Core Web Vitals and complicate Belgian multilingual SEO. I am Mariusz Szatkowski, an independent software developer based in Gdynia, Poland. Working 100% remotely and asynchronously in writing, I engineer Astro 5 web architectures for Ghent organizations that demand static HTML speed, deterministic trilingual routing, and strict Belgian statutory compliance.
Why Ghent’s Biotech, SaaS, and Industrial Ecosystems Adopt Astro 5
Engineering teams in Ghent rarely need convincing about modern web standards, many already run React, Next.js, Vue/Nuxt, or SvelteKit inside their authenticated SaaS dashboards. However, using a stateful Single Page Application framework for public marketing routes, documentation, investor relations, or headless e-commerce introduces unnecessary complexity and runtime cost:
- SaaS Scale-ups and Digital Product Ventures (Wintercircus, Dok Noord, Zuiderpoort): Marketing, pricing, changelog, and documentation pages need instant Time to First Byte (TTFB) and zero main-thread blocking so paid acquisition and organic search traffic convert without hydration lag. Astro 5 lets your frontend team keep writing interactive calculators or product tours in React, Vue, or Svelte while compiling the surrounding 95% of the page into pure zero-JS HTML.
- Biotech, MedTech, and AgTech Spin-offs (Tech Lane Ghent Science Park in Zwijnaarde, UZ Gent campus): Life-sciences companies publish clinical pipeline visualizers, scientific publication repositories, regulatory disclosures, and investor portals accessed globally. Astro’s Content Layer API enforces strict Zod validation on structured scientific and regulatory metadata at build time.
- Cross-Border Industrial & Maritime Logistics (North Sea Port, Skaldenpark, Oostakker): Industrial suppliers and logistics operators serving Flanders, Wallonia, the Netherlands, France, and Germany require fast, multilingual product catalogs (
nl-BE,fr-BE,en,de) that integrate cleanly with ERP and PIM backends without exposing a monolithic CMS to public traffic.
| Architectural Metric | Monolithic SPA / Heavy Framework | Astro 5 Static + Island Architecture |
|---|---|---|
| Default Client JS Payload | 250 KB, 600 KB hydrated across every route | 0 KB on static content routes; surgical hydration per island |
Core Web Vitals Targets (web.dev) | INP spikes above 200 ms during hydration on mid-tier mobile | Engineered to hit LCP up to 2.5 s, INP up to 200 ms, CLS up to 0.1 |
| Framework Flexibility | Locked into a single UI library across the entire repository | Mix React, Vue, Svelte, or Preact islands inside the same Astro project |
Belgian Multilingual SEO (nl-BE / fr-BE / en) | Runtime locale detection often causes redirect chains and crawl waste | Deterministic static route trees with build-time hreflang verification |
| Documentation & Knowledge Bases | Custom MDX plumbing with heavy client-side search bundles | Astro Starlight + Pagefind static WASM search with minimal footprint |
Astro 5 Engineering for Belgian Multilingual Routing and Headless Systems
When I architect an Astro 5 platform for a Ghent company, I focus on three technical pillars: deterministic i18n routing for the Belgian and European market, zero-waste island hydration, and typed backend integrations.
1. Deterministic Trilingual Routing (nl-BE, fr-BE, en) Without Redirect Chains
In Belgium, serving the wrong language variant or relying on Accept-Language cookie redirects confuses both users and search engine crawlers. I configure Astro’s native i18n router alongside a shared translation-key registry in src/content.config.ts:
// astro.config.mjs (excerpt)
import { defineConfig } from 'astro/config';
export default defineConfig({
site: 'https://example.be',
i18n: {
defaultLocale: 'nl',
locales: [
{ path: 'nl', codes: ['nl-BE', 'nl'] },
{ path: 'fr', codes: ['fr-BE', 'fr'] },
{ path: 'en', codes: ['en'] },
],
routing: {
prefixDefaultLocale: true,
redirectToDefaultLocale: false,
},
},
});Every page in Dutch (/nl/...), French (/fr/...), and English (/en/...) is linked via a shared translationKey in the Content Layer schema. At build time, a custom verification script checks that every localized slug has reciprocal <link rel="alternate" hreflang="..." /> tags (nl-BE, fr-BE, en, and x-default) and that the language switcher links directly to the exact translated counterpart rather than dropping the visitor back to the homepage.
2. Multi-Framework Astro Islands and Server Islands (server:defer)
If your Ghent engineering team already maintains a design system in React, Vue 3, or Svelte 5, we do not rewrite those interactive components from scratch:
client:visible&client:idleIslands: ROI calculators for SaaS pricing pages, interactive molecular/clinical pipeline charts for Zwijnaarde biotech portals, or B2B technical configurators hydrate only when needed.server:deferServer Islands: Personalized account status badges, live regional B2B inventory from a North Sea Port warehouse, or dynamic seat availability for events render on the server and stream into the cached static HTML shell.- Astro Actions (
astro:actions): Type-safe server endpoints handle B2B quote requests, clinical partner inquiries, and checkout initiation with Mollie, Stripe, Bancontact, Payconiq, and KBC/CBC payment buttons, forwarding structured data to Odoo (widely used across Belgium), Teamleader Focus (founded right in Ghent at Dok Noord), HubSpot, or SAP.
3. Headless CMS & Starlight Documentation Pipelines
Whether your content editors prefer Storyblok (with visual live preview wired to Astro SSR preview routes), Sanity, Payload CMS, Directus, or headless WordPress, Astro’s Content Layer API unifies all sources into a single typed data graph. For developer-facing products and hardware/biotech documentation, I deploy Astro Starlight customized to your brand tokens with instant static search via Pagefind.
Belgian Statutory Law, GBA/APD Privacy, and KBO/BCE Compliance
Websites operated by companies headquartered in Ghent (East Flanders / Oost-Vlaanderen) must comply with Belgian federal and Flemish regulatory frameworks. I implement these requirements directly in code.
1. Gegevensbeschermingsautoriteit (GBA) / Autorité de protection des données (APD) & Cookie Law
Under the Belgian Data Protection Act of 30 July 2018 (Wet betreffende de bescherming van natuurlijke personen met betrekking tot de verwerking van persoonsgegevens) and Article 129 of the Law of 13 June 2005 on Electronic Communications (Wet betreffende de elektronische communicatie), actively enforced by the Belgian GBA/APD:
- Strict opt-in before non-essential storage: Analytics, marketing pixels, and third-party embeds are blocked at the template level until the user grants affirmative, granular consent. Astro’s zero-JS static output ensures zero covert script execution on initial load.
- No pre-ticked boxes & equal refusal: The consent island provides first-layer accept and reject buttons of identical visual weight, clear categorization of strictly necessary vs. analytical/marketing cookies, and a persistent footer link to withdraw consent as easily as it was given.
2. Mandatory Corporate Disclosures (Wetboek van economisch recht, WER, Book XII, Art. XII.6)
Under Book XII (Recht van de elektronische economie, Article XII.6) and Book III of the Belgian Code of Economic Law (Wetboek van economisch recht, WER), every Belgian commercial website must provide permanent, direct, and easily accessible corporate identification. I structure the global Astro footer and legal templates to include:
- Full corporate name and legal form (BV, NV, CV, or VZW under the Belgian Wetboek van vennootschappen en verenigingen, WVV).
- Geographical address of the registered office (Maatschappelijke zetel in Gent, Zwijnaarde, Merelbeke, Destelbergen, or Evergem).
- The 10-digit KBO / BCE enterprise number (Kruispuntbank van Ondernemingen / Banque-Carrefour des Entreprises, formatted
0XXX.XXX.XXXor1XXX.XXX.XXX) and VAT identifier (BTW BE 0XXX.XXX.XXX). - The competent Legal Entities Register court: RPR Gent (Rechtspersonenregister Ondernemingsrechtbank Gent, afdeling Gent), alongside direct contact email and regulated profession supervisory details where applicable.
3. Belgian European Accessibility Act (EAA) Implementation (WCAG 2.1 AA / EN 301 549)
Belgium’s transposition of Directive (EU) 2019/882 requires consumer-facing e-commerce, SaaS, ticketing, and financial/banking interfaces to conform to EN 301 549 (WCAG 2.1 Level AA). Every Astro build I deliver passes automated axe-core checks and manual keyboard/screen-reader verification: semantic HTML landmarks, programmatic form labels in Dutch, French, and English, focus management across Astro <ClientRouter /> View Transitions, and respect for prefers-reduced-motion: reduce.
Direct, Asynchronous Written Collaboration from Gdynia
From my desk in Gdynia, Poland, I partner with East Flanders engineering and life-sciences teams as a solo software developer. When we collaborate, you deal directly with the engineer writing, testing, and deploying your Astro codebase:
- 100% written, asynchronous communication: I do not conduct phone calls, Zoom/Teams video calls, or live meetings. All technical specifications, architecture diagrams, code reviews, and status updates are exchanged in clear written English via GitHub, Linear, Jira, or email. For every Ghent pull request or architectural question, I reply in writing on working days.
- Design handoff: Your internal product designers or external Ghent creative studio supply the Figma files. I translate those designs into clean, responsive Astro 5 components without adding agency bloat.
- CI/CD & Testing: Every repository includes automated TypeScript (
astro check), Vitest, broken-link, andhreflangparity checks ready for Cloudflare Pages, Vercel, Netlify, or European cloud hosting.
Architectural Blueprint: Trilingual Astro 5 Delivery for Ghent SaaS, Biotech & Industry
When a SaaS scale-up at Wintercircus, a life-sciences spin-off at Tech Lane Ghent Science Park in Zwijnaarde, or an industrial supplier in North Sea Port adopts Astro 5, I execute the build across four structured engineering stages:
| Engineering Stage | Technical Implementation | Verification Gate |
|---|---|---|
1. Trilingual Content Layer (nl-BE, fr-BE, en) | Define unified Zod schemas in src/content.config.ts linking Dutch, French, and English routes via a mandatory translationKey and connecting to Storyblok, Sanity, Payload, or headless WordPress. | Build-time script verifies 100% hreflang reciprocity and zero orphan translations. |
| 2. Multi-Framework Island Isolation | Keep 95% of marketing, documentation, and catalog markup as 0 KB static HTML while mounting existing React, Vue 3, or Svelte 5 interactive components with client:visible or client:idle. | Core Web Vitals meet LCP up to 2.5 s, INP up to 200 ms, and CLS up to 0.1. |
| 3. Server Islands & Belgian Commerce / CRM | Configure server:defer slots for live regional B2B inventory and wire Astro Actions to Mollie (Bancontact, KBC/CBC, Belfius), Stripe, Teamleader Focus, Odoo, or HubSpot. | Type-safe server validation of Belgian enterprise numbers (0XXX.XXX.XXX / 1XXX.XXX.XXX). |
| 4. Belgian Statutory & Accessibility Gates | Enforce GBA/APD and Art. 129 Electronic Communications Law cookie opt-in, Wetboek van economisch recht Book XII Art. XII.6 (KBO/BCE & RPR Gent) disclosures, and EN 301 549 / WCAG 2.1 AA accessibility. | Automated axe-core check + zero pre-consent third-party requests on initial load. |
Why Ghent Engineering Teams Decouple Public Web Properties from Their SaaS Monolith
In many Ghent product companies around Dok Noord, Wintercircus, and Zuiderpoort, the public website originally lived inside the same Next.js, Nuxt, or Angular repository as the authenticated web application. Over time, that coupling creates two problems:
- Shared bundle bloat and deployment friction: Every dependency added for the complex back-office dashboard (charting libraries, state managers, heavy authentication SDKs) leaks into or slows down the build of the public landing pages, while marketing or documentation edits require a full application release cycle.
- Suboptimal Core Web Vitals on acquisition pages: Paid search and organic visitors landing on
/nl/prijzenor/fr/solutionspay the hydration cost of an application shell they haven’t logged into yet.
By extracting the public marketing site, changelog, and Astro Starlight documentation into a dedicated Astro 5 repository (hosted on the root domain or routed cleanly at the CDN edge via Cloudflare Workers or Vercel rewrites), your product engineers stay focused on the core SaaS application while your public web presence achieves instant static load speeds and independent, type-checked publishing.
Start Your Ghent Astro Project in Writing
If your team at Wintercircus, Tech Lane Ghent Science Park, North Sea Port, or anywhere in East Flanders needs a fast, compliant Astro 5 platform, trilingual site architecture, or headless CMS migration, send your technical brief and Figma links via the contact form. I will review your scope and reply in writing on working days.
Selected projects
Examples of my work.
Healthcare Website: fermentum-mobile.pl
The website fermentum-mobile.pl is a dedicated platform created for fermentation enthusiasts who wish to explore traditional processing methods and discover ...
High Quality Artificial Plants - sztuczne-rosliny.pl E-commerce Platform
The sztuczne-rosliny.pl website is a modern e-commerce platform for a company specializing in the import and distribution of high-quality artificial plants in Poland.
Innoopract.com - Developer Tools and Services Platform
Innoopract is a company specializing in software and services, supporting developers and corporations in maximizing returns on investment in developer tools and platforms.
WordPress support & development in Ghent
Need this service: Astro developer in Ghent?
Describe your project by e-mail. I reply within 48 hours.
Describe your projectExplore other WordPress services and knowledge base
WCAG 2.2, BFSG, EAA conformance report and remediation backlog.
CrUX field-data audit with per-template LCP, INP, CLS attribution.
Custom WordPress engineering and architecture.
Clearer structure, messaging, and conversion flow.
Core Web Vitals, caching, and faster delivery.
NIS2 and DORA scope mapping, supplier register, incident runbook.
Related categories
Supporting articles

Germany's Barrierefreiheitsstärkungsgesetz applied from 28 June 2025. It transposes EAA Directive 2019/882 into national law. I unpack how it affects WooCommerce stores in DE and the four plugin failure patterns I see in audits.

WCAG 2.2 was first published as a W3C Recommendation on 2023-10-05; the current published version on www.w3.org/TR/WCAG22/ is dated 2024-12-12. The EU Accessibility Act (Directive 2019/882) applies from 2025-06-28. Germany's Barrierefreiheitsstärkungsgesetz transposes it into federal law on the same date. This article is the implementation map for a WordPress site in 2026.

BFSG and the EU Accessibility Act require a published accessibility statement with a working complaint mechanism, not just a compliant front end. This is a copy-ready template structure mapped to EN 301 549 clauses and WordPress deliverables.