Editing Safely
Skill level: Complete beginner
Nothing you change in Givo is permanent if you keep checkpoints. These habits make every edit safe to try, whether you edit by hand or with AI.
The Safe Editing Loop
- Run the site with
npm run dev, so you see each change as soon as you save. - Change one thing, save, and look at the page. Watch the terminal too: yellow
[organization],[donate], or[forms]lines point at a value to fix. - Make the window narrow to see the phone layout: open the mobile menu and check the Donate bar at the bottom.
- Switch to dark mode with the light/dark button in the header, and look again.
- Check your other languages: open the same page under
/fr/and/ar/. Each language reads its own folder, so change each one. Arabic pages read right to left. - Save a checkpoint when it works (see below).
- Repeat.
Small steps make problems easy to find: if the page breaks, it was the last change.
Save Checkpoints With Git
In VS Code’s Source Control panel (or the terminal):
git add .git commit -m "Change office hours and hero text"- See what changed since the last checkpoint: click a file in the Source Control panel. Removed lines are red, added lines are green.
- Undo changes to one file: right-click it in Source Control and choose Discard Changes.
- Undo everything since the last checkpoint:
git restore .in the terminal.
No git? Copy the whole Givo project folder (without node_modules/) before a big change, and name the copy with the date.
Before You Change Code
Content files are hard to break. Components and styles are easier to break and harder to fix. Before you edit anything in src/layouts/, src/lib/, or src/styles/:
- check whether the change can be made in a content file or
config.tomlinstead (it usually can: many sections have several layouts, and every page can override a section with a named block) - save a checkpoint
- run
npm run astro-checkafterwards
Edit Amounts And Goals With Care
Every donation amount on the site comes from src/content/donate/<language>/-index.md, and every campaign figure from the cause files in src/content/causes/<language>/. A wrong number there changes the donation form, the quick donate panel, the monthly tiers, the progress bars, and the cause cards at the same time. After you edit them:
- keep each value a plain number (
50, not"50"or$50) - copy the same numbers into every language’s file:
npm run buildprints a[donate]warning listing the keys of the donate file that differ. Nothing warns about cause files, so compare those yourself - open
/donate/, pick a few amounts in both one-time and monthly, and check that the receipt and the total make sense. Then open/causes/and check the progress bars
Run The Checks
npm run astro-check # finds mistakes in code, translations, and content files that have a schemanpm run build # builds the full site, as your host willRun both before every deploy. Stop npm run dev first, and run them one after the other, not at the same time.
astro-check doesn’t check the section files or the contact page file, so the safe editing loop above (look at the page after each change) is your check for those. Read the yellow lines in the npm run build output: [site] means baseUrl is still the placeholder, and [forms] means a form still posts to a placeholder address or the donation form is not connected.