Fixtures on your own website

Settings → Connect a Website. Standard and above. Each panel is one line of HTML you paste into the club’s existing website, wherever that site takes HTML. It fetches from Pavilion when somebody loads the page, so it is never out of date — and nobody has to keep two fixture lists in step.

There are six: next fixtures, latest results, what’s on, the green this week, club notices and club details.

🔓 It is public, on purpose

The panels need no key and no sign-in. A fixture list pinned inside the clubhouse is not a secret, and a panel that needs a password is a panel that stops working the day somebody changes it. That puts the whole weight on what goes in, so each panel is deliberately narrow:

• Events appear only where the event is marked public — the same rule as your own public events page. Worth knowing that events are public unless somebody says otherwise, so if a committee meeting turns up on your website, untick “public” on that event.
• Notices are off until you turn them on. A noticeboard is written in the tone of somewhere internal even when nothing on it is confidential. Read yours before ticking it.
• The green says how many rinks are free on each of the next seven days, and never who booked them.
• Names are left out unless you tick the box. A team sheet on the club’s own site is perfectly ordinary — but that is the club’s decision to make on behalf of three hundred people, not a default to inherit.

🎨 Making it match your site

Set the colour and, if your website has a dark background, tick that box. The panels bring their own styling scoped to themselves, so they cannot restyle the rest of your site by accident — a stylesheet arriving uninvited on somebody else’s page has no business touching anything but its own panel.

To show a different number of rows in one place, add data-limit="3" to that panel’s <div>. To give it a heading, add data-title="Next fixtures".

🕔 When it updates

Within five minutes of a change. Not instantly — a fixture list is not a share price, and asking the club’s server for it afresh on every page view would be a poor trade for four minutes.

🙈 When something goes wrong

The panel leaves the space exactly as it was and says nothing. A club’s website should never carry a red error box because a system it does not host was briefly unreachable. If a panel shows “nothing to show just yet”, that is not a fault: it is the honest answer when there are no fixtures, which in February there will not be.

Common questions

Where exactly do I paste it?

Any block on your website that accepts HTML. Wix calls it Embed → Embed a widget → HTML iframe; Squarespace calls it a Code block; WordPress calls it Custom HTML; a hand-written site takes it anywhere in the page.

The panel is blank.

Check there is something to show in Pavilion first — an empty fixture list shows as empty, correctly. Then check the block you pasted into is an HTML block rather than a text block, since a text block will show the code as words instead of running it.

Can I put more than one on a page?

Yes. Paste the div for each; the script only needs to be on the page once, and a second copy is harmless.

Will this slow our website down?

Barely. It is a few kilobytes and it loads after your page has drawn, so your site appears at its normal speed whatever Pavilion is doing.

Our results are not showing.

Only fixtures marked completed with a score entered appear. A fixture marked completed with nothing typed in shows no score rather than “0 – 0”, which would read as a scoreless draw.

We took the club onto a new website. Do we redo anything?

Just paste the same lines into the new site. Nothing is tied to the address your website is served from, deliberately — the alternative was a list of approved domains that breaks silently the day a club adds “www” and protects nothing, because the information is public anyway.