<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docsy Kitchen Sink on Docsy example</title><link>https://projectious-work.github.io/brand/v2.1.0/examples/hugo-docsy/</link><description>Recent content in Docsy Kitchen Sink on Docsy example</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://projectious-work.github.io/brand/v2.1.0/examples/hugo-docsy/index.xml" rel="self" type="application/rss+xml"/><item><title>Kitchen sink</title><link>https://projectious-work.github.io/brand/v2.1.0/examples/hugo-docsy/docs/kitchen-sink/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://projectious-work.github.io/brand/v2.1.0/examples/hugo-docsy/docs/kitchen-sink/</guid><description>&lt;blockquote&gt;
&lt;p&gt;This page is mounted from &lt;code&gt;examples/shared/kitchen-sink.md&lt;/code&gt; into &lt;strong&gt;both&lt;/strong&gt; the
Docsy and the Hextra example. The markup and the stylesheet behind it are the
same files the documentation site uses, so any difference you see between the
two examples is a difference between the &lt;em&gt;themes&lt;/em&gt; — not between three
divergent copies of the brand.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Every specimen on this page is live markup styled by the brand tokens, ported
from &lt;code&gt;brand/html/projectious-kitchen-sink.html&lt;/code&gt;. They follow your colour mode —
switch the theme and they change with the documentation.&lt;/p&gt;</description></item><item><title>First steps</title><link>https://projectious-work.github.io/brand/v2.1.0/examples/hugo-docsy/docs/guide/first-steps/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://projectious-work.github.io/brand/v2.1.0/examples/hugo-docsy/docs/guide/first-steps/</guid><description>&lt;h2 id="a-gentle-beginning"&gt;A gentle beginning&lt;/h2&gt;
&lt;p&gt;Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur feugiat
semper sapien, sed pretium nibh consequat quis. Donec vitae sem non arcu
placerat tincidunt.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Tip&lt;/div&gt;


Small, explicit pages are easier to scan, link, and maintain.
&lt;/div&gt;

&lt;p&gt;&lt;a href="https://projectious-work.github.io/brand/v2.1.0/examples/hugo-docsy/docs/kitchen-sink/"&gt;Open the kitchen sink&lt;/a&gt;{.btn .btn-primary}&lt;/p&gt;
&lt;h2 id="quote"&gt;Quote&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;Documentation is a conversation between a product and its future users.&lt;/p&gt;
&lt;/blockquote&gt;</description></item><item><title>Dashboard mockup</title><link>https://projectious-work.github.io/brand/v2.1.0/examples/hugo-docsy/docs/dashboard/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://projectious-work.github.io/brand/v2.1.0/examples/hugo-docsy/docs/dashboard/</guid><description>&lt;p&gt;A whole application screen, built only from components this theme already
renders elsewhere. It is the worked example behind the brand&amp;rsquo;s
&lt;a href="https://projectious-work.github.io/brand/docs/interface/patterns/"&gt;composed patterns&lt;/a&gt;
page: a page shell, a KPI row, and a primary/secondary split.&lt;/p&gt;
&lt;p&gt;This page is mounted from &lt;code&gt;examples/shared/dashboard.md&lt;/code&gt; into &lt;strong&gt;both&lt;/strong&gt; the Docsy
and the Hextra example, and the specimen itself is one shortcode shared with the
documentation site. Any difference between the two examples is therefore a
difference between the themes.&lt;/p&gt;</description></item><item><title>Review specimen</title><link>https://projectious-work.github.io/brand/v2.1.0/examples/hugo-docsy/docs/review-specimen/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://projectious-work.github.io/brand/v2.1.0/examples/hugo-docsy/docs/review-specimen/</guid><description>&lt;p&gt;This is the Docsy review fixture described in the brand&amp;rsquo;s
&lt;a href="https://projectious-work.github.io/brand/docs/themes/hugo/"&gt;Hugo theme guidance&lt;/a&gt;.
It exercises the states a theme has to prove before it can be approved:
hierarchy, link behaviour, callouts, cards, code, status, and one primary
action. Compare it against the Hextra fixture in &lt;code&gt;examples/hugo-hextra/&lt;/code&gt; — the
two use the same content states, so a migration compares like with like.&lt;/p&gt;
&lt;div class="alert alert-info" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Release boundary&lt;/div&gt;
&lt;p&gt;Validate the configuration locally, then request promotion. The action below is
the only primary action in this view.&lt;/p&gt;</description></item></channel></rss>