Astro developer in Lisbon

Astro.js developer in Lisbon. Fast, lightweight websites with a strong technical SEO foundation. Professional web development for businesses in Portugal.

Astro developer

Migrate from WordPress to Astro in Lisbon

Many businesses in Lisbon 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.

Mariusz Szatkowski builds Astro websites from Gdynia for teams headquartered in Lisbon. Public sites there usually ship European Portuguese for regulators, candidates, and local buyers, plus English for investors and export markets, especially in the run-up to Web Summit. Bloated WordPress multilingual stacks or client-rendered marketing shells punish commuters on Margem Sul trains and make CNPD consent stories harder to audit. Astro compiles each locale to static HTML, limits hydration to the widgets that need scripts, and keeps language and compliance hooks in Git where reviewers can diff them.

#What Lisbon buyers expect from a bilingual public website

Lisbon mixes a dense SME fabric in Chiado and Santos, fintech and SaaS teams around Saldanha and Avenida da Liberdade, and a loud November conference season centred on Web Summit at the riverside venues in Parque das Nações. None of those audiences wait politely while a marketing shell downloads a full client framework.

When I read briefs from Lisbon, the recurring requirements stay predictable even when the sector shifts (hospitality in Alcântara, professional services in Restelo, product companies hiring from Beato):

  • Parallel pt-PT and English content, not machine-translated duplicates stuffed with keywords.
  • Optional third locales (Spanish, French, or Brazilian Portuguese) without breaking the primary tree.
  • Core Web Vitals that meet the thresholds published on web.dev (LCP up to 2.5 s, INP up to 200 ms, CLS up to 0.1), because discovery still starts on a phone on MEO or NOS mobile networks.
  • Cookie and analytics behaviour that your DPO can explain to the CNPD without hand-waving about tag managers.
  • Distance-contract disclosures on checkout flows, aligned with Decreto-Lei n.º 24/2014 when you sell to consumers in Portugal.

Your designer owns visual identity, Figma frames, and component specs. I translate approved layouts into Astro templates and connect the pt-PT and English route map beneath them.

#How Astro i18n routing fits pt-PT and English trees

Astro documents i18n routing in the internationalization guide. The model I use for Lisbon clients keeps three ideas in one place: file-based locale segments, a single configuration block, and build-time verification so a missing translation blocks deploy.

A minimal astro.config.mjs excerpt (field names and behaviour described in the official docs) looks like this:

import { defineConfig } from 'astro/config';

export default defineConfig({
  site: 'https://example.pt',
  i18n: {
    defaultLocale: 'pt-pt',
    locales: ['pt-pt', 'en'],
    routing: {
      prefixDefaultLocale: true,
    },
  },
});

With prefixDefaultLocale: true, European Portuguese URLs live under /pt-pt/... and English under /en/.... That matches how many Lisbon companies already think about information architecture: one brand, several language roots, each with crawlable URLs.

Browser language sniffing is poor primary navigation for a Lisbon brand. Redirects burn crawl budget and break shared links from meetups at Factory Lisbon. I use visible header links to the translated slug and reserve Astro fallback settings for edge cases documented in the internationalization guide.

#Translation parity in typed collections

Service pages, FAQs, and release notes live in Markdown or MDX collections. Every document stores lang plus a stable translationKey. A pre-deploy script compares siblings and stops the build when, for example, the English careers page exists without a pt-PT counterpart:

CheckWhy it matters in Lisbon
Every translationKey has pt-pt and en rows when the brief demands two live languagesPrevents launching a Web Summit landing page in English only
hreflang link pairs are reciprocal in the layoutGoogle Search Console surfaces fewer hreflang mismatch warnings
Slugs are human-readable per locale/pt-pt/servicos/ and /en/services/ can diverge while staying linked
Legal snippets (privacy, cookies, terms) exist per localeStatutory text must match the language shown

The Astro islands concept keeps language switchers and consent banners as small hydrated components (client:load or client:visible only where needed). The article body stays static HTML in the active language, which helps both performance and screen-reader predictability under the European Accessibility Act expectations many Lisbon buyers now add to procurement checklists.

#DL 24/2014, Lei 58/2019, and CNPD: what I implement in the template

Portuguese law treats a consumer-facing website as part of a regulated commercial conversation. The consolidated text of Decreto-Lei n.º 24/2014 sets the distance-contract rules your checkout must respect when you sell into Portugal. Law no. 58/2019 implements GDPR nationally, and the CNPD supervises compliance, including breach notification within 72 hours under Article 33 when a personal data breach is likely to affect rights and freedoms (CNPD breach guidance).

Compliance hooks are part of the base layout partials, not optional checkboxes on each new route:

  1. Pre-contract information - product characteristics, total price, payment method, delivery constraints, and withdrawal rights described in the language of the purchase flow, mapped to DL 24/2014 duties before the pay button.
  2. Withdrawal copy - the 14-day consumer right of withdrawal under Article 10 of DL 24/2014, linked from order confirmation templates when your counsel confirms the offer qualifies as a distance contract.
  3. Processor inventory hooks - form endpoints, newsletter tools, analytics vendors, and CRM relays listed in a typed config file your DPO can diff when the stack changes after a funding round.
  4. Cookies and similar storage - under Law no. 41/2004 (electronic communications), non-essential storage waits for consent. Astro’s default of shipping no client JavaScript until hydration makes it straightforward to gate tag managers and pixels behind a consent island.

GDPR privacy notices still belong in your política de privacidade, usually maintained by your DPO or external counsel. My job is to ensure the technical delivery matches what that policy promises: no stray pixel loads, clear records of consent events if you enable logging, and data minimisation on contact forms that feed HubSpot or Pipedrive during peak hiring season.

#When islands beat a monolithic framework for Lisbon content sites

Beato startups often keep Next.js for authenticated dashboards while marketing still needs fast LPs, careers content, and press kits. Astro handles the brochure layer differently from a full SPA:

  • Default output is static HTML per route, which keeps LCP low on congested mobile networks.
  • Hydration is opt-in per component: a Multibanco checkout hand-off, a demo scheduler, or a stock ticker can mount as a React, Vue, or Svelte island while the surrounding case study stays script-free.
  • Deferred server fragments suit personalised pricing blocks without shipping a React runtime to every visitor.

Hotels facing the Tagus and law firms off Marquês de Pombal use the same split: credibility copy in the active language, one or two interactive modules where the business logic actually lives.

#Typical deliverables I ship

  • Corporate and campaign sites with pt-PT and English trees, plus optional investor microsites.
  • Resource libraries and long-form guides authored in MDX collections without a MySQL-backed theme layer.
  • Replatforming from WPML or Polylang stacks that slowed TTFB and hid broken hreflang pairs.
  • Headless splits where editors stay in WordPress admin and Astro serves the visitor-facing domain.
  • Performance and markup audits on existing Astro repos before a CNPD-oriented privacy review or accessibility remediation.

Portfolio tiles with invented logos never appear here. For vendor checks, post in WordPress Lisboa or ask me for sector peers I already worked with in writing.

#Lisbon startup rhythm: Web Summit, Beato, and written delivery from Gdynia

Web Summit concentrates global press and investor attention on Lisbon each November. Product marketing teams compress launch timelines into the six weeks before badges print, which means your staging environment must survive dozens of copy iterations without breaking hreflang or consent gating.

Factory Lisbon in Beato and the wider Hub Criativo do Beato district recruit engineers who already recognise Astro, Next.js, and headless WordPress patterns. A handover survives when someone in the city can read your repository, not when a deck claims victory after a single deploy Friday.

I work remotely from Gdynia. Discovery calls, on-site workshops, and always-on Slack theatrics are out of scope. Delivery runs through written briefs, clarifying questions, scope notes, staging links, and merge requests your counsel or SEO partner can audit asynchronously.

PhaseWhat you seeWhat I need from you
IntakeWritten restatement of goals and risksSite URL, language list, must-have legal pages, Figma or approved HTML/CSS
Architecture notei18n map, collection schemas, redirect listConfirmation of default locale and slug rules per language
Build sprintsPreview on staging, changelog in GitContent in each language or signed-off placeholders clearly marked
Compliance passFooter IDs, cookie gating, form labelsLegal text from your advisor, cookie taxonomy
LaunchDNS checklist, redirect file, Search Console hintsGo-live window, owner for DNS

Staging stays up across revisions so Portuguese and English reviewers can click real URLs, not PDF screenshots. Acceptance is checklist-driven: translation parity, distance-contract fields present where sales qualify, vitals spot-check on key templates, forms delivering to the inbox or CRM you specify.

#Checklist you can use before signing with anyone (including me)

Even if you never hire me, this list saves rework common on Lisbon RFPs:

  1. Decide whether pt-PT and English are launch-critical or phased.
  2. Inventory legal routes (privacy, cookies, impressum-style notices, terms) for each live language.
  3. Freeze URL patterns (/pt-pt/, /en/) before copywriters touch the CMS.
  4. Demand mutual hreflang in rendered HTML and XML sitemaps, not only inside a translation plugin UI.
  5. Classify cookies and trackers before marketing embeds Google Tag Manager.
  6. Plan Core Web Vitals measurement on real mobile profiles, not only on office Wi-Fi at Oriente.
  7. Name one accountable counsel contact who approves statutory text updates post-launch.

Depending on where you are in the stack, these adjacent pages may fit better as a starting point:

#Start with a written brief

If you need a pt-PT and English Astro site, a headless refactor, or a compliance-focused template rebuild, use the contact form. Send the live URL, language list, launch deadline, and who owns design delivery. I answer on CET business days with clarifying questions or a scope note. The first written estimate is free once the brief is detailed enough for individual pricing.

See also in Portugal

Need this service: Astro developer in Lisbon?

Describe your project by e-mail. I reply within 48 hours.

Describe your project

Explore other WordPress services and knowledge base