✨ Stack Component Guidlines ✨

Stack was created with a single goal: help ourself and others ship better products faster. Stack team very welcome any kind of contributions. Up to date Stack already consist 10+ components. To keep things structured we introduce few guidelines which must be maintained across all Stack components.

If you're looking to add your component to the Stack family or trying to understand internal Stack structure keep reading.

Component files

Every Stack component must include following parts:

CODE_OF_CONDUCT — general code of conduct
README — general component readme.
CONTRIBUTING — contribution guide.
List of contributors — list of all component contributors. We use all-contributors
package.json — mainly used as source for the common component tasks. At the moment allow to add contributors to the component readme.
LICENSE — all Stack components are released under MIT license.
CHANGELOG.md — we keep every change in the CHANGELOG.md
SHIP_README — this is optional readme which becomes README.md, when component get integrated into the Ship.

A beautiful README

A good README needs to contain all the essential information so that developers understand what the project is about, why they should use it, and how to use it. It should also be stylish and attractive (use smiles and easy, concise language).

Headline — every component should have a headline, which is one sentense description of how component can be helful or what it does.
Github topics — every component should have a list of relevant topics.
Features — briefly describe primary features (use smiles 🔥⚡️, they make life more fun). See an example
Installation guide — users should know how to install/use component.
Example — include short component example usage, move full api reference into separate document. See an example
Changelog, License, Contributing, Contributors sections are required to every repository. See an example 1 and an example 2.

Creating your own Stack component

Copy/paste all files to your Stack component repository
Update COMPONENT_README and rename into README.md — that would be a primary readme of your component. It's important to provide meaningful description of the component, update all links to the relevant badges, provide clear getting started guide.
Add initial set of changes to the CHANGELOG
Publish initial version of component using Github Releases
Create new issue into Stack to list your component in the main Stack repository.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!