Skip to content

Latest commit

 

History

History
73 lines (45 loc) · 1.97 KB

File metadata and controls

73 lines (45 loc) · 1.97 KB

Contributing

Thanks for considering contributing to the Lost Type Co-op blog!

  1. Opening issues
  2. Fixing bugs
  3. Writing CSS

Opening issues

If you find a bug, please feel free to open an issue.

Taking the time to describe a problem, even a seemingly small one, is appreciated, and a totally valid contribution to this project. Thank you!

Fixing bugs

The CSS is all documented and shown in use in the Lost Type blog styleguide. If you’d like to build it locally, run the following command:

npm run styleguide

This uses the Node.js version of KSS to parse the CSS for comments and generate a static documentation site.


We love pull requests. Here’s a quick guide:

  1. Fork this repository and then clone it locally:
git clone https://github.com/losttype/blog.losttype.com
  1. Create a topic branch for your changes:
git checkout -b fix-for-that-thing
  1. Commit a failing test for the bug:
git commit -am "Adds a failing test to demonstrate that thing"
  1. Commit a fix that makes the test pass:
git commit -am "Adds a fix for that thing!"
  1. Run the tests:
npm test
  1. If everything looks good, push to your fork:
git push origin fix-for-that-thing
  1. Submit a pull request.

  2. Enjoy being the wonderful person you are

After you’ve opened your pull request, you should email me your mailing address so I can mail you a personal thank you note. Seriously!

Adding new features

Thinking of adding a new feature? Cool! Open an issue and let’s design it together.