feat(contribution-guidelines): add forking and branching structure

Author: Vyogami

bun.lockb

@@ -5,12 +5,7 @@ import { Button, Callout, Steps } from 'nextra/components'
 We're glad that you are interested in contributing to Amigrant. Here are few guidelines and conventions to have a clean and structured codebase.
 Please take a moment to read through them!
 
-## Workflow
-
-We are using a mix of [Gitflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow), [Github flow](https://docs.github.com/en/get-started/using-github/github-flow) and [Forking workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow)
-The upstream has 2 branches, `main` and `develop`. The main branch will not be used for any active development rather it'll act as a [`release-branch`](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow#:~:text=Release%20branches,-Once%20develop%20has&text=Creating%20this%20branch%20starts%20the,tagged%20with%20a%20version%20number) i.e the development will be carried out on `develop` branch(obviously) and the project maintainer will merge `develop` branch into `main` after the release cycle has been completed.
-
-To fork a project follow these steps.
+Follow these steps to contribute!
 
 <Steps>
 
@@ -38,13 +33,23 @@ Now, from the [project list](), fork a project that you want to contribute to!
 2. Now click on `create fork` Button.
 
     ![fork tab](/images/contribution-guidelines/fork-tab.png)
+    
+### Start working!
+
+Now you can start working on the `issue`!
+
+> Refer to [Branching structure](#branching-structure) to understand how branches are managed in this project.
 
 </Steps>
 
-## Branching structure
+## Branching structure 
+
+We are using a mix of [Gitflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow), [Github flow](https://docs.github.com/en/get-started/using-github/github-flow) and [Forking workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow)
+The upstream has 2 branches, `main` and `develop`. The main branch will not be used for any active development rather it'll act as a [`release-branch`](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow#:~:text=Release%20branches,-Once%20develop%20has&text=Creating%20this%20branch%20starts%20the,tagged%20with%20a%20version%20number) i.e the development will be carried out on `develop` branch(obviously) and the project maintainer will merge `develop` branch into `main` after the release cycle has been completed.
 
 ![branching structure](/images/contribution-guidelines/branching-structure.png)
 
+
 ## Conventions
 
 ### Conventional commits

pages/contribution-guidelines.mdx

@@ -53,7 +53,7 @@ The project's documentation will be generated using [Nextra.js](https://nextra.s
 > Tech stack is up for discussion i.e it can be changed since the project is in infant stage.
 
 - Data extraction: NER or langchain.
-- Fontend: Next.js, shadcn/UI and custom CSS.
+- Frontend: Next.js, shadcn/UI and custom CSS.
 - Backend: go-amizone SDK and [Gin](https://gin-gonic.com/).
 - Testing: respective testing frameworks.
 - Documentation: Nextra.js