Skip to main content

Readme file template

README is a file that brings a little description about the whole project, which contains an introduction and explanation of this one. The kind of information that can be describe here is information requeried to understand the project and its structure or purpose. Then, we will give a template to create a README file for a new project.

To copy this readme template as markdown source code click here#

Gif or Image Introduction#

Is simple and can sound so easy and yes, It does, but the impact that a Gif or Image can produce is too big. The viewer acquire the needed information to get interested in the project. For example:

Life bank

About the Project#

Give a general description of the project brings a general view about the project as a product, for example:

"Lifebank is an EOSIO-based dapp that helps local communities create a virtuous circle of value exchange between three parties β€” eligible life donors, community donation centers, and participating local businesses (sponsors).

Lifebank is an initiative of EOS Costa Rica, a company that develops blockchain-based solutions to solve real-world problems. Lifebank is our entry to the Coding for Change challenge organized by leading blockchain company,"

Table of Contents#

With a good view about the information structure can make the reader go to the specific needed information, so then give a good view of the information with a Table of Contents will make easier this process. For example:

Table of Contents

  1. Gif or Image Introduction
  2. About The Project
  3. Content Table
  4. Project Purpose
  5. Version
  6. Tech Stack
  7. Development Environment
  8. File Structure
  9. License
  10. Contributing
  11. Contributors
  12. About Company

Project Purpose#

Describes the reason of why this was made, for example:

"We identified two main problems: a blood donation shortage and a local economic slowdown. Amid the COVID-19 outbreak, blood banks urgently need donors. People who are potential qualifying donors are prompted to stay home and isolate. As donations plummet and demand for blood and plasma increases, blood banks are experiencing a pronounced global shortage.

Moreover, the pandemic is impacting local economies due to a generalized lockdown. Small businesses that rely on the local community must think of ways to incentivize customers to buy as soon as restrictions are lifted."


Know what version of the project is, could helps others to debug problems, give it differents solutions or approaches, for this reason, is needed to specify the lastest version of the project, for example:


Evodex is ready for our first group of beta testers to try the next generation decentralized exchange for EOS

Currently evodex is still in beta pre-release v0.1.0-beta.xx

We release the production software version using github tags following Semver.

We also use the git commit messages to generate the project change log.

Using the yarn version command you can update the version of your package via the command line.

Tech Stack#

The purpose is to make the user know the main technology were needed to develop the project, so the user could understand the project with a new kind of view, for example, the information that could be given here is:

  • React.js - React 16✨, React Router 5
  • Rematch/core - Rematch a Redux Framework
  • Material-ui/core - React components for faster and easier web development universal-authenticator-library - A library for allowing apps to easily use different auth providers
  • Lint - ESlint
  • Styles - Material-UI Theme (customizable)

Development Environment#

Specify where were the project developed, in case someone else wants to make a contribution to the project progress, for example: is running on the EOS MainNet and is built from the master branch, our production branch. is running on the Jungle 3 TestNet and is built from the develop branch used for development, integration, and testing new features.

Quick Start#

  • Clone this repo using git clone
  • Move to the appropriate directory: cd <YOUR_PROJECT_NAME>.
  • Run yarn in order to install dependencies. At this point you can run yarn start to see the example app at http://localhost:3000.

Getting Started#

Give the needed instruction to run the project locally, for example:




  1. Clone the repository

    git clone

  2. Install yarn packages

    yarn install

    or just


  3. Run the project

    yarn start

File Structure#

This could help the reader understand the organization inside the project, for example:

/β”œβ”€β”€ publicβ”‚   β”œβ”€β”€ index.htmlβ”‚   └── manifest.jsonβ”œβ”€β”€  srcβ”‚   β”œβ”€β”€ apiβ”‚   β”œβ”€β”€ componentsβ”‚   β”œβ”€β”€ configβ”‚   β”œβ”€β”€ containersβ”‚   β”œβ”€β”€ modelsβ”‚   β”œβ”€β”€ routesβ”‚   β”œβ”€β”€ themeβ”‚   β”œβ”€β”€ utilsβ”‚   β”œβ”€β”€ App.jsβ”‚   β”œβ”€β”€ index.jsβ”‚   └── store.jsβ”œβ”€β”€ .dockerignoreβ”œβ”€β”€ .gitignoreβ”œβ”€β”€ .env.exampleβ”œβ”€β”€ .eslintrcβ”œβ”€β”€ .prettierrcβ”œβ”€β”€ Dockerfileβ”œβ”€β”€ LICENSEβ”œβ”€β”€ README.mdβ”œβ”€β”€ docker-compose.ymlβ”œβ”€β”€ nginx.conf└── package.json


MIT Β© EOS Costa Rica


If you want to make a contribution, please follow the next steps:

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m '<type>(<scope>): <subject>')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

Please Read EOS Costa Rica's Open Source Contributing Guidelines for more information about programming conventions.

If you find a bug, please report big and small bugs by opening an issue <link to issue project section>


List the people who work in the project.

About EOS Costa Rica#

EOS Costa Rica is an independently-owned, self-funded, bare-metal Genesis block producer that provides stable and secure infrastructure for EOSIO blockchains. We support open source software for our community while offering enterprise blockchain development and custom smart contract development for our clients.