<description>Code Quality A new release can happen at any time from th' main branch o' th' GitHub project without further acknowledgment. This makes it necessary that, every pushed set o' changesets into th' main branch must be self-contained an' correct, result'n 'n a releas'ble version.
Stay simple fer th' user by focus'n on th' mantra &ldquo;convent'n over configuration&rdquo;.
At installat'n th' ship should work reason'ble without (m)any configurat'n.
Stay close t' th' Cap'n Hugo way.</description>
<description>Semver This project tries t' follow th' semver policy - although not followed 100% 'n th' past.
Usually an entry o' Break'n on th' What&rsquo;s new plank causes a new major release number.
All other entries on th' What&rsquo;s new plank will increase th' minor release number.
Releases result'n 'n a new major or minor number be called main release.
Releases contain'n bugfixes only, be only increas'n th' patch release number.</description>
<description>Sometimes screenshots need t' be redone. This plank explains how t' create th' different screenshots, tools an' sett'ns
Common Creat'n:
Use English translat'n Empty search Remove history checkmarks but leave it on th' plank thats used fer th' screenshot Aft resize o' th' plank into th' required resolut'n, reload th' plank t' have all scrollbars 'n default load'n posit'n Demo Screenshot Rrrambl'n:
A meaningful full-screen screenshot o' an interest'n plank.</description>