Migrate from WordPress to Astro in Lyon
Many businesses in Lyon 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.
I am Mariusz Szatkowski, a solo developer in Gdynia, Poland. I build Astro frontends for companies that sell from Lyon and Métropole de Lyon: chemical and equipment suppliers in the Auvergne-Rhône-Alpes region, software firms around Confluence and Silicon Rhône, and corporate marketing teams in the Part-Dieu business district. Those buyers rarely need another all-in-one page builder. They need static HTML that survives a Monday traffic spike, forms that respect RGPD and CNIL expectations, and code their next hire can read without six weeks of archaeology. Astro matches that shape: compile marketing routes ahead of time, hydrate only the pieces that truly need client state, and keep legal and language structure visible in Git instead of buried in plugin checkboxes.
What Lyon B2B and industrial sites actually need from the frontend
Lyon is not Paris La Défense finance theatre and not a Riviera resort brochure. The metro area mixes Part-Dieu towers, Gerland life sciences, chemical heritage along the Rhône, and logistics corridors toward Switzerland and Germany. Briefs I see from this market repeat a handful of pressures that generic agency copy ignores.
First, calendar risk. A product landing must not break the afternoon your team exhibits at Eurexpo or opens registrations for a congress week in Part-Dieu. Frontend changes therefore need preview URLs, redirect inventories, and rollback paths, not Friday evening SFTP uploads.
Second, language and export reality. An industrial SME in Villeurbanne may need French copy for domestic buyers, English for group HQ, and German for Alsace distributors. Search engines index distinct URLs more reliably than client-side language toggles that rewrite the DOM after load.
Third, compliance visibility. Marketing wants pixels; legal wants proof that non-essential scripts waited for consent. Finance wants Mentions légales that match the SIRET on the invoice. Astro lets me separate those concerns: statutory footer partials, consent islands, and static article bodies that auditors can view without executing JavaScript.
Graphic design stays on your side. I implement approved Figma or existing brand CSS into Tailwind and Astro layouts. Part-Dieu remains France’s second-largest business district after La Défense: towers, Gare de Lyon-Part-Dieu, and congress hotels set the rhythm for when marketing sites must not change without a rollback plan.
Part-Dieu, Confluence, and Gerland: three different Astro profiles
Part-Dieu concentrates banks, insurers, corporate HQs, and conference hotels around Gare de Lyon-Part-Dieu. Astro fits employer-branding microsites, investor fact sheets, gated white-paper requests, and campaign landings that must load on hotel Wi-Fi. Interactive pieces are narrow: job filters, investor contact forms, or calendar embeds behind consent.
Confluence and the riverside innovation belt host Lyon Digital Hub meetups and networks such as Silicon Rhône. SaaS companies here often outgrow marketing WordPress stacks that mix Elementor with a dozen analytics snippets. A typical migration keeps editorial in headless WordPress or a French CMS while Astro serves the public marketing tree with typed content collections and preview deploys per pull request.
Gerland and Lyonbiopôle bring regulatory PDFs, trial enquiry forms, and long compound names in product tables. Accessibility and form minimisation matter as much as Lighthouse scores. Server-rendered HTML for articles plus small islands for validated forms beats a single-page application that ships React to every visitor reading a compliance notice.
Across Auvergne-Rhône-Alpes, industrial digitalisation programmes push suppliers to publish spare-part lookup, distributor maps, and technical sheets online. Astro Actions (see the Astro Actions guide) can validate SIRET-bearing quote requests on the server without exposing ERP endpoints in the browser bundle.
Islands architecture for campaigns without shipping a full framework
The Astro islands concept is the technical answer to Lyon campaign constraints. Marketing HTML stays static. Only the booking widget, ROI calculator, or multi-step demo request mounts with client:visible or client:idle so INP stays inside the band Google describes in its Core Web Vitals article.
| Surface | Static Astro route | Typical island |
|---|---|---|
| Part-Dieu product launch | Hero, specs, FAQ, PDF links | Demo request with Zod validation |
| Confluence SaaS pricing | Plans, comparison table, legal footers | Currency toggle or seat calculator |
| Gerland services catalogue | Department listings, accreditations | Enquiry form with file upload gate |
| Rhône-Alpes distributor map | Regional copy, hreflang pairs | Locator search backed by a small API |
When a page truly behaves like an application (logged-in configurators, real-time inventory), I point buyers to Next.js developer in Lyon instead of forcing Astro into the wrong shape. When the workload is content plus a few honest widgets, Astro wins on weight.
Image and font discipline for industrial catalogues
High-resolution equipment photography destroys mobile LCP if every template pulls uncompressed JPEGs from a shared CDN. I use Astro’s asset pipeline to emit responsive AVIF or WebP variants with explicit dimensions, and I self-host subsetted WOFF2 fonts so visitor IP addresses are not sent to US font CDNs on first paint, a point CNIL discussions on trackers repeatedly raise for French-facing sites.
CNIL, RGPD, and LCEN: what I implement in templates
French law treats the marketing site as part of your compliance story, not an exception to it. Your data protection officer owns policy text; I align delivery mechanics with public CNIL guidance.
Cookies and trackers (Article 82 and CNIL deliberations)
The CNIL cookies and trackers section explains that non-essential cookies require informed consent and that refusing must be as simple as accepting. Deliberation 2020-091 is the reference marketing teams quote in RFP annexes.
On Astro builds for Lyon clients I therefore:
- Ship first paint without marketing tags in the base layout.
- Mount consent UI as an island that records choice before loading analytics or remarketing.
- Keep exempt analytics (only if your DPO approves a CNIL-exempt configuration) in a separate code path with documentation in the repo README for auditors.
- Block embedding third-party widgets that inject trackers until consent categories allow them.
RGPD (GDPR) forms and data minimisation
Quote forms for industrial clients often ask for company name, role, SIRET, and project description. I map each field to a stated purpose in the form copy, avoid hidden fields that collect data without visibility, and post submissions through server handlers so browser devtools do not reveal internal API keys. Retention and subprocessors remain your privacy notice content; the frontend must not contradict it.
Mentions légales under LCEN Article 6
Every commercial French website needs permanently accessible legal mentions: identity, registration, VAT, publication director, host. I store them in a typed legalConfig object consumed by layout partials so a new campaign page cannot forget the footer. RCS Lyon registration lines differ from Paris; your registry extract is the source of truth.
Accessibility: RGAA expectations in B2B RFPs
Public-sector inspired buyers and large Part-Dieu vendors increasingly attach RGAA or WCAG 2.2 AA criteria. Semantic landmarks, visible focus states, labelled form controls, and colour contrast in the design tokens I implement from your Figma are baseline deliverables, not stretch goals.
Multilingual FR, EN, and DE without plugin fragility
Exporting from Lyon often means parallel routes rather than one URL that guesses language from the browser. Astro’s i18n configuration generates locale prefixes at build time. I pair it with content collections keyed by a shared translation id so CI fails when German datasheet B exists but French datasheet A does not.
Practical rules I enforce in repositories:
- Reciprocal
hreflanglink tags on every indexable template. - Human slugs per locale (
/fr/produits/vs/de/produkte/) when SEO teams require them. - Legal snippets duplicated per language, not machine-translated footers.
- Sitemaps listing each locale explicitly.
Editors may keep WordPress for blogging while Astro serves the public site via REST or GraphQL at build time. That pattern appears often when Confluence startups want Git review on the frontend but not on editorial habits.
Delivery from Gdynia: written milestones your Lyon PM can forward
I do not fly to Lyon-Part-Dieu for kickoff workshops. Collaboration is asynchronous and traceable, which suits distributed marketing and legal reviewers who already live in email threads and Jira.
| Phase | You receive | I need from you |
|---|---|---|
| Intake | Restated goals, risk list, locale map | URL export, languages, campaign freeze dates |
| Architecture | Collection schemas, redirect table draft | Mentions légales fields, cookie taxonomy |
| Build sprints | Staging URL per milestone, PR links | Copy in each live language or marked placeholders |
| Compliance pass | Consent gating demo, footer diff | Final privacy and cookie texts from counsel |
| Launch | DNS checklist, 301 file, Search Console notes | Go-live owner and rollback approver |
Staging stays available across revisions so a Part-Dieu product manager can forward a link to compliance without scheduling a screen share. Acceptance is checklist-driven: vitals spot-check on templates that matter, forms delivering to the inbox or CRM you name, translations reciprocal, statutory blocks present.
Typical Astro engagements I take for Lyon
Greenfield marketing site with FR and EN collections, consent island, and Cloudflare Pages deploy from GitHub.
WordPress or Webflow migration preserving URL equity: inventory, 301 map, structured data parity, before-and-after Lighthouse capture on the same throttled profile.
Headless split where WordPress or Storyblok remains editorial and Astro remains public, common for Confluence SaaS firms.
Performance rescue on an existing Astro repo: bundle analysis, image pipeline fix, font self-hosting, third-party script diet.
Industrial catalogue refresh with PDF download gates, distributor locator island, and FR/DE hreflang for Rhône-Alpes exporters.
WooCommerce checkout, payment orchestration, and long-term WordPress maintenance are separate scopes linked below. I do not bundle them silently into an Astro marketing quote.
Checklist before you sign with any Astro supplier in Lyon
Even if you never hire me, this list prevents rework common in Auvergne-Rhône-Alpes RFPs:
- Name the launch languages and which pages are statutory on day one.
- Freeze URL patterns before authors start writing in Notion.
- Decide consent categories before marketing pastes a tag manager snippet.
- Collect Mentions légales fields from finance, not from a generic template.
- Require staging that legal can open without a VPN trick.
- Measure Core Web Vitals on 4G, not only on office fibre.
- Document campaign freeze weeks around Part-Dieu congresses and Eurexpo.
Related services in Lyon
Depending on where you sit in the stack, these pages may be a better starting point:
- WordPress developer in Lyon when editorial must stay inside WordPress for now.
- Next.js developer in Lyon when the product is closer to a logged-in application than to a multilingual brochure.
- Next.js to Astro migration in Lyon when you want to shrink client bundles but keep component investments.
- WooCommerce developer in Lyon when checkout and French payment plugins are in scope.
- PHP developer in Lyon when Laravel or Symfony powers APIs behind the Astro front.
Start with a written brief
If you need an Astro site for Part-Dieu campaigns, Confluence SaaS marketing, Gerland compliance-heavy catalogues, or Rhône-Alpes export pages, use the contact form. Include your URL, languages, integration list, and hard deadlines. I answer by email within Central European working hours with follow-up questions or a scope outline. A written quote follows when the brief is complete enough to price without guessing integration or migration risk.
Selected projects
Examples of my work.
E-commerce Development: led-lumina.pl
led-lumina.pl is a professional online store that presents a comprehensive range of innovative LED solutions for both individual and business customers. The ...
E-commerce Development: like2slide.com
like2slide.com is a website for the ski, snowboard, and wakeboard community, built for inspiration, publishing, and stable operation.
E-commerce Development: marcoaldany.pl
marcoaldany.pl is a WordPress website built to present personalised services to show how this system can support companies offering personalised services or...
WordPress support & development in Lyon
Need this service: Astro developer in Lyon?
Describe your project by e-mail. I reply within 48 hours.
Describe your projectExplore other WordPress services and knowledge base
Migration to Astro, Next.js, and headless WordPress.
WooCommerce sync with ERP and wholesale systems.
Business process automation around WordPress and company systems.
Library of concrete automation use cases.
Headless WordPress, Sanity, Strapi, and Contentful with Astro or Next.js.
Astro, MDX, edge delivery, and Core Web Vitals measured on real traffic.
Custom WordPress engineering and architecture.
Scalable headless, ERP, and AI architecture for enterprise.
Related categories
Supporting articles

Six to sixteen weeks for typical engagements, with a four-phase shape: discovery, scoping, build and cutover, tuning. The variables are catalogue size, integration count, URL preservation, and editorial team readiness, not framework choice.

A definitive 4-year Total Cost of Ownership (TCO) analysis, real-world Core Web Vitals benchmarks, Astro 7 GraphQL APQ architecture, and a 10-point executive decision matrix for choosing between decoupled and traditional WordPress.

The Shopify Plus vs WooCommerce headless decision in 2026 is no longer a binary "platform vs custom" trade-off. Both can run headless, both integrate AI, both ship at the edge. The real axes are control, total cost over five years, and exit strategy. This article walks the matrix with confirmed platform facts.