add arch pic, contrib guide, github issue and PR temp, workflows...

Signed-off-by: wiseaidev <[email protected]>

Author: wiseaidev

.github/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,37 @@
+---
+name: Bug
+about: "[Bug \U0001F41B]: Create a bug report for Moerphous."
+title: "[\U0001F41B Bug]: Bug Title."
+labels: needs triage
+assignees: wiseaidev
+
+---
+
+**👶 Getting Started**
+Please [search the history](https://github.com/moerphous/moerphous-server/issues) to see if an issue already exists for the same problem.
+- [ ] I have searched the existing issues.
+- [ ] I have tested the latest version.
+
+**📝 Describe the bug**
+Please provide a summary of what this issue is all about. Thanks for contributing by creating an issue! ❤️
+
+**🕹 Steps to reproduce**
+Please provide a link to a live example and an unambiguous set of steps to reproduce this bug. You can click the deploy button to provide a live reproduction case.
+
+Link to live example:
+Steps:
+1.
+2.
+3.
+
+**😯 Current behavior**
+A clear and concise description of what you expected to happen.
+
+**🤔 Expected behavior**
+Describe what should happen.
+
+**📸 Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**🔦 Additional context**
+What are you trying to accomplish? How has this issue affected you? Providing context helps us come up with a solution that is more useful in the real world.

.github/ISSUE_TEMPLATE/feature.md

@@ -0,0 +1,22 @@
+---
+name: feature
+about: "[Feature\U0001F484]: Suggest a new idea for Brave Chat Server."
+title: "[\U0001F484Feature]: Feature title."
+labels: needs triage
+assignees: wiseaidev
+
+---
+
+**👶 Getting Started**
+Please [search the history](https://github.com/moerphous/moerphous-server/issues) to see if an issue already exists for the same problem.
+- [ ] I have searched the existing issues.
+- [ ] I have tested the latest version.
+
+**📝 Describe the feature**
+Please provide a detailed explanation of what this feature is all about. Thanks for contributing by creating an issue! ❤️
+
+**📸 Screenshots**
+Please provide screenshots of the expected feature, if applicable.
+
+**🔦 Context**
+What are you trying to accomplish? How has the lack of this feature affected you? Providing context helps us come up with a solution that is more useful in the real world.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+## What was wrong?
+
+Related to #
+Closes #
+
+## How was it fixed?
+
+
+## Todo:
+
+- [ ] I have followed (at least) the [PR section of the contributing guide](https://github.com/moerphous/moerphous-server/blob/main/CONTRIBUTING.md#-pull-request-guidelines).
+
+## Cute Animal Picture

.github/dependabot.yml

@@ -0,0 +1,19 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    reviewers:
+      - "wiseaidev"
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    reviewers:
+      - "wiseaidev"

.github/workflows/dependency-review.yml

@@ -0,0 +1,20 @@
+# Dependency Review Action
+#
+# This Action will scan dependency manifest files that change as part of a Pull Request, surfacing known-vulnerable versions of the packages declared or updated in the PR. Once installed, if the workflow run is marked as required, PRs introducing known-vulnerable packages will be blocked from merging.
+#
+# Source repository: https://github.com/actions/dependency-review-action
+# Public documentation: https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement
+name: 'Dependency Review'
+on: [pull_request]
+
+permissions:
+  contents: read
+
+jobs:
+  dependency-review:
+    runs-on: ubuntu-latest
+    steps:
+      - name: 'Checkout Repository'
+        uses: actions/checkout@v3
+      - name: 'Dependency Review'
+        uses: actions/dependency-review-action@v3

CONTRIBUTING.md

@@ -0,0 +1,76 @@
+# 🌍 Contributing.
+
+Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
+
+## 👶 Getting Started!
+
+Ready to contribute? Here's how to set up `moerphous-server` for local development.
+
+1. Fork the `moerphous-server` repo on GitHub.
+2. Clone your fork locally:
+
+```sh
+git clone [email protected]:your_name_here/moerphous-server.git
+```
+3. Create a virtualenv with make:
+
+```sh
+make venv
+```
+
+4. Activate the virtualenv:
+
+```sh
+source .venv/bin/activate
+```
+
+5. Install the main dependencies into the virtualenv using poetry and make. Assuming you have poetry installed, this is how you set up your fork for local development:
+
+```sh
+make install
+```
+
+**Note**: _This command will automatically generate a `.env` file from `.env.example`, uninstall the old version of poetry on your machine, then install latest version `1.2.2`, and install the required main dependencies._
+
+6. Create a branch for local development:
+
+```sh
+git checkout -b name-of-your-bugfix-or-feature
+```
+
+Now you can make your changes locally.
+
+7. When you're done making changes, check that your changes pass tox tests, including testing other Python versions with make:
+
+```sh
+make test-all
+```
+
+8. Commit your changes and push your branch to GitHub:
+
+```sh
+git add .
+git commit -m "Your detailed description of your changes."
+git push origin name-of-your-bugfix-or-feature
+```
+
+9. Submit a pull request through the GitHub website.
+
+## 📙 Pull Request Guidelines.
+
+Before you submit a pull request, check that it meets these guidelines:
+
+1. The pull request should include tests, if possible.
+2. The pull request should work for Python 3.9.10. Check and make sure that the tests pass for all supported Python versions.
+
+## 💡 Tips.
+
+To run a subset of tests:
+
+```sh
+make test
+make lint
+make coverage
+```
+
+Thank you for helping us improve!

README.md

@@ -8,9 +8,10 @@
 [![Static typing: mypy](http://www.mypy-lang.org/static/mypy_badge.svg)](http://mypy-lang.org/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 ![Codeql](https://github.com/github/docs/actions/workflows/codeql.yml/badge.svg)
-
 </div>
 
+![architecture](./static/architecture.png)
+
 A Fully Async-based backend for [Moerphous](https://github.com/moerphous/moerphous).
 
 **Note**: MongoDB is being used to store only the wallet `classic_address` and its `seed` to make transactions work. This project is just a POC for an NFT marketplace backend. In the future, once deployed on the mainnet, MetaMask will be utilized to connect the wallet.
@@ -192,7 +193,7 @@ For development purposes, you can use openapi to interact with the endpoints. To
 
 As you can notice, the default openapi authorization form has been customized to authenticate wallets using only an access token.
 
-- Now you can interact with any endpoints that require authorization.
+- Now you can interact with any endpoint that require authentication.
 
 ![wallet info](./static/wallet-info.png)