Update CONTRIBUTING.md

Author: violetforest

CONTRIBUTING.md

@@ -1,13 +1,5 @@
 # CONTRIBUTING
 
-Hi, welcome to hic et nunc repository. We're happy you're here.
-
-We're trying to optimize the source code little by little, and it is only fair to write some notes on the thinking behind why we're making some of the decisions we're making. Writing this down will help you (the contributor) get comfortable with the source code.
-
-## Testing
-
-We're currently implementing [Storybook](https://storybook.js.org/) which will be the ideal place where you can check how the components look. We're also currently implementing basic unit testing using [Jest](https://jestjs.io/).
-
 ## Components
 
 When creating a component you need to provide a few properties in order to render the component properly. Try to avoid creating prop drilling, or even accessing react context in a component. The components should be as dumb as possible. The only place where you should have access to API requests, or React.Context is at the page level (`src/pages/*`).
@@ -28,10 +20,8 @@ There are some auxiliary components that aren't doing much besides aiding with t
 
 ## PR
 
-Pull requests should be as small as possible. At the moment there are a lot of eslint errors everywhere, and instead of fixing them all in one go (potentially breaking something and not being able to identify exactly what broke it), we're deciding to go page by page, component by component, fixing those warnings, removing unused code, etc.
-
-Because it's been a very small team contributing to this project, we've been mainly contributing directly into the `main` branch, but that won't happen anymore.
+We take PRs on a case-by-case basis. Please contact us in the discord in the #dev channel to have your PR considered.
 
-We will be using a Git flow approach. This means that you will need to create a feature branch from the `develop` branch, write all your code there, and then when you submit your PR you submit it against the `develop` branch. Once the features on `develop` are tested and ready to push to production, an Admin will create a PR from `develop` to `main` and kick off a deployment.
+You will need to create a feature branch from the `main` branch, write all your code there, and then when you submit your PR you submit it against the `main` branch.
 
-If Git flow is something new to you, don't feel intimidated, come and join us on Discord and we'll take the time to help.
+If anything else is new to you, don't feel intimidated, come and join us on Discord and we'll take the time to help.