A tour of every Khalid feature in this demo

This blog, Larkspur Ledger, is the demo of Khalid, an open-source blog engine. Larkspur Studio, its people and its benchmark are made up. The advice is real.

Each line below names one feature and links to a page where you can see it. Open any link, look, and come back.

Long guides and topic hubs

• Flagship guides with every block: keyword research, content strategy, technical SEO audit, internal linking, AI search and choosing SEO tools.
• A topic hub for each section: a pillar guide linked to and from every post in its cluster, such as the SEO writing guide.
• Sections, tags and an archive: the SEO tools section, the tools tag and the archive of every post.
• A series as a course: seven lessons in SEO writing, in order.
• Editor's picks: posts marked as featured appear first on the home page.

Blocks a writer can use

• Key takeaways, tips, notes, warnings, further reading and big numbers: all six boxes in the keyword research guide.
• A table of contents: at the top of the technical SEO audit.
• Figures and charts with captions: the content benchmark.
• A gallery of screenshots: the Quillmeter review.
• Tables, including one that folds its long rows away: writing headlines.
• Pros and cons: the Quillmeter review.
• Side-by-side columns: Search Console against Bing Webmaster Tools.
• Quotes: the content strategy guide.
• Step-by-step how-to: set up Google Search Console.
• Questions and answers: the end of the XML sitemaps post.
• A section that opens on click: the transcript in the podcast episode.
• A section banner between parts: the choosing SEO tools guide.
• Code with highlighting: the robots file and headers in the technical SEO audit.
• Formulas: the median in the benchmark data page.
• Footnotes: the internal linking guide.
• Link cards to other sites: the best free SEO tools.
• Buttons: the meta description guide.
• A file to download: the planning sheet in our content calendar post.
• A reusable snippet, written once and placed in two posts: the method note in the content benchmark.
• A product card with price and rating: the tools we use.
• A business card with address and map details: about Larkspur.
• A self-hosted video with its poster: the animation in the technical SEO audit.
• A video from YouTube, played through its privacy player: notes on debugging INP.
• An audio player: the podcast episode.
• The site's call to action in a post: the AI search guide.
• A newsletter sign-up: the end of almost every guide, such as internal linking.
• A contact form: the contact page.

Comments, sign-ups, forms, members-only parts and search need Khalid running as a server. The published demo is a set of static files, so in those places it shows a short note instead.

• Glossary links: links such as the one on "answer capsule" in how AI search picks its sources, which open the answer capsule entry.

Search results features

Each page carries structured data, the code search engines read to understand it. You can see it with Google's Rich Results Test.

• Article, author, publisher and breadcrumbs: on every post, such as the SEO writing guide.
• FAQ: the AI search guide.
• How-to: set up Google Search Console.
• Review with a rating: the Quillmeter review.
• Ranked list: the best free SEO tools.
• Comparison, shaped the way the linter asks: Search Console against Bing Webmaster Tools.
• Fact check: word count is not a ranking factor
• Dataset: the benchmark data.
• Course: the SEO writing course.
• Podcast episode: episode one.
• Video: the animation in the technical SEO audit.
• News article, with its own news sitemap: our benchmark data is free to download.
• Product: the tools we use.
• Local business: about Larkspur.

Trust and people

• Author pages with photo, role, credentials and profile links: Dalia Moreno and all four authors.
• Reviewed by a second editor: shown under the title of each guide, such as content strategy.
• Updated dates with a note on what changed: the AI search guide.
• Co-authors: the podcast episode.
• An editorial policy: how we write and check.
• Members-only posts and gated sections: the content brief template, and the full tables in the content benchmark.
• Comments: under every post when Khalid runs as a server, which is how this site is set up.

Reading and finding

• Search: the search page, also opened with the slash key, finds posts as you type when Khalid runs as a server. The published demo is static, so it says search is off.
• Related posts and the posts that link here: the end of any post, such as content refresh.
• Link previews: point at a link to another post, such as the ones in the SEO writing guide.
• Another language, with the language switch and hreflang: the German blog, and Core Web Vitals in both languages.
• Feeds: RSS, Atom and JSON Feed.
• Sitemaps for search engines and a sitemap for people: the sitemap page.
• A page for AI tools: for readers and AI, with the site's summary in llms.txt.

Ten looks for the same blog

The same posts, built with each of Khalid's templates: Almanac, Atlas, Compass, Folio, Harbor, Keystone, Ledger, Meridian, Wire and Workbench.

What you cannot see on a page

• A linter that refuses a weak post: every post here passes khalid lint with no warning. It checks titles, descriptions, links, sources for numbers, glossary links, answers under question headings and more.
• A site audit: the built blog passes khalid audit, the same kinds of checks the big SEO tools run.
• An admin, an API and command-line tools: the editor offers every block on this page. See Khalid on GitHub to run your own.