Technology in practice
Astro
Publish content on a lightweight, maintainable website
A fit for corporate, editorial and product websites where content and navigation matter more than continuous interaction.
Let’s discuss your situation ↗01
Choose with context
What we assess before recommending it
If most of the experience depends on sessions and interactive state, we assess an application architecture. Astro does not replace editorial work or guarantee rankings.
This capability supports those areas according to the project. If the solution is still unclear, we start by organising needs and priorities. Explore Strategy ↗
02
What we can address
We structure pages and components to send only the necessary interaction to the browser.
We model content and languages and connect editing workflows to the chosen CMS.
We prepare metadata, URLs and redirects, measure performance and verify migration.
Technical detail, explained
- CMS
- The environment where the team edits and organises content.
- Technical SEO
- Structure and signals that support crawling; they do not replace content quality.
03
What you receive
We specify these deliverables in the proposal, according to what needs building or reviewing.
- Page templates and a content model.
- A documented editing and publishing workflow.
- URL map, redirects and technical SEO checks within the agreed scope.
The proposal identifies source code and documentation to deliver, client access and third-party licences. We agree ownership and handover before starting.
04
Getting started
We review pages, languages, CMS and traffic to existing URLs. Integrations and content migration shape the plan.
- Share the context: what exists, who uses it and what needs to change.
- Where technical uncertainty remains, we propose a bounded review before estimating implementation.
- We agree deliverables, phases, acceptance criteria, schedule and budget before building.
Timing, investment and third-party costs
We do not publish a single figure because a review and a full build are different engagements. The estimate separates our work from hosting, licences and usage-based services, and identifies dependencies such as access, content or app store approval.
What happens after handover
We define validation, handover and any included support period. Ongoing maintenance is agreed separately, with explicit coverage, channels and response times; continuous availability is not assumed.
Let’s start with your situation.
Tell us what you want to improve and what exists today. You do not need to have chosen the technology.