Migrate from WordPress to Astro in Antwerp
Many businesses in Antwerp 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.
Antwerp firms in port logistics, the diamond quarter and the fashion district need public websites that load quickly on mobile networks, read cleanly in Dutch and French, and survive scrutiny from the Gegevensbeschermingsautoriteit (GBA/APD) when marketing pixels or checkout forms collect personal data. I am Mariusz Szatkowski, a sole developer working remotely from Gdynia, Poland, on Central European Time, the same zone Antwerp uses for business hours. I build Astro architectures where each page compiles to static HTML, interactive pieces hydrate as islands, and Belgian consumer law becomes typed template code your team can diff before launch.
Who in Antwerp hires an Astro developer and why
An Astro brief from Antwerp rarely starts with framework religion. It starts with a sector pain point and a regulator or partner who will read the live site.
Freight forwarders, terminal services and suppliers around the Port of Antwerp-Bruges need sailing schedules, tariff tables and safety data sheets that remain reachable when a captain opens a link on a phone with weak signal. The port authority’s English site describes the complex as Europe’s second largest port and a driver of circular economy and energy transition work (Port of Antwerp-Bruges, our port). That scale means traffic spikes after press releases and weather disruptions, which static HTML on a CDN tolerates better than a monolithic CMS executing PHP on every view.
In the diamond quarter around Hoveniersstraat, the Antwerp World Diamond Centre (AWDC) states that it represents more than 1,300 Belgian registered diamond companies, cites about 3,300 jobs in the sector, and publishes a figure of 19.1 billion US dollars in annual import and export (AWDC home page). Trading firms need compliance statements, due-diligence PDFs and contact flows without loading a full client-side application on every catalogue page.
Fashion brands tied to the Royal Academy of Fine Arts Antwerp fashion department and to MoMu (Fashion Museum Antwerp) publish image-heavy seasonal stories. The Academy’s English pages describe an internationally recruited student body, drawing-led design education, and yearly SHOW and EXPO events (Royal Academy fashion department). MoMu programmes public exhibitions such as The Antwerp Six and collection displays at its museum site (MoMu). Their sites need fast galleries, accessible alt text and editorial calendars that marketing can update without breaking Core Web Vitals.
Across these sectors the technical ask repeats: stable multilingual URLs, honest cookie choices, checkout copy that matches Book VI WER, and a repository a Flemish agency or in-house developer can maintain after handover.
How port and logistics sites stay fast under traffic spikes
Logistics marketing pages look simple but fail in predictable ways: embedded trackers in the base layout, PDF links that rot after a redesign, and tariff tables pulled from a slow database on every request.
For an Astro build serving Antwerp maritime clients I usually split content into three layers:
- Operational facts (berth names, UN numbers, cut-off times) live in typed content collections. A missing field stops the build instead of silently publishing an empty cell on a live schedule page.
- Documents (PDF safety sheets, terms PDFs) sit at stable paths in the repository or object storage with redirects logged in plain text, so a partner bookmark from 2022 still resolves after a template refresh.
- Interactive tools (freight calculators, terminal finders) mount as islands with
client:visibleorclient:idleso the surrounding document stays zero-JavaScript HTML (Astro islands).
When a terminal operator publishes a disruption notice, the workflow is a pull request: reviewer, diff, deploy. That matches how communications teams already work with compliance officers who want proof of what was public on a given date.
Performance targets follow the thresholds Google documents on web.dev Core Web Vitals: Largest Contentful Paint up to 2.5 seconds, Interaction to Next Paint up to 200 milliseconds, and Cumulative Layout Shift up to 0.1 on mobile profiles. Astro’s static output helps on LCP and CLS for document-heavy logistics pages; islands stay small so INP does not spike on mid-range Android devices forwarders actually carry.
What diamond and luxury B2B sites need from public HTML
AWDC emphasises compliance, ethics and transparency as part of Antwerp’s diamond heritage, and invites companies to contact the centre at Hoveniersstraat 22 (AWDC). Public sites in that cluster rarely run full e-commerce; they run trust-building routes: KYC explainers, event listings, membership forms and document libraries.
Astro fits that pattern when:
- Case studies and policy pages ship as static HTML with no third-party scripts in the layout.
- A gated download form is an island that posts to your CRM with fields listed in a privacy notice the GBA can compare to reality.
- Multilingual routes keep Dutch primary for Flemish visitors and add French or English where AWDC’s own communications do.
I do not invent client logos, audit scores or kimberley-process outcomes. Your compliance officer supplies statements; I structure them in components with revision history in Git.
How fashion brands in Antwerp publish shows and lookbooks
The Academy fashion department lists Nationalestraat 28 and Mutsaardstraat 31 as Antwerp addresses and describes drawing, material study and personal supervision as core teaching methods (AP fashion education). MoMu schedules exhibition seasons with fixed opening hours on its English home page (MoMu). Digital teams supporting graduates, alumni labels or museum campaigns face the same constraints: large imagery, strict brand typography, press deadlines before a SHOW, and social traffic that arrives in bursts.
An Astro fashion build typically uses:
- Responsive images with defined width and height to hold CLS under control during lookbook loads.
- A headless CMS or Markdown collections for show notes, so curators edit copy without touching layout code.
- Optional e-commerce islands only on routes that truly sell to consumers, because consumer routes pull in Book VI duties described in the next sections.
Video or 3D embeds load from a consent-gated island when they are not strictly necessary to view the collection, which keeps the first paint lightweight for international press browsing on hotel Wi-Fi during fashion week traffic.
Which language routes Flanders and Brussels buyers expect
Antwerp sits in Flanders, where Dutch dominates daily business, but Belgian consumer sites often need French pages for Walloon buyers and for Brussels bilingual audiences. Astro’s internationalization routing lets you define locales, default language, and folder structure under src/pages/ (Astro i18n guide).
For a typical Antwerp B2C fashion or accessories shop I configure:
nlas defaultLocale with/nl/prefixes when you want visible language in every URL.frsibling routes with shared translation keys in content collections, so a product missing French copy fails CI instead of publishing an empty shelf.enwhen the brand sells to foreign tourists or trade buyers who search in English.
Hreflang is generated at build time from the same key map, which avoids hand-edited <link> tags drifting apart after a relaunch. I do not rely on Accept-Language redirects for primary navigation; they confuse crawlers and bookmarking behaviour your Antwerp marketing team already tests manually.
What Book VI WER requires on distance selling pages
Consumer distance contracts in Belgium fall under Book VI of the Code of Economic Law (Wetboek van economisch recht). The Federal Public Service Economy summarises the withdrawal rules for purchases made by phone, internet or catalogue under articles VI.47 to VI.53 WER, including a withdrawal period of 14 calendar days and a model withdrawal form consumers may use (Economie, herroepingsrecht bij aankoop op afstand).
In an Astro shop I translate that framework into concrete templates:
- Pre-contract information blocks sit on product and checkout routes with fields your legal team approves, not paraphrased marketing gloss.
- The withdrawal form is a static page and downloadable file linked from the footer and order confirmation email template.
- Order buttons use explicit contractual wording stored as a single string per language, with an automated check on the built HTML so a redesign cannot swap in a vague label.
When the payment step runs in Bancontact, Mollie, Stripe or another hosted flow, Astro still owns the product pages and the summary the buyer sees immediately before authorisation. I document which hosted fields remain your PSP’s responsibility and which sentences must match Book VI on your domain.
Your counsel decides product-specific exceptions (custom jewellery, perishable goods, digital content). The CMS stores exception flags per SKU so templates do not promise a withdrawal right the law excludes for that item.
How the GBA and Article 10/2 govern cookies and scripts
The Gegevensbeschermingsautoriteit states that its mission is to ensure fundamental data protection principles are respected (GBA citizen homepage). For websites that means GDPR accountability plus Belgium’s cookie rule.
Article 10/2 of the Law of 30 July 2018 concerning the protection of natural persons with regard to the processing of personal data allows storage of or access to information on a user’s terminal equipment only when the user receives clear and precise information about processing purposes and rights, and consents after receiving that information. Exemptions cover technical storage strictly necessary to transmit a communication or to provide a service the user expressly requested (Belgian official text, Article 10/2). The rule implements Article 125 of the Electronic Communications Act of 13 June 2005 by reference in that same article.
On an Astro site I apply five build rules Antwerp marketing teams can audit:
- The base layout contains no analytics, advertising or social pixels.
- A consent island loads non-essential scripts only after an affirmative choice, with reject as visible as accept.
- A build step scans generated HTML for known tracker domains outside the island and fails when it finds one.
- Form endpoints list processors in a typed config file mirrored on the privacy page.
- Preference storage uses a first-party cookie whose lifetime your DPO approves; the GBA’s cookie guidance treats six months as a reasonable default for choice cookies in many setups.
Complaints and supervisory contact paths belong on the privacy page with the same wording your legal team uses in offline notices.
Where Bancontact sits in a Belgian checkout architecture
Bancontact presents itself on bancontact.com as the Belgian scheme with consumer, professional and developer sections, including legal and administrative specifications for merchants (Bancontact English site). Most Antwerp retailers expect Bancontact beside international card brands; the public marketing site does not need to host the cryptographic payment flow itself.
Astro renders catalogue, basket summary and statutory information as static or server-island routes. Payment authorisation runs in:
- A redirect to a PSP-hosted Bancontact flow, or
- A small island embedding the provider’s widget, loaded only on the payment step.
I keep product attributes, VAT display rules and withdrawal links on your domain, and pass an order reference to the PSP unchanged. Your finance team validates the reconciliation fields; I validate that the buyer never reaches payment without passing the Book VI information screen on your site.
What the 2023 Belgian accessibility law changes for consumer e-commerce
Directive (EU) 2019/882 on accessibility requirements for products and services is partially transposed by Belgian law of 5 November 2023. Article 2 of that law states it transposes the directive for certain services. Book VIII Title 5 of the Code of Economic Law, inserted by the same law, applies to consumer banking services and consumer e-commerce services, with exceptions for some archive and third-party content (Justel consolidated law 2023-11-05).
The law entered into force on 28 June 2025. Article 40 of the transposition law excludes micro-enterprises employing fewer than ten people with annual turnover or balance sheet total not exceeding 2,000,000 euros from scope until 28 June 2030, except for specific provisions. Complaints about accessibility can be filed with the agents named in Book XV of the Code of Economic Law.
I do not certify legal conformity. I build semantic landmarks, labelled form controls, keyboard-visible focus, and colour contrast that your designer specifies. Where you fall in scope, accessibility information your legal team prepares can live in a static route linked from the footer, matching Book VIII disclosure duties described in the consolidated text.
How an Antwerp Astro project runs from brief to handover
Work stays in writing on Central European Time. Your designer or branding agency supplies layouts; I implement them in Astro with the compliance hooks above.
| Stage | What you receive | What I need from your Antwerp team |
|---|---|---|
| Brief review | A free initial written estimate with scope, assumptions and open questions | Current site URL, languages at launch, sector (port, diamond, fashion, mixed), who owns legal copy |
| Architecture note | Route map for nl, fr, en, content schemas, redirect inventory, third-party script list | Confirmed slugs, CRM and PSP choices, consent categories from your DPO |
| Build | Staging deploys from pull requests and a changelog in Git | Approved designs, product data, show or catalogue content, tagged placeholders where copy is pending |
| Compliance pass | Consent island, tracker scan, withdrawal templates, signup logging | Final privacy notice, withdrawal form text, Book VI checkout strings from counsel |
| Launch | DNS checklist, redirect file, Search Console spot checks, handover README | Named DNS contact, go-live date, recipient developer for repository access |
I do not run workshops, discovery calls or on-site visits in Antwerp. Questions and decisions end up in email or your issue tracker so both sides keep a record.
When is Astro the wrong fit for an Antwerp company?
Astro is the wrong primary tool when most value sits behind a login: a forwarder’s customer portal with live container tracking tied to your TMS, or a diamond trading room with real-time inventory and negotiation state. Those products need an application framework with persistent server logic. Astro still fits the public marketing layer around such systems.
If WordPress already passes Core Web Vitals and editors refuse to leave Gutenberg, migrating to Astro only for fashion blogs may cost more than it saves. In that case I say so in the estimate.
Send an Antwerp project brief
Send the brief through the contact form with your current site URL, sector (port, diamond, fashion or mixed), languages you need at launch, whether you sell to consumers online, and who supplies designs and legal texts. I reply on Central European working days with questions or a written scope.
Selected projects
Examples of my work.
E-commerce Development: pepegotti.com
The pepegotti.com website is a modern platform dedicated to furniture distribution, combining clear design with advanced functionalities tailored for both in...
E-commerce Development: pluginfinance.com
pluginfinance.com is a modern, highly scalable WordPress-based service dedicated to showcasing and distributing financial plugins. The project was designed w...
E-commerce Development: radio.friko.pl
Radio.friko.pl is an internet radio station that operated between 2005 and 2010 as part of the Friko.pl platform, offering users access to music streaming, l...
WordPress support & development in Antwerp
Need this service: Astro developer in Antwerp?
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.