<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Contributing on Quollix</title><link>https://quollix.org/docs/community/contributing/</link><description>Recent content in Contributing on Quollix</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://quollix.org/docs/community/contributing/index.xml" rel="self" type="application/rss+xml"/><item><title>Glossary</title><link>https://quollix.org/docs/community/contributing/glossary/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quollix.org/docs/community/contributing/glossary/</guid><description>&lt;p&gt;This glossary defines preferred wording so terms are used consistently across the Quollix ecosystem.&lt;/p&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Term&lt;/th&gt;
 &lt;th&gt;Preferred Use&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;License key&lt;/td&gt;
 &lt;td&gt;Customer-facing credential used to activate Premium in a Quollix instance.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Signed license token&lt;/td&gt;
 &lt;td&gt;Signed proof returned by the license server and cached by Quollix for Premium validation.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;License server&lt;/td&gt;
 &lt;td&gt;Quollix service that validates license keys and issues signed license tokens.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;</description></item><item><title>Website</title><link>https://quollix.org/docs/community/contributing/website/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://quollix.org/docs/community/contributing/website/</guid><description>&lt;p&gt;The Quollix website is the canonical documentation hub for the Quollix ecosystem. It should help users and contributors find reliable, trustworthy information in one clear, searchable place.&lt;/p&gt;
&lt;p&gt;The website follows a text-first approach: content should be concise, well structured, searchable, easy to maintain, and accessible for anyone to improve through Markdown
contributions. Prefer text over images, audio, or video. Include non-text media only when they communicate information substantially better than text alone.&lt;/p&gt;</description></item></channel></rss>