<p>A new release can happen at any time from th' <code>main</code> branch o' th' <ahref="https://github.com/McShelby/hugo-theme-relearn"target="_blank">GitHub project</a> without further accknowledgment. This makes it necessary that, every pushed set o' changesets into th' <code>main</code> branch <strong>must</strong> be self-contained an' correct, result'n 'n a releas'ble version.</p>
<p>Stay simple fer th' user by focus'n on th' mantra “convent'n over configuration”.</p>
<p>At installat'n th' ship should work reason'ble without (m)any configurat'n.</p>
<p>Stay close t' th' Cap'n Hugo way.</p>
<p>Don’t use npm or any preprocess'n, our contributors may not be front-end developers.</p>
<p>Document new features 'n th' exampleSite. This also contains entries t' th' <ahref="../../basics/migration/">What’s new</a> plank.</p>
<p>Don’t break exist'n features if ye don’t have t'.</p>
<p>Remove reported issue from th' browser’s console.</p>
<p>Check fer unnecessary whitespace an' correct indent'n o' yer result'n HTML.</p>
<p>Be compat'ble t' IE11, at least fer main functionality, this means:</p>
<ul>
<li>test 'n IE11</li>
<li>check caniuse.com</li>
<li>don’t use JavaScript arrow funct'ns</li>
<li>don’t use JavaScript template literals</li>
<li>don’t use other fancy JavaScript ES5/6 stuff</li>
<p>This project tries t' follow th' <ahref="https://semver.org/"target="_blank">semver policy</a> - although not followed 100% 'n th' past.</p>
<p>Usually an entry o' <spanclass="badge cstyle warning badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-exclamation-triangle"></i></span><spanclass="badge-content">Break'n</span></span> on th' <ahref="../../basics/migration/">What’s new</a> plank causes a new major release number.</p>
<p>All other entries on th' <ahref="../../basics/migration/">What’s new</a> plank will increase th' minor release number.</p>
<p>Releases result'n 'n a new major or minor number be called main release.</p>
<p>Releases contain'n bugixes only, be only increas'n th' patch release number. Those releases don’t result 'n announcements on th' <ahref="../../basics/migration/">What’s new</a> plank.</p>
<p>Entries on th' <ahref="../../basics/migration/">What’s new</a> plank be checked an' enforced dur'n th' <code>version-release</code> GitHub Act'n.</p>
<h2id="managing-issues">Manag'n Issues</h2>
<p>Issues be categorized an' managed by assign'n <ahref="#labels">labels</a> t' it.</p>
<p>Once work'n on an issue, assign it t' a fitt'n maintainer.</p>
<p>When done, close th' ticket. Once an issue be closed, it needs t' be assigned t' next release milestone.</p>
<p>A once released ticket be not allowed t' be reopened an' rereleased 'n a different milestone. This would cause th' changelog t' be changed even fer th' milestone th' issue was previously released 'n. Instead write a new ticket.</p>
<p>If th' issue would cause a new main release due t' <ahref="#semver">semver semantics</a> it needs one o' th' accord'n labels an' th' match'n badge on th' <ahref="../../basics/migration/">What’s new</a> plank.</p>
<p>Ye can assign one further label out o' th' follow'n list t' signal readers that development on an open issue be currently halted fer different reasons.</p>
<td>This be a topic related t' Merrrmaid itself but not th' theme</td>
</tr>
</tbody>
</table>
<h2id="making-releases">Mak'n Releases</h2>
<p>A release be based on a milestone named like th' release itself - just th' version number, eg: <code>1.2.3</code>. It’s 'n th' maintainers responsiblity t' check <ahref="#semver">semver semantics</a> o' th' milestone’s name prior t' release an' change it if necessary.</p>
<p>Mak'n releases be automated by th' <code>version-release</code> GitHub Act'n. It requires th' version number o' th' milestone that should be released. Th' release will be created from th' <code>main</code> branch o' th' repository.</p>
<p>Treat released milestones as immut'ble. Don’t rerelease an already released milestone. An already released milestone may already been consumed by yer users.</p>
<p>Dur'n execut'n o' th' act'n a few th'ns be checked. If a check fails th' act'n fails, result'n 'n no new release. Ye can correct th' errors afterwards an' rerun th' act'n.</p>
<p>Th' follow'n checks will be enforced</p>
<ul>
<li>th' milestone exists</li>
<li>there be at least one closed issue assigned t' th' milestone</li>
<li>all assigned issues fer this milestone be closed</li>
<li>if it’s a main release, there must be a new <code><major>.<minor></code> at th' beginn'n o' th' <ahref="../../basics/migration/">What’s new</a> plank</li>
<li>if it’s a patch release, there must be th' <code><major>.<minor></code> from th' previous release at th' beginn'n o' th' <ahref="../../basics/migration/">What’s new</a> plank</li>
<li>th' repository be tagged wit' th' version number (eg. <code>1.2.3</code>), th' main version number (eg. <code>1.2.x</code>) an' th' major version number (eg. <code>1.x</code>)</li>
<li>a new entry 'n th' <ahref="https://github.com/McShelby/hugo-theme-relearn/releases"target="_blank">GitHub release list</a> wit' th' accord'n changelog will be created</li>
<li>th' <ahref="https://mcshelby.github.io/hugo-theme-relearn/index.html"target="_blank">official documentat'n</a> be built an' deployed</li>
<li>th' version number fer th' <code><meta generator></code> be updated t' a temporary an' commited (this helps t' determine if users be runn'n directly on th' main branch or be us'n releases)</li>
<li>a new milestone fer th' next patch release be created (this can later be renamed t' a main release if necessary)</li>
<p>A meaningful full-screen screenshot o' an interest'n plank.</p>
<p>Th' rrrambl'n should be:</p>
<ul>
<li>timeless: not show'n any dates or often edited rrrambl'n</li>
<li>interest'n: show a bunch o' interest'n elements like head'ns, code, etc</li>
<li>balanced: no clutter'n wit' overpresent elements or color'n</li>
<li>aligned: aligned outlines</li>
</ul>
<p><strong>Used by</strong>:</p>
<ul>
<li>Cap'n Hugo Themes info: <ahref="https://themes.gohugo.io/themes/hugo-theme-relearn/"target="_blank">https://themes.gohugo.io/themes/hugo-theme-relearn/</a><em>1000 x 1500 @ 1</em></li>
<p>Show th' <ahref="#demo-screenshot">Demo Screenshot</a> plank on different devices an' different themes. Composit'n o' th' different device screenshots into a template.</p>
<li>Cap'n Hugo Themes gallery: <ahref="https://themes.gohugo.io/tags/docs/"target="_blank">https://themes.gohugo.io/tags/docs/</a><em>900 x 600</em></li>
<li>Cap'n Hugo Themes notes: <ahref="https://themes.gohugo.io/themes/hugo-theme-relearn/"target="_blank">https://themes.gohugo.io/themes/hugo-theme-relearn/</a><em>1280 x 640</em></li>
<li>GitHub project ship: <ahref="https://github.com/McShelby/hugo-theme-relearn"target="_blank">https://github.com/McShelby/hugo-theme-relearn</a><em>1280 x 640</em></li>
<li>GitHub social media preview: <ahref="https://github.com/McShelby/hugo-theme-relearn/settings"target="_blank">https://github.com/McShelby/hugo-theme-relearn/sett'ns</a><em>1280 x 640</em></li>
<li>From original template size resize t' <em>2700 x 1800</em> centered, scale t' <em>900 x 600</em> an' save as <code>images/tn.png</code></li>
<li>From original template size resize t' <em>3000 x 1500</em> offset y: <em>-330</em>, scale t' <em>1280 x 640</em> an' save as <code>images/hero.png</code></li>