Migrate from WordPress to Astro in Cluj-Napoca
Many businesses in Cluj-Napoca 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.
Cluj-Napoca is Transylvania's primary center for software engineering, artificial intelligence research, B2B SaaS, and nearshore product development. Across the technology campuses at The Office (Bulevardul 21 Decembrie 1989), Liberty Technology Park, Cluj Innovation Park (CREIC), the engineering hubs in Mărăști, Zorilor, and Bună Ziua, and the research clusters around Babeș-Bolyai University (UBB) and the Technical University of Cluj-Napoca (UTCN), hundreds of product companies and software houses compete for enterprise contracts across DACH, the UK, the Nordics, and North America. I build and migrate fast, maintainable web platforms using Astro, working as a solo software developer in Gdynia, Poland, collaborating with your Cluj-Napoca team entirely in writing.
Why Cluj-Napoca software houses and SaaS startups choose Astro
In Cluj-Napoca, a company’s public website, its technical case studies, architecture whitepapers, B2B service pages, and developer documentation, is scrutinized directly by CTOs and VP Engineering buyers in Munich, Zurich, London, and Austin.
Yet many Cluj software companies run their public sites on stacks that undercut their own engineering credibility:
- Heavy React SPAs (Next.js / Gatsby) used for static marketing: When a prospective enterprise buyer opens a case study or architecture blog post on a full React SPA, their browser downloads and executes hundreds of kilobytes of framework JavaScript and serialized JSON state just to display static prose and diagrams.
- Legacy WordPress installs with visual page builders: Marketing teams spin up Elementor or Divi pages that fail mobile Core Web Vitals and require constant PHP plugin security patching.
Astro solves this by compiling .astro, Markdown, and MDX pages into zero-JavaScript static HTML and scoped CSS at build time, while letting your frontend engineers mount interactive React, Vue, or Svelte islands only where browser state is needed.
Multi-framework UI islands and View Transitions (<ClientRouter />)
Inside a Cluj software company, different product squads often work with React, Vue, or Svelte. Astro is the only modern web framework that lets you mount existing .tsx, .vue, and .svelte components inside the same static codebase without shipping any of those runtimes on purely static routes:
---
// src/pages/en/case-studies/[slug].astro
import BaseLayout from '../../../layouts/BaseLayout.astro';
import ArchitectureMetricsTable from '../../../components/ArchitectureMetricsTable.astro';
import CloudCostEstimator from '../../../components/react/CloudCostEstimator.tsx';
import TelemetrySparkline from '../../../components/svelte/TelemetrySparkline.svelte';
import { getEntry, render } from 'astro:content';
const { slug } = Astro.params;
const study = await getEntry('caseStudiesEn', slug);
const { Content } = await render(study);
---
<BaseLayout title={study.data.seoTitle} description={study.data.seoDescription} lang="en">
<article class="case-study-shell">
<h1>{study.data.title}</h1>
<!-- Static HTML compiled from MDX: 0 KB client JavaScript -->
<ArchitectureMetricsTable metrics={study.data.verifiedMetrics} />
<Content />
<!-- Svelte Island: lightweight interactive chart hydrated on idle -->
<TelemetrySparkline client:idle series={study.data.latencySeries} />
<!-- React Island: interactive estimator hydrated only when scrolled into view -->
<CloudCostEstimator client:visible baseline={study.data.cloudBaseline} />
</article>
</BaseLayout>When paired with Astro’s native browser View Transitions API (<ClientRouter /> from astro:transitions), page-to-page navigation feels instantaneous while keeping the main thread free. Every build targets Google’s official Core Web Vitals “Good” thresholds in real-user CrUX data:
- Largest Contentful Paint (LCP): up to
2.5 s - Interaction to Next Paint (INP): up to
200 ms - Cumulative Layout Shift (CLS): up to
0.1
Romanian statutory and regulatory compliance built into your Cluj-Napoca Astro stack
Operating a commercial website from Cluj-Napoca requires compliance with Romanian national statutes alongside European Union directives. Building on Astro allows me to enforce these legal and technical disclosures directly in the server-rendered HTML templates.
1. Transylvanian SaaS Privacy Hygiene: ANSPDCP and Law 506/2004 Art. 4(5) compliance
For Cluj-Napoca software companies, data protection is enforced by ANSPDCP under the GDPR and Legea nr. 190/2018, while reading or writing non-essential browser cookies falls under Art. 4(5) of Legea nr. 506/2004.
In my Astro builds for Cluj-Napoca companies:
- Zero non-technical scripts before affirmative opt-in: Because Astro outputs static HTML with zero third-party JavaScript by default, no analytics, heatmaps, or attribution scripts execute until the visitor grants explicit opt-in consent in your CMP.
- Self-hosted
.woff2web fonts: To prevent unconsented transfer of visitor IP addresses to third-party US servers on initial load, I never load fonts fromfonts.googleapis.com. All web fonts (with complete Romanian comma-below diacriticsă, â, î, ș, țalongside German umlauts for DACH client portals) are subsetted and served directly from your first-party European origin.
2. Mandatory ONRC Cluj corporate disclosures (Law No. 365/2002 & Law No. 31/1990) and ANPC SAL/SOL badges
Under Art. 5 of Legea nr. 365/2002 and Art. 74 of Legea nr. 31/1990, every Cluj-Napoca S.R.L. or S.A. must display verifiable corporate identification data on its public domain. Where B2C services or digital products are sold to consumers in Romania, the National Authority for Consumer Protection (ANPC) mandates visual dispute-resolution pictograms under ANPC Order No. 225/2022.
I wire a schema-validated global footer and legal layout that renders server-side across all language versions (en, de, ro, fr):
- Full company name (Denumire societate) and legal form (S.R.L., S.A.).
- Registered office address (Sediu social) in Cluj-Napoca (Cluj-Napoca, jud. Cluj).
- Fiscal registration identifier (Cod Unic de Înregistrare - CUI, with
ROVAT prefix for EU cross-border invoicing). - Trade Register registration number with the Trade Register Office attached to the Cluj Tribunal (Oficiul Registrului Comerțului de pe lângă Tribunalul Cluj - ONRC), displaying
J12/XXXX/YYYYor the unified nationalJYYYYXXXXXX...format and EUID. - Subscribed share capital (Capital social) as recorded in the Cluj Trade Register.
- Where consumer services or e-commerce transactions are offered, standardized ANPC SAL (Soluționarea Alternativă a Litigiilor) and SOL graphical pictograms rendered with explicit
widthandheightattributes (CLS = 0).
3. Accessibility (Legea 232/2022) and NIS2 Security for Cluj Software Houses
Romania’s European Accessibility Act transposition (Legea nr. 232/2022, in force since 28 June 2025) and the NIS2 cybersecurity regime (OUG nr. 155/2024, supervised by DNSC) apply directly to Cluj digital product companies and IT service providers.
Building your frontend on Astro directly supports both frameworks:
- WCAG 2.1 Level AA / EN 301 549 compliance: Every Astro template uses semantic HTML5 landmarks (
<header>,<nav>,<main>,<article>,<footer>), native<details>/<summary>disclosures, and keyboard-verified Astro Islands with high-contrast:focus-visiblestates. - Zero public database or CMS surface: Serving pre-compiled static HTML from global edge nodes while keeping any headless CMS or internal API behind private authentication eliminates public SQL injection and
/wp-adminbrute-force vectors.
Multilingual export SEO (en, de, ro, fr) for Transylvanian tech companies
Cluj-Napoca companies frequently publish in English (en) for global markets, German (de-DE / de-AT / de-CH) for DACH automotive, finance, and industrial clients, French (fr), and Romanian (ro) for domestic recruitment and enterprise sales.
| SEO & Architecture Layer | How I Engineer It in Astro for Cluj-Napoca Clients |
|---|---|
| Static i18n Routing | Native Astro locale routing (/en/..., /de/..., /ro/..., /fr/...) compiled ahead of time with zero edge-middleware latency |
| Reciprocal Hreflang | Build-time checks verifying every localized page links to its exact translated counterparts plus x-default |
| Server-Rendered Schema.org | JSON-LD @graph combining Organization, LocalBusiness, SoftwareApplication, TechArticle, FAQPage, and BreadcrumbList in <head> |
| 301 Migration Safety | Complete pre-cutover URL crawl preserving existing canonical URLs or mapping retired slugs via single-hop 301 edge rules |
How a project with me runs
I am Mariusz Szatkowski, an independent software developer based in Gdynia, Poland (1 hour behind Cluj-Napoca EET/EEST). When a Cluj-Napoca team engages me, I write the Astro and TypeScript code directly without agency account managers or junior handoffs.
- Asynchronous written collaboration for Cluj teams: Every architecture note, URL redirect map, and pull request review happens in writing via GitHub, GitLab, Linear, or email, with zero video calls or workshops. Your Cluj-Napoca developers and product leads get a clean, searchable written record they can review asynchronously.
- Design handoff for Cluj projects: Your Cluj-Napoca UI/UX designer or product studio supplies the Figma files and visual assets. Your in-house designer or Cluj creative studio supplies the Figma files (or I replicate your existing visual layout during a migration from WordPress, Webflow, or Next.js), and I implement them into clean, accessible Astro and Tailwind CSS code.
- What your Cluj-Napoca team sends to start:
- Your current Cluj domain URL (if migrating) or a written technical brief.
- Read access to your Cluj Figma files or existing Git repository.
- Your preferred CMS setup (Markdown/MDX in Git, Sanity, Strapi, Directus, Storyblok, Contentful, or headless WordPress) and target locales (
en,de,ro,fr). - Any required form, API, or CRM integration endpoints (e.g., HubSpot, Salesforce, Pipedrive).
I reply to Cluj-Napoca teams in writing on working days and deploy each milestone to a dedicated staging URL for performance and compliance checks.
Start your Astro project in Cluj-Napoca
If you want to launch a fast Astro website or migrate an existing Cluj-Napoca platform away from a slow monolithic CMS or heavy SPA, send me your current URL, target languages, CMS setup, and timeline via my contact page. Your initial written Cluj-Napoca scope estimate is free, and I reply in writing on working days.
Selected projects
Examples of my work.
E-commerce Development: dkf.za.pl
DKF.za.pl is a website created in 2010 for the Film Discussion Club “ZA”, operating as part of the Polish Federation of Film Discussion Clubs. The project wa...
E-commerce Development: eclipsesource.com
EclipseSource, founded in 1997, is a global leader in Eclipse technologies, with a strong presence in Europe and North America, specializing in enterprise so...
E-commerce Development: estel-poland.com
estel-poland.com is a professional online store for cosmetics, created for customers seeking high-quality skincare and makeup products. The platform is desig...
WordPress support & development in Cluj-Napoca
Need this service: Astro developer in Cluj-Napoca?
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.