Speed and privacy

One stylesheet and one script, minified, loaded only on the pages that use them. No jQuery, no fonts fetched from anywhere, nothing requested from a third party.

Article views are counted by the page once it has loaded, so an article served from a page cache is counted like any other. The browser remembers for a day which articles it has counted, so the same reader is not counted twice; no cookie is set, which matters because most page caches will not store a page that sets one. Search engines and people who can write articles are not counted. Feedback votes store a number against a post and nothing about who voted. The notes readers write after a No keep the words and the time, and nothing about who wrote them. Unanswered searches keep the words and nothing about who typed them.

A customer's conversation, and the page holding the form, tell page caches not to store them. A stored conversation would not show a reply the customer had just sent, and a stored form carries a security token that expires. The rest of the help centre is cached as usual. When the first article or FAQ is published, or the last one taken down, the page caches we know about are emptied so the help centre's front page changes with it. Other code can listen for the trhc_purge_caches action.