davidjeddy / project_documentation_templates

Project Documentation Templates

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

NAME

Table of Contents

Badges

Build Status, Code Coverage, PR stats/time frame, Project status, etc.

Description

What project is this project addressing?

Design

What is the architectural design of this project? Diagrams are great content here.

Purpose

Who needs it for what purpose? What problem / pain does this solve?

Special Features

Does this project have a special ability or functionality comparative projects do not?

Contributing

Code of Conduct

Please see CODE_OF_CONDUCT.md.

Contributing Guidelines

Please see CONTRIBUTING_GUIDELINES.md.

Development Documentation

Please see DEVELOPMENT.md.

RoadMap

Upcoming planned project changes and feature adds.

./ROADMAP.md

Requirements

  • A list of items
  • required to run
  • the project (pre project cloning).
  • Do not include
  • project dependencies
  • installed via a
  • package manager such
  • as compose, npm, gem, etc.

Runbook

A collection of errors and corrective actions within the scope of this project.

./RUNBOOK

Usage

Download

git clone ...

Configure

echo -e "Some commands\n
to configure\n
the project.\n"

Execute

echo -e "The commands\n
to run\n
the project."

Terminate

echo -e "You guessed it\n
the command to stop
the project.\n"

Versioning

This project follows SemVer 2.0 tagging pattern.

Given a version number MAJOR.MINOR.PATCH, increment the:

1. MAJOR version when you make incompatible API changes,
2. MINOR version when you add functionality in a backwards compatible manner, and
3. PATCH version when you make backwards compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

Contributors

Additional Information

About

Project Documentation Templates

License:Other