50 lines
1.6 KiB
Markdown
50 lines
1.6 KiB
Markdown
# Maintenance guide
|
|
|
|
Use this guide when making regular content changes to the live static site.
|
|
|
|
## Safe change workflow
|
|
|
|
1. Start from an up-to-date `main`.
|
|
2. Create a branch.
|
|
3. Edit the smallest set of files needed.
|
|
4. Start a local server from the repo root:
|
|
|
|
```bash
|
|
docker compose up
|
|
```
|
|
|
|
5. Preview each changed page at `http://localhost:8080/`.
|
|
6. Check that images, internal links, and forms still behave as expected.
|
|
7. Commit, push, and open a PR into `main`.
|
|
|
|
## What to edit first
|
|
|
|
For a maintained public website, prioritize these pages:
|
|
|
|
- `index.html`
|
|
- `about-us/index.html`
|
|
- `contact/index.html`
|
|
- `events/index.html`
|
|
- `services/index.html`
|
|
- `videos/index.html`
|
|
|
|
These are the most visitor-facing pages. Archive pages can be improved later
|
|
unless they contain broken links or outdated information that visitors rely on.
|
|
|
|
## What to avoid
|
|
|
|
- Do not rename public route folders without a redirect plan.
|
|
- Do not edit `.forgejo/` for content or design changes.
|
|
- Do not add build tools, package managers, or framework dependencies.
|
|
- Do not delete legacy-looking assets just because they look unused. Verify
|
|
references first with `rg` and a browser preview.
|
|
|
|
## Suggested cleanup order
|
|
|
|
1. Confirm contact details, service times, and current event information.
|
|
2. Check the core pages on desktop and mobile.
|
|
3. Fix broken internal links and missing images.
|
|
4. Remove or adjust forms that cannot submit on a static site.
|
|
5. Clean duplicated export metadata only after confirming pages render the same.
|
|
6. Later, consider a tiny static templating workflow if shared navigation/footer
|
|
edits become frequent.
|