Service Pages are simple gateway pages used to connect members and visitors to useful club services such as:
They are not ordinary content pages.
Their purpose is to give people a clear and controlled route into a service, and a clear route back afterwards.
We use Service Pages so that:
A Service Page is a shared gateway page.
It may be linked from:
The same Service Page can therefore be reused in more than one place.
The return rule is simple.
The user may return to the public website or to the members website, depending on where they came from.
The service page itself must still use the public/service layout. It must not expose normal member-hub navigation or sidebar controls.
The user returns to the public club website.
If the final public website later hosts the same service, these pages can be replaced with matching public URLs while preserving the same return principle.
Only return links to known club domains are allowed as explicit return pages.
Allowed return hosts are:
coulsdonclub.co.ukwww.coulsdonclub.co.ukcoulsdonclubmembers.infowww.coulsdonclubmembers.infoReturn links to unknown websites or unsafe locations must not be accepted.
This keeps the system secure and predictable.
Service Pages should be stored in a hidden folder outside the normal navigation structure.
They should:
They are utility pages, not reading pages.
A Service Page should be kept short and simple.
It normally contains:
That is all.
Examples include:
More may be added later using the same pattern.
All Service Pages should use one shared page template.
This ensures:
Volunteers should only need to change the page title, explanatory text, and service link.
When creating or editing a Service Page:
Service Pages are shared utility pages that:
The Service Gateway consists of a minimal set of pages, all using a single service-landing template, whose sole purpose is to route users to externally managed systems. No additional landing page templates will be created.