Skip to content

Document conventions used in construction of website#157

Open
cornelius wants to merge 2 commits into
mainfrom
website-conventions
Open

Document conventions used in construction of website#157
cornelius wants to merge 2 commits into
mainfrom
website-conventions

Conversation

@cornelius
Copy link
Copy Markdown
Member

No description provided.

Comment thread AGENTS.md
Comment on lines +29 to +30
- Use `{{</* relurl "path" */>}}` for static file links (never hardcoded absolute paths)
- Use `{{</* relref "/page" */>}}` for internal page links
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I hope agents will interpret this correctly, as a copy-paste version of this shortcode leads to an inactive shortcode AFAIK.

Comment thread AGENTS.md

## Commit conventions

Conventional commits. Scope is typically the area affected: `content`, `theme`, `data`, `ci`, `static`.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some content changes will involve static and content changes, sometimes in addition data. Does it make sense like this? Wouldn't topic scope rather make sense, e.g. feat(news): whatever?

Comment thread CONVENTIONS.md
Always use the `relurl` shortcode for links to files in `static/`:

```markdown
[Download PDF]({{</* relurl "documents/my-file.pdf" */>}})
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned above, this snippet doesn't work AFAIK.

@github-actions
Copy link
Copy Markdown

Pull Request Live Preview


🚀 View preview at
https://web-preview.openrailassociation.org/main-pr-157/

Last updated: 2026-05-13 15:24:29 UTC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants