Skip to content

🖌 Document CAP & SEP reference style #2736

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
JFWooten4 wants to merge 2 commits into
base: main
Choose a base branch
from
+1 −0
Open

🖌 Document CAP & SEP reference style #2736

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b7af44f
📝 Document SEP reference style
JFWooten4 Aug 6, 2026
c9c1ab2
📝 Add CAP reference style guidance
JFWooten4 Aug 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,7 @@ A husky pre-commit hook runs the prettier check; if it fails, run `pnpm format:m
### Terminology and style

- "Stellar network" — lowercase *network*. Likewise *asset* and *anchor* are not capitalized.
- Write SEP and CAP references without zero-padding (for example, `SEP-1` and `CAP-1`, not `SEP-0001` and `CAP-0001`). Keep canonical filenames and URLs unchanged (for example, `sep-0001.md` and `cap-0001.md`).
- Meeting notes (in `meetings/`) use the date as the title (`2026-05-07`), uniformly across the series.

## Site Code and Infrastructure
Expand Down