Cyber Week30% off Lifetime with code CYBER — it will never be this cheap againUntil 28 Nov, 10:00 CET

Getting started

Install & projects

Getting the app, signing in, creating a project, opening one, keeping its Astro current, and what a project folder contains.

sitereal is an app for macOS, Windows and Linux. It runs on your machine, opens a folder and edits the site in it — nothing you build is uploaded anywhere. Signing in once puts the computer on your license. On a Mac, download it from the download page and drag it into Applications — it is signed and notarized by Apple. On Windows, one line in PowerShell installs it, and the setup is signed; on Linux, one line in a terminal, or the .deb from the same page. The same line on a Mac installs the sitereal command, which opens the builder in your browser — or, with Homebrew, brew install meinaufwind/tap/sitereal.

Requirements

  • The app — macOS 13 Ventura or newer, Windows or Linux.
  • Node.js 22.23.4 or newer and git. A sitereal site is an Astro site: Node builds it — today’s Astro 7 will not start on anything older — and git gives every project a history of its own, which is what History and Publish work from. You do not have to fetch either first — the New Project dialog checks for both and offers to install what is missing (through winget on Windows, Homebrew or Apple’s command line tools on a Mac, or the download page), and says so when your Node.js is too old; so do the build check and the preview of a site you open. Everything after that is the app’s job, including installing a new project’s packages.

Signing in

The first screen is the sign-in: your email address, then the six-digit code we send you — there is no password. New here? Create one asks for your name as well; it is the same two steps. An account without a license gets three choices: Start 7-day free trial — every feature, no card, nothing renews it — or buy Yearly or Lifetime. Buying opens the checkout in your browser, already tied to your account, and sitereal picks the license up by itself a few seconds after you pay. There is one free trial per account and per computer.

When a trial or a yearly license ends, sitereal stops opening projects and says so, with a way to buy. Your sites are untouched: they are plain Astro in your own folders and keep building and running without sitereal. A license runs on three computers; Settings → Devices in the project manager lists them, and signing one out makes room for another.

The project manager

The window you land in is a grid of your projects. Each card is led by a picture of the project’s home page, taken for you whenever you open or save it. A project you have not opened yet shows a mark made from its name instead.

  • Pin a project to keep it at the front. Pins are ordering only; nothing on disk moves.
  • Remove from list takes a project off the grid. It deletes nothing but its picture.
  • Folders in the sidebar group projects — drag a card onto one, or use Move to folder on its menu. A folder is only a name on the list; nothing on disk moves.
  • Duplicate… makes a new project from an existing one: its files, none of its history, and a repository of its own — for the site you build again for the next client. The copy leaves .env behind, so one site’s keys never become another’s.
  • Settings — the last entry in the rail — holds what belongs to the app, not to a site: your license and computers, your GitHub account, where new projects are created, and updates. A project’s own settings live inside the project window.

Creating a project

Add Project first asks where the site comes from: an empty project, a folder already on this computer (any Astro site works), a repository you open from GitHub and keep working on, or a copy of a GitHub master — a repository you reuse as the start of new sites, copied into a project with a history of its own. For an empty project, give it a name and a location. sitereal writes a complete Astro project:

my-site/
  site.sitereal            the project document — everything the builder knows
  package.json             what Astro needs to build the site
  astro.config.mjs
  tsconfig.json
  .gitignore
  README.md
  .vscode/                 settings for anybody who opens it in VS Code
  public/favicon.svg
  src/
    layouts/PlainBase.astro   the layout every page uses — yours from here on
    pages/                    your pages
    components/               your components

It also gives the project a history of its own, two templates — Main, which every page renders inside, and 404, which the error page keeps for itself — and installs the packages the site needs. There is nothing to run yourself. The project is ready to open the moment it appears in the grid.

If you have marked a preset as the one new projects start from, it is applied before the project file is first written — the project has never existed without your design system. The site's own identity (name, URL, social links) is never carried by a preset. See Presets.

Opening a project

Open any project from the grid, or a folder that holds a site.sitereal with Open Project…. Each project opens in its own window, and switching to another one replaces it rather than piling windows up.

Keeping Astro current

A site keeps the version of Astro it was made with until it is updated. Settings → Astro shows the Astro your site builds with, Astro’s own packages beside it, and any known security issues in those versions, as npm reports them. Known issues are listed again when you go to publish.

Within the major version the site is on — 7.2 to 7.4, say — updating is one button: fixes and new features, nothing that breaks. It installs with the site’s own package manager, the build check runs, and Put back restores package.json and the lockfile as they were. A new major version changes things a site may rely on, so it is only ever tried on a branch of its own: sitereal commits your current work, makes the branch, installs and commits the new Astro there, runs the build check and links Astro’s upgrade guide. Merge the branch when the site holds; switch back, and that branch’s packages are installed again.

Updates run only in a folder this computer trusts, because installing runs the project’s own scripts. Each one checks the Node.js the new version needs, and says so when yours is older.

Seeing the real site

The canvas draws your pages itself, instantly, without building anything. To see a page exactly as it will ship — in your own browser, with its scripts running — press ▶ in the top bar. sitereal saves first, starts a preview of the whole site the first time you ask, and opens the page you are on.

Both views are the same files. Editing src/pages/about.astro by hand and editing it on the canvas are two ways of touching one thing: an edit made in your editor, or in code mode beside the canvas, is read back onto the canvas, and nothing you wrote is ever written over — see Code mode & files.