Cleanup documentation (#113)

.gitignore

@@ -180,4 +180,5 @@ dist
 .env.development
 .env.test
 
-.DS_Store
+.DS_Store
+package-lock.json

CONTRIBUTING.md → docs/contributing.md

@@ -26,7 +26,7 @@ Welcome to the Akeru.ai community! We are thrilled to have you onboard. This doc
 
 [Akeru.ai](https://www.akeru.ai) leverages the power of the Akeru AI edge network running on a Bittensor Subnet to offer transparent, safe, and highly available AI capabilities. We strive to maintain a welcoming and inclusive community. 
 
-Our [Code of Conduct](/CODE_OF_CONDUCT.md) outlines expected behavior and practices to ensure a collaborative and respectful environment.
+Our [Code of Conduct](/docs/code_of_conduct.md) outlines expected behavior and practices to ensure a collaborative and respectful environment.
 
 ### Getting Started
 
@@ -49,7 +49,7 @@ To contribute to [Akeru.ai](https://www.akeru.ai):
 
 ### Coding Conventions
 
-[Akeru.ai](https://www.akeru.ai) follows Next.js linting standards in the Next app and plans to setup ESLint for the API and service mesh parts. For coding styles, we use Prettier. Our Prettier config will serve as the source of truth. View the full coding convention [here](/CODING_CONVENTIONS.MD). 
+[Akeru.ai](https://www.akeru.ai) follows Next.js linting standards in the Next app and plans to setup ESLint for the API and service mesh parts. For coding styles, we use Prettier. Our Prettier config will serve as the source of truth. View the full coding convention [here](/docs/coding_conventions.md). 
 
 ### Building and Testing
 
@@ -61,12 +61,12 @@ To contribute to [Akeru.ai](https://www.akeru.ai):
 
 All contributions should include relevant documentation updates:
 
-- **Formatting Guidelines**: Follow our documentation style guide [here](/DOCUMENTATION_STYLE_GUIDE.MD).
+- **Formatting Guidelines**: Follow our documentation style guide [here](/docs/documentation_style_guide.md).
 - **Where to Add Documentation**: Add to `/docs` or inline as appropriate.
 
 ### Handling Issues and Pull Requests
 
-- **Reporting Issues**: Use our template [here](/ISSUES_TEMPLATE.md). Ensure to include the detailed steps to reproduce the issue.
+- **Reporting Issues**: Use our template [here](/docs/issue_and_pr_template.md). Ensure to include the detailed steps to reproduce the issue.
 - **Pull Requests**: Use our PR template, link related issues, and provide a detailed description of your changes. Check that out [here](/PULL_REQUEST_DOC_TEMPLATE.md)
 
 ### Community and Communication

DOCUMENTATION_STYLE_GUIDE.MD → docs/documentation_style_guide.md

@@ -45,7 +45,7 @@ This guide establishes standards for creating clear, accessible, and effective d
 ### Language and Grammar
 
 - **Grammar and Spelling**: Utilize tools like [Grammarly](https://www.grammarly.com/) and [Hemingway Editor](http://www.hemingwayapp.com/) to ensure correctness. Adhere to American English spelling conventions.
-- **Examples and Tutorials**: Provide clear examples and detailed tutorials. Use [link to a style guide](#) for complex topics.
+- **Examples and Tutorials**: Provide clear examples and detailed tutorials. Use [link to a style guide](/docs/documentation_style_guide.md) for complex topics.
 
 ### Technical Content
 

docs/issue_and_pr_template.md

@@ -0,0 +1,110 @@
+# Akeru.ai Issue and Pull Request Templates
+
+## Table of Contents
+
+1. [Issue Template](#akeruai-issue-template)
+2. [Pull Request Template](#akeruai-pull-request-template)
+
+## Akeru.ai Issue Template
+
+**Title**: [Enter a clear, concise title describing the issue]
+
+### Description
+
+Provide a detailed description of the problem or the enhancement proposed. Explain the background and the importance of addressing this issue.
+
+### Objectives
+
+- List the specific goals or outcomes expected from resolving this issue.
+- Detail the sections of the project affected and suggest possible solutions, if applicable.
+
+### Expected Outcomes
+
+- Describe what a successful resolution will look like.
+- Explain how it will improve the project (e.g., enhanced usability, reduced errors).
+
+### Tags
+
+- Include relevant tags to help categorize the issue (e.g., `documentation`, `enhancement`, `bug`).
+
+### Assignees
+
+- Tag potential contributors who might be best suited to tackle this issue.
+
+### Example
+
+#### Title: Enhance README Documentation for Akeru.ai
+
+#### Description
+
+The README file is the first point of interaction for potential users and contributors to Akeru.ai. As the project grows and incorporates more features, it's crucial that the README accurately reflects the capabilities and mission of Akeru.ai, providing clear and engaging content that facilitates understanding and involvement.
+
+#### Objectives
+
+- Expand Introduction: Clearly define what Akeru.ai does, the problems it solves, and how it's distinct from other AI platforms.
+- Detail API Features: Include descriptions of current and upcoming features, expected use cases, and any associated limitations or costs.
+- Clarify Bittensor Subnet Integration: Explain how the subnet supports the platform, including any security features and the advantages of decentralization.
+- Update Self-Hosting and Validation Sections: Provide preliminary guidelines and expectations for users interested in self-hosting or participating as validators/miners.
+- Visual Enhancements: Propose the creation of diagrams and workflows to help visually explain complex concepts.
+
+#### Expected Outcomes
+
+- A comprehensive, well-structured README that serves as an effective entry point for engaging new users and contributors.
+- Enhanced clarity on technical aspects and project roadmap, facilitating easier onboarding and collaboration.
+
+#### Tags
+
+`documentation`, `enhancement`
+
+#### Assignees
+
+- @username (Documentation Lead)
+- @username2 (Technical Reviewer)
+
+## Akeru.ai Pull Request Template
+**Title**: [Descriptive title reflecting the main change]
+
+### Description
+
+Briefly describe the purpose of the pull request and what it aims to achieve. Include key changes made, such as feature additions, bug fixes, or enhancements.
+
+### Key Changes
+
+- List significant changes and their impact on the project.
+- Mention any particular areas of the codebase affected.
+
+### Link to Issues
+
+- Reference related issue numbers that this pull request addresses.
+
+### Request for Review
+
+- Tag reviewers who are familiar with the impacted areas of the codebase.
+
+### Checklist
+- [ ] I have written tests.
+- [ ] My code does not produce new errors.
+- [ ] I gave myself a code review before asking others.
+
+### Example
+
+#### Title: Update README for Enhanced Project Clarity and Information
+#### Description
+This pull request updates the README to provide a clearer and more comprehensive understanding of Akeru.ai. The enhancements include detailed descriptions of new API features, the Bittensor Subnet integration, and improved section formatting. These updates aim to make the repository more welcoming and informative for new contributors and users.
+
+#### Key Changes
+
+- Expanded Introduction: Better explains Akeru.ai's unique features and its differentiation in the AI space.
+- Detailed API Features: Includes use cases and development status for upcoming features.
+- Clarified Bittensor Subnet Integration: Details on how the Bittensor Subnet enhances Akeru.ai’s capabilities, including security features and decentralized benefits.
+- Preliminary Self-Hosting Info: Provides initial guidelines on self-hosting and the requirements for validators and miners.
+
+#### Link to Issues
+
+- Addresses feedback from issue #[issue_number] for more detailed documentation.
+
+#### Request for Review
+- @username1
+- @username2
+
+Looking forward to your feedback and suggestions to further refine our project documentation.