Here is an example. Note however that the latest change (enabling the anchor also for h1) somehow also enables it for the website title and subtitle... That is something to address.

This is due to the header and subheader being specified in default.html as

    <h1 class="project-name">{{ site.title }}</h1>
    <h2 class="project-tagline">{{ site.description }}</h2>

Since I opened this PR, I propose that someone else approves of it and merges it for release on the website.

How are you doing it?

I am doing it basically the same: I also have a gh-pages and a master branch on http://github.com/robertoostenveld/bids-website, where the master is the one I am rendering on https://robertoostenveld.github.io/bids-website. My idea right now (and far from ideal) was that I would try stuff in the master and revert (or delete and make a new master) when needed, just like you.

Note that so far I did most testing on my local laptop, which I already knew how to do (since the FT website is also based on Jekyll).

We definitely need a "neutral" place where PRs and/or branches can be rendered.