Why we chose Astro for the Lancio Studio website.

Most people visiting this website do not care that it is built with Astro. Nor should they.

They care whether it loads quickly, works properly on their phone, makes information easy to find and gives them confidence in the studio behind it. The technology only matters when it affects those things.

We chose Astro because it suited the job Lancio needed the website to do. It gave us the freedom to build a distinctive, content-led site without adding an editing system, database and application layer that we would not use.

We started with the job, not the platform

The Lancio site needs to explain four areas of work, show detailed case studies and answer the questions clients ask before commissioning a project. That includes a growing Glossary, practical Insights and pages covering our web design and development.

Most visits involve reading and comparing. Nobody needs an account to view the site. Prices and availability are not changing every minute. There is no live stock, customer dashboard or booking process to assemble for each visitor.

That made a largely static website the sensible starting point. Static does not mean fixed or basic. It means the main pages can be prepared before somebody visits instead of being rebuilt each time they ask for one. Our guide to static and dynamic websites explains that distinction in more detail.

What Astro changes for the visitor

Astro prepares pages during the site build by default. Each service page, Glossary entry, Insight and case study becomes finished HTML that can be sent straight to the browser.

In plain English, much of the work has already been done before somebody clicks the link.

That gives us a strong starting point for page speed, accessibility and search visibility. It does not guarantee any of them. A badly sized image can still be heavy. A poor layout can still be confusing. Technical choices support good design, but they do not replace it.

Astro also sends no browser JavaScript for an ordinary component unless we deliberately add it. The site still has interactive features: the navigation opens, cookie preferences are remembered, the enquiry form provides feedback and case study images can be enlarged. Each of those features has a reason to run in the browser. The rest of the page does not have to behave like an application.

Why we did not choose WordPress

WordPress is a content management system. One of its main advantages is that people can sign in, edit pages and publish content through a browser dashboard without changing the underlying code.

That can be exactly what a business needs. If several people publish content, permissions and editorial tools matter. If a team already knows WordPress, keeping that familiar workflow may be more valuable than changing technology. Its plugin ecosystem can also add established functionality without starting from scratch.

Lancio does not need that editing workflow. The same studio maintains the content, design and code, so changes can be reviewed and published together. There is no separate content team waiting for a browser editor and no requirement to hand page editing to somebody outside the build process.

Using WordPress anyway would mean running an admin area and database, managing user access and keeping WordPress itself, its theme and any plugins updated. Managed hosting can take care of some of that work, but it would still be a system to maintain.

WordPress is not inherently slow or unsuitable. A well-built WordPress site can perform very well. It simply would have given Lancio an extra layer without giving us a useful benefit in return.

How the content grows without a CMS

Not having a CMS does not mean every new article requires a new page design.

The Glossary, Insights and case studies are organised into Astro content collections. Each entry is a straightforward text file with a small set of details such as its title, summary, date and topic. Astro checks that those details are present and correctly formatted before the site can be published.

That structure lets one piece of content appear in several useful places. A new Insight gets its own page, joins the Insights index, appears under its topic, enters the RSS feed and receives a social sharing image. A new Glossary entry joins its category and can link readers to related explanations and services.

It supports the long-term publishing approach described in why we are building the Glossary one question at a time, without requiring a general-purpose admin system behind it.

This approach would not suit every client. If frequent non-technical editing is central to the project, the editing experience should be part of the technology decision from the beginning.

The design was allowed to behave like the brand

The Lancio identity does not fit an off-the-shelf theme. Large type, honey-gold surfaces, deep plum sections and changes of pace between pages all do useful work. They help the site feel like the studio rather than a template with a logo added.

Astro lets us build reusable pieces for consistency while keeping control of the page composition. The header, article structure, service navigation and case study frames can share one system. Individual pages can still respond to their content.

That connection between brand identity and implementation matters. A distinctive design is only useful if it remains coherent when the website grows.

Images are prepared for different screens

The Inspiring Leaders case study contains detailed platform screenshots. They need to remain legible without making a phone download the same large file as a desktop screen.

Astro’s image tools create optimised versions at several widths when the site is built. The browser can choose a suitable version for the available space. Dimensions and alternative text are handled as part of the component, supporting both responsive performance and website accessibility.

That removes a repetitive manual task and makes sensible image handling part of the normal publishing process.

Would we recommend Astro for every client?

No. Choosing a familiar tool before understanding the business is how websites end up serving their platform instead of their users.

WordPress or another CMS may be the better choice when a client needs a browser-based editing workflow, several publishing roles or established integrations. A product with accounts, live data and complex user journeys may need to be approached as a web app rather than a content-led website. Other projects will sit somewhere between those two.

Astro can connect to a CMS and support server-rendered or highly interactive features. The fact that it can do those things does not mean every project should use them.

For Lancio, the fit was specific: content that grows steadily, design that should not be constrained by a theme, pages that can be prepared in advance and a small number of purposeful interactions. Visitors do not need to know which framework made that possible. They should simply find a website that loads promptly, explains the work clearly and stays out of their way.