> For the complete documentation index, see [llms.txt](https://stephanosterburg.gitbook.io/scrapbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stephanosterburg.gitbook.io/scrapbook/coding/github/project-readme.md).

# Project README

### Project title

A little info about your project and/ or overview that explains **what** the project is about.

### Motivation

A short description of the motivation behind the creation and maintenance of the project. This should explain **why** the project exists.

### Build status

Build status of continues integration i.e. [travis](https://travis-ci.com/), [appveyor](https://www.appveyor.com/) etc. For example:

[![Build Status](https://camo.githubusercontent.com/fa00b92302c0b97620b5a33bded99e3c09436479/68747470733a2f2f7472617669732d63692e6f72672f616b6173686e696d6172652f666f636f2e7376673f6272616e63683d6d6173746572)](https://travis-ci.org/akashnimare/foco) [![Windows Build Status](https://camo.githubusercontent.com/5e793870fb73577fd32a199e946c4a99ec5e53f3/68747470733a2f2f63692e6170707665796f722e636f6d2f6170692f70726f6a656374732f7374617475732f6769746875622f616b6173686e696d6172652f666f636f3f6272616e63683d6d6173746572267376673d74727565)](https://ci.appveyor.com/project/akashnimare/foco/branch/master)

### Code style

If you're using any code style like xo, standard etc. That will help others while contributing to your project. For example:

[![js-standard-style](https://camo.githubusercontent.com/d0f65430681b67b7104f6130ada8c098ec5f66ba/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f636f64652532307374796c652d7374616e646172642d627269676874677265656e2e7376673f7374796c653d666c6174)](https://github.com/feross/standard)

### Screenshots

Include logo/demo screenshot etc.

### Tech/framework used

For example:

**Built with**

* [Electron](https://electron.atom.io/)

### Features

What makes your project stand out?

### Code Example

Show what the library does as concisely as possible, developers should be able to figure out **how** your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.

### Installation

Provide step by step series of examples and explanations about how to get a development env running.

### API Reference

Depending on the size of the project, if it is small and simple enough the reference docs can be added to the README. For medium size to larger projects it is important to at least provide a link to where the API reference docs live.

### Tests

Describe and show how to run the tests with code examples.

### How to use?

If people like your project they’ll want to learn how they can use it. To do so include step by step guide to use your project.

### Contribute

Let people know how they can contribute into your project. A [contributing guideline](https://github.com/zulip/zulip-electron/blob/master/CONTRIBUTING.md) will be a big plus.

### Credits

Give proper credits. This could be a link to any repo which inspired you to build this project, any blogposts or links to people who contributed in this project.

**Anything else that seems useful**

### License

A short snippet describing the license (MIT, Apache etc)

MIT © [Yourname](https://gist.github.com/akashnimare/7b065c12d9750578de8e705fb4771d2f)