Update README.md

Author: Nemika-Haj

README.md

@@ -1,38 +1,49 @@
-<p align="center"><img src="https://i.imgur.com/NZfsD1p.png"></p>
-
-## Usage
-
-### Create an App
-
-```
-# with npx
-$ npx create-nextron-app my-app --example with-typescript
-
-# with yarn
-$ yarn create nextron-app my-app --example with-typescript
-
-# with pnpx
-$ pnpx create-nextron-app my-app --example with-typescript
-```
-
-### Install Dependencies
-
-```
-$ cd my-app
-
-# using yarn or npm
-$ yarn (or `npm install`)
-
-# using pnpm
-$ pnpm install --shamefully-hoist
-```
-
-### Use it
-
-```
-# development mode
-$ yarn dev (or `npm run dev` or `pnpm run dev`)
-
-# production build
-$ yarn build (or `npm run build` or `pnpm run build`)
-```
+<center>
+<img src="https://raw.githubusercontent.com/BytesToBits/LockPass/main/resources/splash-icon.gif" height="300px" margin="0 auto 0 auto" />
+<h1><strong><em>LOCKPASS, A PASSWORD MANAGER</em></strong></h1>
+</center>
+
+# **LockPass**
+> *LockPass is a simple passsword manager made using [Electron](https://electronjs.org/) + [Next.js](https://nextjs.org/) ([Nextron](https://github.com/saltyshiomix/nextron/)).*
+
+## How it works
+- Head over to the [Releases](https://github.com/BytesToBits/LockPass/releases) tab and download the latest version. The file you must downlaod must be formatted like so: `LockPass-Setup-[VERSION].exe`
+- Run the downlaoded file. Chrome and Windows might try to prevent its download, but you can discard the alerts if you wish. There are no threats in the applications whatsoever.
+- Whenever there is a new release, the application will update automatically.
+- Passwords are saved __locally__, so there is no fear of having them leaked online.
+
+## To-Do
+- Improve the overall design
+- Settings panel allowing more features to be used
+- A more protective way of storing passwords (encryptions & user pin)
+
+
+# **Contributions**
+All contributions are welcome! Feel free to work on any of the above To-Do features. Make sure, however, that your commit messages follow the guidelines below to make it easier for us to track. *it's fine if you don't*
+1. **Select the type of commit:**  
+• `feat`: The new feature you're adding to a particular application  
+• `fix`: A bug fix  
+• `style`: Feature and updates related to styling  
+• `refactor`: Refactoring a specific section of the codebase  
+• `test`: Everything related to testing  
+• `docs`: Everything related to documentation  
+• `chore`: Regular code maintenance.[ You can also use emojis to represent commit types]
+2. **Separate the subject from the body with a blank line**
+3. **Your commit message should not contain any whitespace errors**
+4. **Remove unnecessary punctuation marks**
+5. **Do not end the subject line with a period**
+6. **Capitalize the subject line and each paragraph**
+7. **Use the imperative mood in the subject line**
+8. **Use the body to explain what changes you have made and why you made them.**
+9. **Do not assume the reviewer understands what the original problem was, ensure you add it.**
+10. **Do not think your code is self-explanatory**
+> ***Read [this article](https://www.freecodecamp.org/news/writing-good-commit-messages-a-practical-guide/) to learn more***
+
+Once you are done with your contribution, create a [Pull Request](https://github.com/BytesToBits/LockPass/pulls)!
+
+<center style="margin-top:30px">
+<h1><strong><em>💖 CONTRIBUTORS 💖</em></strong></h1>
+<a href="https://github.com/BytesToBits/LockPass/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=bytestobits/LockPass" />
+</a>
+</center>