<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Comments on Liquid Stack</title><link>https://liquid-stack.pages.dev/tags/comments/</link><description>Recent content in Comments on Liquid Stack</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>My Blog</copyright><lastBuildDate>Wed, 22 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://liquid-stack.pages.dev/tags/comments/index.xml" rel="self" type="application/rss+xml"/><item><title>Configure Waline Comments</title><link>https://liquid-stack.pages.dev/p/configure-waline-comments/</link><pubDate>Wed, 22 Jul 2026 00:00:00 +0000</pubDate><guid>https://liquid-stack.pages.dev/p/configure-waline-comments/</guid><description>&lt;p&gt;Liquid Stack keeps the Waline comment component, while its example URL is not connected to a real backend.&lt;/p&gt;
&lt;h2 id="prepare-a-server"&gt;Prepare a server
&lt;/h2&gt;&lt;p&gt;Deploy your own service by following the official Waline documentation. When you have its URL, replace the sample value at &lt;code&gt;params.comments.waline.serverURL&lt;/code&gt; in &lt;code&gt;hugo.yaml&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id="enable-or-disable-comments"&gt;Enable or disable comments
&lt;/h2&gt;&lt;p&gt;Set &lt;code&gt;params.comments.enabled&lt;/code&gt; to &lt;code&gt;true&lt;/code&gt; to enable comments. Individual posts can still use &lt;code&gt;comments: false&lt;/code&gt;, which is useful for privacy pages, documentation, or announcements.&lt;/p&gt;
&lt;h2 id="test-before-release"&gt;Test before release
&lt;/h2&gt;&lt;p&gt;Check that the comment box appears below a post locally, then test submission, moderation, and notifications after deployment. Keep server URLs, tokens, and administrator settings in your own environment rather than in a public theme example.&lt;/p&gt;</description></item></channel></rss>