<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hugo</title><link>https://caed2eb5.hugo-theme-liquid-demo.pages.dev/categories/hugo/</link><description>A privacy-safe demo of Hugo Theme Liquid for layout, typography, and progressive glass surfaces.</description><generator>Hugo -- gohugo.io</generator><language>zh-CN</language><atom:link href="https://caed2eb5.hugo-theme-liquid-demo.pages.dev/categories/hugo/index.xml" rel="self" type="application/rss+xml"/><item><title>Basic Markdown Test</title><link>https://caed2eb5.hugo-theme-liquid-demo.pages.dev/posts/basic-markdown-test/</link><pubDate>Fri, 28 Aug 2026 00:00:00 +0000</pubDate><guid isPermaLink="true">https://caed2eb5.hugo-theme-liquid-demo.pages.dev/posts/basic-markdown-test/</guid><description>An H1 Inside the Article This page is a deliberately ordinary Markdown document. It gives a theme a dependable baseline: a short sentence, a paragraph with enough texture to wrap across several lines, and a longer paragraph that lets us see whether the measure remains comfortable as the viewport changes. A good reading surface should make simple content feel unremarkable.&#10;Here is a normal paragraph with bold text, italic text, bold italic text, struck-through text, and inline code. The code is not decoration: it should sit on the same baseline as the words around it without making the line jump or becoming impossible to select.&#10;</description></item><item><title>Code Highlighting Showcase</title><link>https://caed2eb5.hugo-theme-liquid-demo.pages.dev/posts/code-highlighting-showcase/</link><pubDate>Tue, 25 Aug 2026 00:00:00 +0000</pubDate><guid isPermaLink="true">https://caed2eb5.hugo-theme-liquid-demo.pages.dev/posts/code-highlighting-showcase/</guid><description>How to Read This Page The examples are intentionally small. Their purpose is to reveal whether code blocks have the right font, padding, contrast, border, and scroll behavior—not to teach each language. Inline tokens such as hugo, content/posts/example.md, --accent-color, and npm run build should sit naturally inside paragraphs.&#10;HTML &amp;lt;article class=&amp;#34;post-card&amp;#34;&amp;gt; &amp;lt;h2&amp;gt;Readable by default&amp;lt;/h2&amp;gt; &amp;lt;p&amp;gt;Structure gives the stylesheet something meaningful to style.&amp;lt;/p&amp;gt; &amp;lt;/article&amp;gt; CSS .prose-article { max-width: 70ch; margin-inline: auto; overflow-wrap: anywhere; } @media (prefers-color-scheme: dark) { .prose-article { color: #edf4f1; } } JavaScript const headings = document.querySelectorAll(&amp;#39;article h2, article h3&amp;#39;); headings.forEach((heading) =&amp;gt; { heading.dataset.ready = &amp;#39;true&amp;#39;; }); TypeScript type Article = { title: string; tags: string[]; published: Date }; function label(article: Article): string { return `${article.title} · ${article.tags.length} tags`; } Go package main import &amp;#34;fmt&amp;#34; func main() { for _, word := range []string{&amp;#34;calm&amp;#34;, &amp;#34;clear&amp;#34;, &amp;#34;useful&amp;#34;} { fmt.Println(word) } } Python from dataclasses import dataclass @dataclass class Note: title: str published: bool = True print(Note(&amp;#34;A small content model&amp;#34;)) Rust fn main() { let pages = [&amp;#34;home&amp;#34;, &amp;#34;posts&amp;#34;, &amp;#34;about&amp;#34;]; for page in pages { println!(&amp;#34;/{page}/&amp;#34;); } } Bash #!/usr/bin/env bash set -euo pipefail hugo --gc --minify JSON { &amp;#34;title&amp;#34;: &amp;#34;Code Showcase&amp;#34;, &amp;#34;draft&amp;#34;: false, &amp;#34;features&amp;#34;: [&amp;#34;highlighting&amp;#34;, &amp;#34;overflow&amp;#34;, &amp;#34;contrast&amp;#34;] } YAML params: codeTheme: quiet showLineNumbers: false allowHorizontalScroll: true TOML baseURL = &amp;#34;https://example.test/&amp;#34; title = &amp;#34;A small documentation site&amp;#34; enableRobotsTXT = true Markdown ## A heading Write a paragraph with **emphasis** and `inline code`. SQL SELECT category, COUNT(*) AS post_count FROM content_index WHERE published_at &amp;lt;= CURRENT_DATE GROUP BY category ORDER BY post_count DESC; Long Code Line The next line is intentionally unreasonable. It should scroll inside the code block rather than widen the page or create horizontal overflow on the document itself.&#10;</description></item><item><title>Categories and Tags Test</title><link>https://caed2eb5.hugo-theme-liquid-demo.pages.dev/posts/categories-and-tags-test/</link><pubDate>Sat, 15 Aug 2026 00:00:00 +0000</pubDate><guid isPermaLink="true">https://caed2eb5.hugo-theme-liquid-demo.pages.dev/posts/categories-and-tags-test/</guid><description>Shared Terms Are the Test This article deliberately shares terms with several other test posts. A taxonomy page is more useful when it contains a small population with different counts, not when every term appears exactly once.&#10;The primary categories for this dataset are Development, Design, and Hugo. The post also uses tags for Hugo, CSS, Typography, Testing, and Static Site.&#10;What to Inspect Category links should remain readable when several appear together. Tag chips should wrap without widening the page. Taxonomy pages should show more than one post for shared terms. A term with a space, such as Web Development, should receive a stable URL. Counts and chronological order should make sense after new posts are added. A Small Editorial Note Taxonomy is metadata, but it still participates in the reading experience. It tells a visitor how a collection is shaped: a few broad shelves, a few recurring interests, and enough overlap to make exploration worthwhile. The everything showcase reuses this vocabulary so the aggregate pages feel like a real site rather than a set of isolated fixtures.&#10;</description></item><item><title>Everything Showcase</title><link>https://caed2eb5.hugo-theme-liquid-demo.pages.dev/posts/everything-showcase/</link><pubDate>Fri, 07 Aug 2026 00:00:00 +0000</pubDate><guid isPermaLink="true">https://caed2eb5.hugo-theme-liquid-demo.pages.dev/posts/everything-showcase/</guid><description>The Surface of a Modern Hugo Theme A modern Hugo theme begins with an old-fashioned question: what should this page help a person do? The answer might be read a careful essay, find a related note, understand when something was published, or decide whether a link is worth opening. Visual polish matters, especially when a theme uses soft translucency and layered surfaces, but polish is most convincing when it follows a clear content structure.&#10;</description></item></channel></rss>