Contributing

Code Quality

A new release can happen at any time from th' main branch o' th' GitHub project without further accknowledgment. 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 “convent'n over configuration”.

At installat'n th' ship should work reason'ble without (m)any configurat'n.

Stay close t' th' Cap'n Hugo way.

Don’t use npm or any preprocess'n, our contributors may not be front-end developers.

Document new features 'n th' exampleSite. This also contains entries t' th' What’s new plank.

Don’t break exist'n features if ye don’t have t'.

Remove reported issue from th' browser’s console.

Check fer unnecessary whitespace an' correct indent'n o' yer result'n HTML.

Be compat'ble t' IE11, at least fer main functionality, this means:

• test 'n IE11
• check caniuse.com
• don’t use JavaScript arrow funct'ns
• don’t use JavaScript template literals
• don’t use other fancy JavaScript ES5/6 stuff

Conventional Commits

Write commit messages 'n th' conventional commit format.

Follow'n be an impomplete list o' some o' th' used conventional commit types. Be creative.

Maintaining

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’s new plank causes a new major release number.

All other entries on th' What’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 bugixes only, be only increas'n th' patch release number. Those releases don’t result 'n announcements on th' What’s new plank.

Entries on th' What’s new plank be checked an' enforced dur'n th' version-release GitHub Act'n.

Manag'n Issues

Issues be categorized an' managed by assign'n labels t' it.

Once work'n on an issue, assign it t' a fitt'n maintainer.

When done, close th' ticket. Once an issue be closed, it needs t' be assigned t' next release milestone.

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.

Manag'n Pull Requests

If a PR be merged an' closed it needs an accompanied issue assigned t'. If there be no issue fer a PR, th' maintainer needs t' create one.

Ye can assign multiple PRs t' one issue as long as they belong together.

Usually set th' same labels an' milestone fer th' PR as fer th' accompanied issue.

Labels

Kind

An issue that results 'n changesets must have exactly one o' th' follow'n labels. This needs t' be assigned latest before release.

Impact

If th' issue would cause a new main release due t' semver semantics it needs one o' th' accord'n labels an' th' match'n badge on th' What’s new plank.

Declinat'n

If an issue does not result 'n changesets but be closed anyways, it must have exactly one o' th' follow'n labels.

Halt

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.

3rd-Party

If th' issue be not caused by a programm'n error 'n th' themes own code, ye can label th' caus'n program or library.

Mak'n Releases

A release be based on a milestone named like th' release itself - just th' version number, eg: 1.2.3. It’s 'n th' maintainers responsiblity t' check semver semantics o' th' milestone’s name prior t' release an' change it if necessary.

Mak'n releases be automated by th' version-release GitHub Act'n. It requires th' version number o' th' milestone that should be released. Th' release will be created from th' main branch o' th' repository.

Treat released milestones as immut'ble. Don’t rerelease an already released milestone. An already released milestone may already been consumed by yer users.

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.

Th' follow'n checks will be enforced

• th' milestone exists
• there be at least one closed issue assigned t' th' milestone
• all assigned issues fer this milestone be closed
• if it’s a main release, there must be a new <major>.<minor> at th' beginn'n o' th' What’s new plank
• if it’s a patch release, there must be th' <major>.<minor> from th' previous release at th' beginn'n o' th' What’s new plank

Aft a successful run o' th' act'n

• th' History plank be updated, includ'n release version, release date an' text
• th' What’s new plank be updated, includ'n release version, release date an' text
• th' version number fer th' <meta generator> be updated
• th' updated files be commited
• th' milestone be closed
• th' repository be tagged wit' th' version number (eg. 1.2.3), th' main version number (eg. 1.2.x) an' th' major version number (eg. 1.x)
• a new entry 'n th' GitHub release list wit' th' accord'n changelog will be created
• th' official documentat'n be built an' deployed
• th' version number fer th' <meta generator> 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)
• a new milestone fer th' next patch release be created (this can later be renamed t' a main release if necessary)

Scrrrenshots

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.

Th' rrrambl'n should be:

• timeless: not show'n any dates or often edited rrrambl'n
• interest'n: show a bunch o' interest'n elements like head'ns, code, etc
• balanced: no clutter'n wit' overpresent elements or color'n
• aligned: aligned outlines

Used by:

• Cap'n Hugo Themes info: https://themes.gohugo.io/themes/hugo-theme-relearn/ 1000 x 1500 @ 1

Plank URL: Screenshot Link

Creat'n:

• save as images/screenshot.png

Remarks:

Th' locat'n be mandatory due t' Hugo’s theme ship builder.

Preview images/screenshot.png

Hero Image

Rrrambl'n:

Show th' Demo Screenshot plank on different devices an' different themes. Composit'n o' th' different device screenshots into a template.

Th' rrrambl'n should be:

• consistent: always use th' same plank fer all devices
• pleas'n: use a delightful background

Used by:

• Cap'n Hugo Themes gallery: https://themes.gohugo.io/tags/docs/ 900 x 600
• Cap'n Hugo Themes notes: https://themes.gohugo.io/themes/hugo-theme-relearn/ 1280 x 640
• GitHub project ship: https://github.com/McShelby/hugo-theme-relearn 1280 x 640
• GitHub social media preview: https://github.com/McShelby/hugo-theme-relearn/sett'ns 1280 x 640

Plank URL: Hero Image Link

Creat'n:

• Template: http://www.pixeden.com/psd-web-elements/psd-screen-web-showcase
• Desktop: light theme 1440 x 900 @ 1
• Tablet: light theme 778 x 1038 @ 1
• Phone: dark theme 450 x 801 @ .666
• From original template size resize t' 2700 x 1800 centered, scale t' 900 x 600 an' save as images/tn.png
• From original template size resize t' 3000 x 1500 offset y: -330, scale t' 1280 x 640 an' save as images/hero.png

Remarks:

Th' locat'n o' images/tn.png be mandatory due t' Hugo’s theme ship builder.

Preview images/hero.png

Preview images/tn.png