Website Guide

Overview

The website is built from Markdown files stored in a GitHub repository. Changes made via the Content Management System (CMS) (or directly in GitHub) are automatically built and deployed to the live site within a minute or two.

Not sure how to make a change? Raise a GitHub issue

If you’re unsure how to make a change, or the page you want to update is complex (events pages, pages with booking links, galleries, or anything with special formatting), the best thing to do is raise a GitHub issue describing what needs changing. The IT Officer will pick it up.

Raise an issue on GitHub →

You don’t need a GitHub account to view existing issues, but you’ll need one to create new ones. If you don’t have one, email the IT Officer instead.

This is not a last resort — it’s a completely normal way to contribute. A clear description of what’s wrong or out of date is genuinely useful, even if you could also fix it yourself.

Logging in to the CMS

1. Go to /admin/
2. Click Login with GitHub
3. You’ll need a GitHub account that has been added as a collaborator on the brightontri-website repository. Ask the IT Officer to add you if needed.

What can be edited via the CMS

The CMS is organised into collections:

Pages outside these collections (About, Committee, Join, Kit etc.) can be edited directly in GitHub, or raise an issue and ask the IT Officer.

Editing an existing page

1. Log in to the CMS
2. Click the relevant collection in the left sidebar
3. Click the page you want to edit
4. Make your changes in the editor
5. Click Save — the change is committed to GitHub and the site rebuilds automatically

The editor has a Rich Text mode (like a word processor) and a Markdown mode. Either works; use whichever you’re comfortable with.

Writing a blog post

1. In the CMS, click Blog in the sidebar
2. Click New Blog (top right)
3. Fill in:
   • Title — shown as the page heading and in the blog index
   • Date — defaults to today
   • Description — a short summary shown in previews (optional but recommended)
   • Body — the post content
4. Click Save

Training blog posts work the same way via the Training Blog collection.

Adding photos to a page (gallery)

Pages can include a photo gallery using the gallery shortcode. To add one, switch the editor to Markdown mode and add:

{{< gallery >}}
/images/your-folder/photo1.jpg
/images/your-folder/photo2.jpg
{{< /gallery >}}

Photos must be uploaded to the repository first and converted to JPEG at a reasonable size — see the IT Officer. The gallery renders as a responsive three-column grid.

Refreshing the coaches list

The coaches page is generated from the private coaching planner spreadsheet. To update it after coaches join, leave, or change qualification, ask the IT Officer to run the /refresh-coaches command.

Member-only areas

The Discounts, Resources for Coaches, and Resources for Committee sections are hidden behind a MembershipWorks member login — any current member who logs in can view them. The hiding is cosmetic (the content is still in the page source), so don’t publish genuinely sensitive material here; use Google Drive for that.

There is nothing to administer per person: access follows MembershipWorks membership automatically.

Getting help

For anything beyond straightforward text edits, raise a GitHub issue (link at the top of this page) or contact the IT Officer (currently Rob Jessop).