Create the 1-click-bom file. Download the extension and see the guide on exporting a 1-click-bom from your design. This format will allow people to quickly purchase the components. By default this file is expected to be a `1-click-bom.tsv` in the root of the
project, if the file has a different name or is in a different location, please add this info in the kitspace.yaml file (see below).

(Optional) Create the YAML project description file. The `kitspace.yaml` file allows you to specify a website, give a description, pick a rendering color or configure custom paths for the two requirements above. If you don't have a `kitspace.yaml` with a description we will try and find a description from your repo. If we can't find one the build will fail. See the README for details of the file format.

Add your project to a Git repository. To have your project included on Kitspace it needs to be in a publicly accessible Git repository (but it doesn't have to be on GitHub). If you don't know how to use Git then *don't worry*! - you can easily create a repo on GitHub and upload your files using the web interface.

Add your project to Kitspace's board list. To add your project to Kitspace, edit the boards.txt file in the Kitspace repository, by appending the full public URL to your repo (including `https://`, `http://` or `git@` ). Then submit a pull request and Travis CI should confirm that it builds ok. We will then preview your page for you and can merge it so it appears on kitspace.org.

Submitting a project to Kitspace:

Export your plotted gerbers & drill data in RS-274-X format together with drill information into a directory - by default the path "gerbers/" will be searched. If this is not where they are stored, please add this info in the kitspace.yaml file (see below).