Khalid 1.3.2: fixes we found by testing this blog in three browsers

Khalid 1.3.2 came out on 4 November 2026. Before this Khalid release, we tested every page of this blog in Chrome, Firefox and Safari. We used phone, tablet and desktop widths. This release fixes each fault we found, and a new check now looks for them before every release. The update is free.

What is new in Khalid 1.3.2? #

Khalid 1.3.2 adds four things readers can see. There is a trail of links above each page and a feed for each category. The home page's topic tabs and video row now show pictures. Finally, a short note can say why a post was updated. Breadcrumbs and update notes are on by default in Keystone.

• Breadcrumbs. A short trail of links from the front page sits above each post, page, list and author page. For example, you can see it above this post.
• A feed for each category. Each category now has its own RSS, Atom and JSON feed, such as the AI search feed. As a result, a reader can follow one topic instead of the whole blog.
• Pictures in topic tabs and the video row. The home page groups posts by topic in tabs, and posts with a video get their own row. Both now show each post's picture and the author's photo.
• Update notes. When you change a post, a short updated_note tells readers what changed, under the date.
• More related posts. Keystone now shows five related posts under each post by default, instead of three.

Which faults does the new release fix? #

The new release fixes layout faults that showed in one browser or at one width. So most readers never saw all of them. However, each one made a page look broken to someone. This release also fixes video in Safari. Safari asks for a video in small parts, and older versions sent the whole file, so the video never started.

These are the faults a reader would notice:

• On a wide screen, the side contents list no longer runs over the lead picture or a wide table.
• On a phone, the Contents button no longer floats over the text. Instead, it sits at the start of the post.
• The tick and cross in a pros and cons list no longer cover the first letters of each line.
• Videos now play in Safari, and CSV downloads open with the right file type.
• The comment form has borders in Safari, like the other forms.

The full list is in Khalid's change log.

How does Khalid stop these faults coming back? #

Khalid now runs a layout check before every release. It opens the demo pages in Chrome, Firefox and Safari at three widths. The release stops if text covers text, a marker covers words, a page scrolls sideways or a picture fails. Because the check names the browser and the width, each fault is quick to find and fix.

This blog also runs a check of its own. It opens every page type in the same three browsers. It fails if anything overlaps, is cut off or does not work.

Are the writing checks fairer now? #

Yes. With this release, two writing checks warn less often when nothing is wrong. For example, a good short answer followed by more detail no longer warns. A step count or a date no longer counts as a statistic, either. Links also work inside tables, and saved settings take effect without a restart. So writers see fewer warnings.

• The short-answer check looks only at the first paragraph under a question heading.
• The statistics check warns only about real statistics, such as a percentage or a figure from a study.
• A link with its own words, such as [[slug|words]], now works inside a table cell.
• When you save site.toml or a theme file, the blog uses it at once. If the file has a mistake, the blog keeps the last good version.

How do I update to Khalid 1.3.2? #

To update, download the program for your computer from the release page on GitHub. You can also use the Docker image tagged 1.3.2. Then replace the old program and start it again. Your posts, comments and settings stay exactly as they were, because the update only changes the program.

To see each Khalid feature working on a real blog, read our tour of this blog's features.