Welcome to the C&P By Design Reference Guide! Here you will find information and guidance to developing software in Crude and Products.

• Add your project logo.
• Write a short introduction to the project.
• If you are using badges, add them here.

block-beta
  columns 3
  a:3
  block:group1:2
    columns 2
    h i j k
  end
  g
  block:group2:3
    %% columns auto (default)
    l m n o p q r
  end

---
title: Example Git diagram
---
gitGraph
   commit
   commit
   branch develop
   checkout develop
   commit
   commit
   checkout main
   merge develop
   commit
   commit

---
title: Order example
---
erDiagram
    CUSTOMER ||--o{ ORDER : places
    ORDER ||--|{ LINE-ITEM : contains
    CUSTOMER }|..|{ DELIVERY-ADDRESS : uses

graph TD;
    A-->B;
    A-->C;
    B-->D;
    C-->D;

graph LR
A[Start] --> B{Is it working?}
B -->|Yes| C[Success]
B -->|No| D[Failure]

• About
• Usage
  • Installation
  • Commands
• Development
  • Pre-Requisites
  • Developmen Environment
  • File Structure
  • Build
  • Deployment
• Community
  • Contribution
  • Branches
  • Guideline
• FAQ
• Resources
• Gallery
• Credit/Acknowledgment
• License

Add a detailed introduction about the project here, everything you want the reader to know.

Write about how to use this project.

• Steps on how to install this project, to use it.
• Be very detailed here, For example, if you have tools which run on different operating systems, write installation steps for all of them.

$ add installations steps if you have to.

• Commands to start the project.

If you want other people to contribute to this project, this is the section, make sure you always add this.

List all the pre-requisites the system needs to develop this project.

• A tool
• B tool

Write about setting up the working environment for your project.

• How to download the project...
• How to install dependencies...

Add a file structure here with the basic details about files, below is an example.

.
├── assets
│   ├── css
│   │   ├── index-ui.css
│   │   └── rate-ui.css
│   ├── images
│   │   ├── icons
│   │   │   ├── shrink-button.png
│   │   │   └── umbrella.png
│   │   ├── logo_144.png
│   │   └── Untitled-1.psd
│   └── javascript
│       ├── index.js
│       └── rate.js
├── CNAME
├── index.html
├── rate.html
└── README.md

Write the build Instruction here.

Write the deployment instruction here.

If it's open-source, talk about the community here, ask social media links and other links.

Your contributions are always welcome and appreciated. Following are the things you can do to contribute to this project.

1. Report a bug
   If you think you have encountered a bug, and I should know about it, feel free to report it here and I will take care of it.

2. Request a feature
   You can also request for a feature here, and if it will viable, it will be picked for development.

3. Create a pull request
   It can't get better then this, your pull request will be appreciated by the community. You can get started by picking up any open issues from here and make a pull request.

If you are new to open-source, make sure to check read more about it here and learn more about creating a pull request here.

I use an agile continuous integration methodology, so the version is frequently updated and development is really fast.

1. stage is the development branch.

2. master is the production branch.

3. No other permanent branches should be created in the main repository, you can create feature branches but they should get merged with the master.

Steps to work with feature branch

1. To start working on a new feature, create a new branch prefixed with feat and followed by feature name. (ie. feat-FEATURE-NAME)
2. Once you are done with your changes, you can raise PR.

Steps to create a pull request

1. Make a PR to stage branch.
2. Comply with the best practices and guidelines e.g. where the PR concerns visual elements it should have an image showing the effect.
3. It must pass all continuous integration checks and get positive reviews.

After this, changes will be merged.

coding guidelines or other things you want people to follow should follow.

You can optionally add a FAQ section about the project.

Add important resources here

Pictures of your project.

Credit the authors here.

Add a license here, or a link to it.