<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Project on Mergeway</title><link>https://mergewayhq.github.io/docs/project/</link><description>Recent content in Project on Mergeway</description><generator>Hugo</generator><language>en</language><atom:link href="https://mergewayhq.github.io/docs/project/index.xml" rel="self" type="application/rss+xml"/><item><title>Documentation authoring</title><link>https://mergewayhq.github.io/docs/project/documentation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://mergewayhq.github.io/docs/project/documentation/</guid><description>&lt;h1 id="documentation-authoring"&gt;Documentation authoring&lt;a class="anchor" href="#documentation-authoring"&gt;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;The website uses Hugo Book and organizes canonical documentation by reader need. Put pages under exactly one of &lt;code&gt;tutorials&lt;/code&gt;, &lt;code&gt;how-to&lt;/code&gt;, &lt;code&gt;reference&lt;/code&gt;, or &lt;code&gt;explanation&lt;/code&gt;; component hubs orient readers and link to those canonical pages.&lt;/p&gt;
&lt;h2 id="required-front-matter"&gt;Required front matter&lt;a class="anchor" href="#required-front-matter"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Every page must define a useful &lt;code&gt;title&lt;/code&gt; and &lt;code&gt;description&lt;/code&gt;, use &lt;code&gt;type: docs&lt;/code&gt;, and set a &lt;code&gt;weight&lt;/code&gt; in increments of ten. Section indexes follow the same convention. Use &lt;code&gt;bookToC: true&lt;/code&gt; unless a short page has no useful second-level headings. New substantive pages should also declare their &lt;code&gt;mode&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>GitHub</title><link>https://mergewayhq.github.io/docs/project/github/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://mergewayhq.github.io/docs/project/github/</guid><description>&lt;p&gt;&lt;a href="https://github.com/mergewayhq/mergeway-cli"&gt;GitHub repository&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Releases</title><link>https://mergewayhq.github.io/docs/project/releases/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://mergewayhq.github.io/docs/project/releases/</guid><description>&lt;p&gt;&lt;a href="https://github.com/mergewayhq/mergeway-cli/releass"&gt;GitHub Releases&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Contributing</title><link>https://mergewayhq.github.io/docs/project/contributing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://mergewayhq.github.io/docs/project/contributing/</guid><description>&lt;h1 id="contributing"&gt;Contributing&lt;a class="anchor" href="#contributing"&gt;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Mergeway accepts changes through its public GitHub repository. Before starting a substantial behavior change, open or find an issue so the intended specification and compatibility impact are visible.&lt;/p&gt;
&lt;h2 id="prepare-a-change"&gt;Prepare a change&lt;a class="anchor" href="#prepare-a-change"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Enter the pinned development environment with &lt;code&gt;devenv shell&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Make a focused change with tests at the layer that owns the behavior.&lt;/li&gt;
&lt;li&gt;Run the relevant focused checks, then &lt;code&gt;make fmt-check&lt;/code&gt; and &lt;code&gt;go test ./...&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Run &lt;code&gt;make website-check&lt;/code&gt; when user behavior, examples, commands, protocols, or documentation change.&lt;/li&gt;
&lt;li&gt;Explain the user-documentation impact in the pull request, including “no documentation impact” when appropriate.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Detailed prerequisites, package ownership, build/debug commands, release mechanics, and the temporary mdBook/Hugo dual-site workflow live in &lt;a href="https://github.com/mergewayhq/mergeway-cli/blob/main/DEVELOPING.md"&gt;&lt;code&gt;DEVELOPING.md&lt;/code&gt;&lt;/a&gt;. Keeping volatile commands there lets this page remain a concise public entry point.&lt;/p&gt;</description></item><item><title>MIT License</title><link>https://mergewayhq.github.io/docs/project/license/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://mergewayhq.github.io/docs/project/license/</guid><description>&lt;p&gt;&lt;a href="https://github.com/mergewayhq/mergeway-cli/blob/main/LICENSE.md"&gt;MIT License&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>