The public website of the Space Array Initiative: https://spacearray.org
The site is built with Astro. GitHub builds the site and publishes it after every merge to main, so nobody needs to run anything on their own computer. A merge goes live within a few minutes.
Each page is one file in src/pages/. The menu, the page head and the footer are in one shared file, src/layouts/Layout.astro. Change the menu there, and it changes on every page.
| File | Page |
|---|---|
src/pages/index.astro |
Home |
src/pages/science.astro |
Science |
src/pages/sharp.astro |
SHARP |
src/pages/technology.astro |
Technology |
src/pages/team.astro |
Team (the list comes from public/team.json) |
src/pages/news.astro |
News |
src/pages/contact.astro |
Contact |
src/layouts/Layout.astro |
Head, menu and footer for all pages |
public/styles.css |
Colors, fonts and layout for all pages |
public/images/ |
Images |
Files in public/ go online as they are. For example, public/images/photo.jpg is at https://spacearray.org/images/photo.jpg.
The page addresses did not change. src/pages/news.astro is still at https://spacearray.org/news.html.
- Open the page's file in
src/pages/on GitHub (see the table above) and click the pencil icon. - Change the text between
<main>and</main>. It is normal HTML. - Click Commit changes, choose Create a new branch, then Propose changes.
- Open the pull request and merge it (see below).
Each page file starts like this. Leave these lines as they are:
---
import Layout from "../layouts/Layout.astro";
---
<Layout title="Science · Space Array" active="science.html">The last line of the file is </Layout>. Leave it as well.
Curly brackets: do not type { or } in the text. Astro reads them as code, and the build fails. Write { for { and } for }.
A new page needs a file and a menu link.
-
Open a page in
src/pages/on GitHub, for examplescience.astro, and copy all of its text. -
Go to the
src/pages/folder. Click Add file, then Create new file. Give it a short name, for exampleevents.astro, and paste the text. Its address is thenhttps://spacearray.org/events.html. -
In the
<Layout ...>line of the new file, change the title and setactiveto the new address:<Layout title="Events · Space Array" active="events.html">
-
Replace the text between
<main>and</main>. -
Click Commit changes, choose Create a new branch, then Propose changes.
-
Add the menu link in the same branch. On the repository page, switch the branch menu from
mainto your new branch. Opensrc/layouts/Layout.astroand click the pencil icon. -
In the menu (
<nav>), copy one link line and change it to the new page:<a class={active === "events.html" ? "active" : undefined} href={`${base}events.html`}>Events</a>
-
Click Commit changes and choose Commit directly to your branch. Then open the pull request and merge it.
The menu on every page now shows the link. The link is highlighted on the new page.
- Open
src/pages/news.astroon GitHub and click the pencil icon. - Copy one
<article>block and paste it above the newest item. - Change the date, the title and the text.
- Click Commit changes, choose Create a new branch, then Propose changes.
- Open the pull request and merge it (see below).
<article class="card" style="margin-bottom:2rem;">
<div class="kicker">10 June 2026</div>
<h2>Title of the news item</h2>
<p>
Two or three sentences about the news.
</p>
</article>A news item with its own page shows a proper preview (title, summary and photo) when someone shares its link on LinkedIn, X, Slack or email. See src/pages/news/simulation-working-group-sweden.astro for an example.
- Put the photo in
public/images/. Also add a copy cropped to 1200 x 630 pixels for the preview. - Copy the example page in
src/pages/news/and give the copy a short name, for examplemy-news-item.astro. - Change the title, the summary (
description, under 160 characters),path,image,imageAltand the text. - On the News page, link the item's title to
news/my-news-item.html. - After the merge, share
https://spacearray.org/news/my-news-item.html, not the News page.
The Team page reads public/team.json. The script tools/csv_to_json.py builds that file from the sign-up form responses.
- Export the form responses as a CSV file.
- Save it in the
data/folder, with the same file name as the CSV that is there now. - Run
python3 tools/csv_to_json.py. It rewritespublic/team.json, sorted by last name. - Commit the new
public/team.json.
Do not edit public/team.json by hand. The script overwrites it the next time it runs.
A pull request (PR) is a proposed change. Nothing goes live until someone merges it.
- Open the PR from the Pull requests tab.
- Read the description and look at the before and after screenshots.
- Click Files changed to see the exact lines that change.
- To ask for a change, write a comment on the PR.
- When you are happy, click Merge pull request, then Confirm merge.
To undo a merged PR, open it and click Revert. GitHub creates a new PR that undoes the change.
After each merge, GitHub builds the site. Open the Actions tab to see the build.
- A green check means the build worked and the live site has the change.
- A red X means the build failed. The live site does not change. It keeps the last version that built.
To find the problem:
- Click the failed run, then click build.
- Look for
ERROR. The lines near it name the page, for examplescience.astro:19(the file and line number) orrendering /science. - Fix it in a new PR. Or open the PR that caused it and click Revert.
Two common causes: a { or } in the text (see "How to change the text on a page"), or a deleted </Layout> line.
This is optional. You only need it to see a change before you open a PR.
- Install Node.js version 22.23.4 or later.
- In the repository folder, run
npm cionce. It installs Astro. - Run
npm run devand open http://localhost:4321 in a browser. When you save a file, the page updates. - Press Ctrl+C to stop it. If it started in the background, run
npx astro dev stop.
To check that GitHub can build your change, run npm run build. It must end with Complete!. The built site is in dist/.
- Code (HTML structure, CSS, scripts): MIT License. See LICENSE.
- Content (text and images): Creative Commons Attribution 4.0 International (CC BY 4.0). See LICENSE-CONTENT.
Images from other sources keep their own license. Their credit lines say where they come from.