Contribute
Share your knowledge, help the community
Contributing Made Easy
Follow these simple steps to start contributing, even if you're new to coding!
1. Download VS Code
Visual Studio Code is a free code editor for Windows, Mac, and Linux.
2. Sign Up for GitHub
Create a free account to contribute and track your changes.
3. Set Up Copilot
In VS Code, go to Extensions and install GitHub Copilot. Sign in with your GitHub account.
4. Fork & Clone the Repo
Go to the repo and click Fork.
Then, copy your repo link and run:
git clone https://github.com/YOUR-USERNAME/surfdeeper.git
5. Add/Edit Guides & Spots
Edit or add Markdown files in src/content/guides/
or src/content/spots/
. Copilot will help you write!
6. Commit & Push
In the terminal, run:
git add .
git commit -m "Add new guide/spot"
git push
origin main
7. Make a Pull Request
Go to your fork on GitHub, click Compare & pull request, add a description, and submit!
Update Spot Coordinates
If you notice a spot's pin is in the wrong location on the map:
- Go to the Spots page
- Click on the spot marker to open the popup
- Click "๐ Pin in wrong location?"
- Drag the pin to the correct location
- Click "Done - Show Instructions" to get the new coordinates
- Follow the GitHub link to submit your correction
The coordinates are stored in the frontmatter of each spot's markdown file
at src/content/spots/
.
How it works
Keep it simple. Follow existing patterns. Thatโs it.
-
Put guides in
src/content/guides/<section>/<slug>.md
-
Frontmatter:
title
(required),description
andorder
(optional) - Sections = folder names; display labels and order live in _sections.json
- Sorting: by
order
, then bytitle
Schema lives in content config. Browse existing files in the guides folder and copy the closest example.
Quick steps
- Open the guides folder.
- Copy an existing file in the right section; rename with a clear slug.
-
Edit the
title
and content; addorder
if you want to control position. - Open a PR. Weโll review quickly.
PR workflow (short)
Use the GitHub UI for quick edits, or develop locally with npm run dev
. Keep changes small and follow existing patterns. Link sources when
helpful.