Astro developer in Athens

Astro.js developer for Athens and Attica firms selling in Greek and English. Static sites shaped for HDPA rules, consumer law and EAA e-commerce.

Astro developer

Migrate from WordPress to Astro in Athens

Many businesses in Athens 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 Astro developer in Gdynia, Poland, and I build public marketing sites for companies in Athens and the wider Attica region. Three buyer types keep showing up in briefs: ship managers and maritime service firms around Piraeus that publish fleet and voyage data to charterers abroad, logistics operators tied to the Port of Piraeus gateway, and startups on the National Startup Registry that must publish a bilingual site before they update their registry profile. Astro compiles pages to HTML before deploy and loads JavaScript only on routes where a form or widget requires client code, which makes Greek privacy and consumer rules easier to enforce in code a compliance reviewer can read in Git before launch.

#What an Astro brief from Athens usually asks for

An Athens Astro brief usually bundles four demands: Greek (el) and English (en) routes that stay paired, cookie and tracker behaviour that matches what the Hellenic Data Protection Authority supervises under the GDPR, Law 4624/2019 and Law 3471/2006, checkout and signup flows shaped by Law 2251/1994 on consumer protection, and performance that survives summer tourism or maritime fair traffic without a database meltdown. The sector decides which demand carries the legal weight.

Ship management offices in the Attica basin publish vessel particulars, crewing policies and charter terms that investors and brokers quote verbatim. A wrong deadweight figure on a public page is a commercial problem before it is a cosmetic one. Logistics firms selling warehousing or forwarding through Piraeus run contact and quote forms whose fields match what their CRM already stores. Startups on the National Startup Registry publish a public site that matches the language investors see on the registry and that a first frontend hire can extend without private build magic.

Your designer or agency supplies visual files. I turn approved layouts into Astro routes, typed content collections, consent islands and the Greek checkout strings your counsel signs off.

#Why Piraeus shipping and Attica logistics firms publish on static routes

Maritime and port-adjacent businesses market on deadlines: a berth window, a charter party date, a fleet renewal press release. Those updates are infrequent relative to page views, which suits a static publish model.

Piraeus Port Authority S.A. describes Piraeus as Greece’s main gateway at the crossroads of Europe, Asia and Africa, with container, car, cruise and coastal shipping services plus a logistics centre on the same estate (Piraeus Port Authority). Forwarders and ship agencies around that hub often run bilingual sites where English carries the commercial offer and Greek carries statutory labels. Astro handles that split in four practical ways:

  1. Each service line or vessel class is one entry in a typed collection, so a missing IMO field or an empty charter contact blocks the build.
  2. The same record feeds the HTML page, Open Graph tags, JSON-LD and the PDF link list, so brokers see the same figure in search results and in structured data.
  3. Schedules and specifications live in Git with dated filenames, so a redesign does not orphan last season’s timetable URL.
  4. Pages ship as cached HTML on a CDN, so a spike after a trade fair or a lane announcement does not hit PHP and MySQL on every request.

When a fleet status moves from “under survey” to “open for charter”, the change is one tracked edit with reviewer and date in Git. For a communications team that answers to principals in London, Singapore or Geneva, that history matters.

#What the National Startup Registry expects from a public site

The government startup portal at elevategreece.gov.gr describes itself as the official digital entry point for startups, run with the General Secretariat for Research and Innovation under the Ministry of Development. The National Startup Registry, hosted at registry.elevategreece.gov.gr, is the official record of startups in Greece; applications go online, and the FAQ states profiles must be updated twice a year in June and December or the company may be removed (registry FAQ).

For an Astro marketing site this creates a narrow but real constraint: the public URLs, product wording and team page your registry profile links to should not contradict what investors read on the registry. I keep founder-editable copy in Markdown or MDX with a schema, so a changelog or pricing tweak goes through pull request review instead of an unlogged CMS click. The registry does not replace legal counsel on state aid, and entering the registry does not by itself make a firm eligible for every scheme; the FAQ states case-by-case assessment. I do not put registry status on the site unless your counsel approves the sentence.

#What the Hellenic Data Protection Authority supervises on an Astro site

The Hellenic Data Protection Authority (HDPA) states on dpa.gr that it is an independent public authority supervising the GDPR, Law 4624/2019, Law 3471/2006 and related rules on personal data. Law 4624/2019 is Greece’s adaptation of the GDPR framework referenced alongside Regulation (EU) 2016/679 in national acts such as Law 4994/2022. Your privacy notice and processor contracts remain counsel work; my scope is how the site behaves.

Law 3471/2006 article 4 paragraph 5, in its current amended text, allows storage or access on terminal equipment only after the user has consented on the basis of clear and comprehensive information, except when storage is solely for transmitting a communication or strictly necessary for an information society service the user explicitly requested. HDPA’s cookie explainer names paragraph 5 as the basis for that consent and lists categories such as session, authentication and load-balancing cookies that may fall outside consent when genuinely necessary (HDPA, what are cookies).

On an Astro build I translate that into build rules:

  • The base layout loads no third-party script. Analytics, chat and advertising pixels mount from one consent island after a stored choice.
  • Accept and reject controls share the same visual weight, because pre-ticked or nudged consent is a common audit finding in EU practice.
  • A deploy step scans generated HTML for known tracker domains outside the island and fails when it finds one.
  • Lead forms declare fields in a typed manifest that must match the privacy page list of processors.
  • Form posts log the consent text version and timestamp beside the email address.

Static hosting removes whole classes of CMS exploit paths, but forms and scripts remain. I document each data path at handover so your data protection contact knows what leaves the browser.

#What Law 2251/1994 requires on a distance-selling checkout

Law 2251/1994 on consumer protection, in the codified text published in the Government Gazette, applies to distance contracts including online sales. Article 3beta paragraph 1 lists pre-contract information the supplier must give in a clear and understandable way before the consumer is bound, including main characteristics, supplier identity and contact routes, total price including VAT where calculable, and the right of withdrawal where it exists (Law 2251/1994 codified text).

Article 3delta paragraph 2 in the same code requires that when the consumer places an order, the control they activate must be labelled in a readable way with words equivalent to an order with an obligation to pay, or another clear formulation with the same meaning. If the supplier does not comply, the consumer is not bound by the contract or order.

Article 3epsilon gives a 14 calendar day withdrawal period for distance contracts outside the statutory exceptions, counted from the contract date for services and from delivery rules for goods described in the same article.

In Astro I keep the Greek order-button label in one string referenced by the checkout island. An automated check on the built HTML fails if that string disappears. Pre-contract summaries render as static pages linked from the basket step, and the withdrawal form ships as HTML and PDF templates your legal team words. When checkout runs on Shopify, Stripe or a Greek payment gateway, Astro still owns product pages and the information screen before redirect, and I verify the hosted step’s label against the same string before go-live.

#How Greek and English routes are wired in Astro

Athens buyers selling cruises, freight or SaaS into the EU often carry Greek copy for domestic compliance and English for foreign buyers on the same domain. Astro’s internationalization guide documents locale routing, fallback behaviour and URL patterns (Astro i18n).

I implement that as:

  • A shared translation map keyed by content id, with el and en paths generated from the same collection entry.
  • hreflang and canonical tags derived from one config so Search Console does not show accidental duplicates.
  • Language switcher components that preserve the current slug across locales.
  • Legal blocks, withdrawal labels and cookie banner text stored per locale in typed files, not hard-coded inside unrelated components.

A missing English title on a Greek product page stops the build. That is deliberate: partial bilingual launches cause more support load than a delayed English route.

#What the European Accessibility Act layer means after June 2025

Directive (EU) 2019/882 defines accessibility requirements for products and services including e-commerce services provided through websites at the consumer’s request (EUR-Lex, Directive 2019/882). Greece transposed it through Law 4994/2022. Article 46 paragraph 2 of that law states that application of Part B begins on 28 June 2025 unless otherwise provided (Law 4994/2022). Part B covers services such as e-commerce, electronic communications and access to audiovisual media services named in the transposition text.

Law 4994/2022 article 15 implements the directive’s conformity presumption for harmonised standards published in the Official Journal of the European Union. Greece’s AccessibleEU monitoring report states that since 12 February 2022 EN 301 549 version 3.2.1 defines technical requirements for website and application accessibility in the Greek framework alongside Directive (EU) 2016/2102 transposed in Law 4727/2020 (AccessibleEU Greece annual report). The European Commission issued a reasoned opinion to Greece in March 2025 over remaining transposition gaps, so counsel may still adjust wording even where templates already follow EN 301 549 patterns (AccessibleEU news, March 2025).

On an Astro e-commerce or booking site I bake accessibility into components: semantic headings, labelled form fields, visible focus, captions on hero media and colour contrast checked on staged builds. Islands for maps or date pickers still require keyboard paths. I do not claim WCAG certification; I deliver HTML your auditor can test with the tools they already use.

#Which technical choices fit Attica buyers

Interactive islands suit quote calculators, berth availability widgets or multi-step charter inquiries without shipping a full client framework on every page (Astro islands). Core Web Vitals targets follow the thresholds Google documents on web.dev: LCP up to 2.5 seconds, INP up to 200 milliseconds and CLS up to 0.1 on mobile profiles.

Headless WordPress, Sanity or Markdown in Git all work as editorial backends. The public domain serves static HTML; the CMS admin stays on a separate host. That separation matches how maritime firms already treat document control.

When most value sits behind a login, such as a principal portal or a live AIS dashboard, a server-rendered framework may fit better; the Next.js developer Athens page covers that split. When the team lives inside WordPress editorial workflows and performance is already acceptable, WordPress developer Athens may be the starting point. I state that in the written estimate when the brief points there.

#How an Athens Astro project runs from brief to launch

StageWhat you receiveWhat your Attica team supplies
Brief reviewA free written estimate with scope, assumptions and open questionsCurrent site URL, launch languages, target window, design file owner
Architecture noteRoute map for el and en, content schemas, redirect list, third-party script inventoryApproved slugs, processor list from your DPO, consent categories
BuildStaging from pull requests and a readable Git historyApproved designs and copy or marked placeholders in both languages
Compliance passConsent island, tracker scan, order-button test, withdrawal templatesPrivacy notice, cookie policy, checkout strings from counsel
LaunchDNS checklist, redirect file, handover guideNamed DNS contact and go-live date

Communication stays written. I do not fly to Athens for workshops. Gdynia uses Central European Time and Athens uses Eastern European Time, one hour ahead, which keeps morning questions and review comments on the same working day without travel.

#Send an Athens project brief

Use the contact form with your current URL, languages needed at launch, whether you sell to consumers online under Law 2251/1994, and who supplies design files. I reply on Central European working days with questions or a written scope, and the first written estimate is free after I read the brief.

See also in Greece

Need this service: Astro developer in Athens?

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

Describe your project

Explore other WordPress services and knowledge base