Skip to content
ESEN
Contact

Technology · Web framework

Web development with Astro

Astro is a framework for websites where content comes first: company sites, catalogs, documentation, blogs. It delivers pages already built and loads JavaScript only where interaction is needed. We develop the site, connect it to your content management system and migrate the one you have.

Tell us about your project See an example

Often combined with

Fig. 01Page press1/3CONTENT · HTMLLooping
Each sheet of content passes under the head and comes out as a finished page. The side module lights up only when the page carries an interactive part.

Situations

What you can solve with an Astro website

Astro fits when a site is read more than it is used: many pages, content that changes and a team that wants to publish without depending on anyone.

  • A company site that is hard to maintain

    Every change goes through someone technical, or the site is slow to load. Content is edited in a CMS and the pages are served already built.

  • A catalog with many product pages

    Hundreds of products or services with the same structure. The pages come from your data, be it a CMS, a spreadsheet or an API, and are not laid out one by one.

  • A migration that keeps being postponed

    The current site has fallen behind, but it holds content and traffic you can't lose. It is moved with its routes and redirects reviewed.

  • Interaction only where it helps

    A search box, a filter or a form inside a page that is otherwise content. It is added as an isolated piece, without turning the whole site into an application.

The head: where content becomes a page

What to check before starting

  • Where the content lives today and who edits it
  • Which URLs exist and which ones get visits or links
  • Which forms, maps or third-party scripts the site uses
  • Where it will be published and who will have access

Services

What we build with Astro

The job can be a new site, the move of an existing one, or both at once.

  • Module 1 · Head

    Company and content sites

    The design turned into components, one template per type of page and a site your team updates without asking for help.

    Examples of deliverables

    • Company website
    • Blog or resource center
    • Product documentation
  • Module 2 · Tray

    Connection to content management systems

    Astro reads content from WordPress, from another CMS or from files in the repository, and rebuilds the pages when something changes.

    Examples of deliverables

    • WordPress as the CMS
    • Content in Markdown
    • Catalog from an API
  • Module 3 · Output

    Migrations

    An inventory of content and URLs, a redirect map, the move itself and a page-by-page check before the domain switches.

    Examples of deliverables

    • URL inventory
    • Redirect map
    • Checks after the switch
  • Module 4 · Side module

    Performance and measured interaction

    Images at their real size, fonts that don't make the page jump and JavaScript only in the components that need it.

    Examples of deliverables

    • On-site search
    • Catalog filters
    • Forms with validation

A working example

Edit an entry and watch it reach its page

An illustrative example. Change the title or the text in the CMS on the left and publish: you will see the steps the change takes to reach the page.

Simulated demo · sample data

Content management system

From the edit to the page

  1. Entry saved in the CMS
  2. Notification to the page server
  3. Page rebuilt
  4. Published

What a visitor sees

example.com/news/summer-opening-hours

Summer opening hours

From July 1 to August 31 we open from 8 a.m. to 3 p.m.

The page shows the latest published version.

The CMS and the publishing step are simulated in your browser. In a real project, publishing notifies the server, which rebuilds the affected pages.

Integration

How it fits with your systems

Astro doesn't store content: it reads it from wherever it already is and turns it into pages. So the first thing to know is where each piece comes from.

Where it comes from

AstroAstro sitecomposes and builds the pages

Where it goes

Dependencies worth checking

  • Whether the CMS offers an API and a notification on publish
  • How long a full rebuild of the site takes
  • Which parts need a server: search, private areas
  • Which redirects have to be kept

How we work and what we deliver

How we run an Astro site

  1. 01

    Initial review

    An inventory of the current site: content, URLs, forms and integrations.

  2. 02

    Scope

    Which pages and templates are in, where the content comes from and what is migrated as is or rewritten.

  3. 03

    First release

    One complete template with real content, published at a test address.

  4. 04

    Validation

    Your team edits for real on the test version, and routes and redirects are checked before the switch.

  5. 05

    Documentation

    How to edit, how to publish, how to add a type of page and what to do if a publish fails.

What you get when the job closes

  • The repository and the deployment in your name
  • Documented templates and components
  • The redirect map, applied
  • An editing guide for your team

Questions

Questions about Astro

Missing yours? Write it to info@veodar.com and we'll reply with a specific question, not a brochure.

Does Astro work for a store or a private area?

For the content side, yes: catalog, product pages and informational pages. Anything that needs a user session, a cart or live data needs a server; Astro can render those pages on demand or live alongside a separate application. That is decided when the scope is defined.

Can I keep editing content in WordPress?

Yes. WordPress can stay as the CMS while Astro takes care of showing the pages. The plugins that depend on the current theme need reviewing, because they will stop rendering on the public site.

What gets lost in a migration?

Nothing that was inventoried. The risk is in what nobody remembered: a URL with links pointing at it, a form wired to another system, a measurement script. That is why a migration means reviewing content, routes and integrations before moving anything, and checking it all afterwards.

Does an Astro site rank better?

Astro makes it easier for pages to load fast and reach the search engine complete, which is a good starting point. Rankings also depend on content, structure and links; no framework decides them on its own.

Who publishes changes afterwards?

Your team. Publishing is left automated: you edit in the CMS or in the repository and the site rebuilds. The guide explains the process and what to do if something fails.

Updated:

Related services

All services

Other technologies

What it is combined with

All technologies
  • Custom WordPress developmentCustom features, plugins and integrations that extend your WordPress. We track down bugs and fit the site to the way your business works.
  • React developmentDashboards, search and complex forms. Interfaces connected to your data, to look things up and get tasks done from the browser.
  • JavaScript programmingCalculators, filters, validation and interactions for your website. New features and problem-solving in the code you already have.

Get started

Tell us which site you want to build or move.

If it exists, its address is enough. If not, the kind of content it will hold and who will maintain it.

What helps us assess it

  • The address of the current site, if there is one
  • Who edits the content, and with which tool
  • Which forms or integrations it has
  • Roughly how many pages or product pages there are
Tell us about your project info@veodar.com

Before you write, see how we price a project or our solutions by department.

Fig. 07Morse keyH · E · L · L · O