Basic docs (W.I.P.)

Author: SimonB50

blog/2019-05-28-first-blog-post.md

@@ -1,23 +1,22 @@
-yangshun:
-  name: Yangshun Tay
-  title: Front End Engineer @ Facebook
-  url: https://github.com/yangshun
-  image_url: https://github.com/yangshun.png
-  page: true
+59L:
+  name: 59L
+  title: Project Leader
+  url: https://github.com/59L
+  image_url: https://avatars.githubusercontent.com/u/60123007?v=4
+  page:
+    # customize the url of the author page at /blog/authors/<permalink>
+    permalink: '/59l'
   socials:
-    x: yangshunz
-    github: yangshun
+    github: 59L
 
-slorber:
-  name: Sébastien Lorber
-  title: Docusaurus maintainer
-  url: https://sebastienlorber.com
-  image_url: https://github.com/slorber.png
+simonb50:
+  name: SimonB50
+  title: Project Maintainer
+  url: https://github.com/SimonB50
+  image_url: https://avatars.githubusercontent.com/u/40821945?v=4
   page:
     # customize the url of the author page at /blog/authors/<permalink>
-    permalink: '/all-sebastien-lorber-articles'
+    permalink: '/simonb50'
   socials:
-    x: sebastienlorber
-    linkedin: sebastienlorber
-    github: slorber
-    newsletter: https://thisweekinreact.com
+    github: SimonB50
+    website: https://simonb50.xyz

blog/2019-05-29-long-blog-post.md

@@ -1,19 +1,4 @@
-facebook:
-  label: Facebook
-  permalink: /facebook
-  description: Facebook tag description
-
-hello:
-  label: Hello
-  permalink: /hello
-  description: Hello tag description
-
-docusaurus:
-  label: Docusaurus
-  permalink: /docusaurus
-  description: Docusaurus tag description
-
-hola:
-  label: Hola
-  permalink: /hola
-  description: Hola tag description
+release:
+  label: Release
+  permalink: /releases
+  description: Release notes for the latest versions of BryanBot.

blog/2021-08-01-mdx-blog-post.mdx

@@ -0,0 +1,4 @@
+{
+  "label": "Community",
+  "position": 3
+}

blog/2021-08-26-welcome/docusaurus-plushie-banner.jpeg

@@ -0,0 +1,22 @@
+---
+title: Addons
+sidebar_position: 4
+---
+
+# Addons
+There are multiple types of addons available for BryanBot. They differ in the way they are created, maintained and distributed. Here is a list of the different types of addons available for BryanBot:
+
+## Official Addons
+Official addons are created and maintained by the BryanBot team. They are guaranteed to work with the latest version of BryanBot. Compatibility updates are released with every new version of BryanBot.
+
+Currently, there are no official addons available for BryanBot.
+
+## First-party Addons
+First-party addons are created by the developers of the BryanBot. They are maintained and frequently updated by the developers. They are not guaranteed to work with the latest version of BryanBot and compatibility updates can be posted later than the release of a new version of BryanBot.
+
+Currently, there are no first-party addons available for BryanBot.
+
+## Third-party Addons
+Third-party addons are created by the community. They are not maintained by the BryanBot team and are not guaranteed to work with the latest version of BryanBot or at all. Compatibility updates are released by the developers of the addon.
+
+Currently, there are no third-party addons available for BryanBot.

blog/2021-08-26-welcome/index.md

@@ -0,0 +1,44 @@
+---
+title: Developer Guidelines
+sidebar_position: 2
+---
+
+# Community Developer Guidelines
+- "We", "Us", "Our" refer to the BryanBot Development Team.
+- "You", "Your" refer to the **Community Developers.**
+- "Third Party Developers" refer to any developers who are not in contact with us and have not read this document.
+
+> You, for the entirety of the time that you are holding the title and included within the position of **Community Developer**, are bound by this agreement and any direct or indirect violations will have consequences. In case of resigning from the position, you will no longer be bound by this agreement until you will once again be holding the title and included within the position of **Community Developer**.
+
+## Community Developers
+1. All resources must be submitted for verification before being published. No exceptions will be made.
+2. Do not publicly call out any users or developers in the event of a dispute or conflict between two parties. Contact BryanBot staff instead.
+3. You are not allowed to publish addons explicitly made by another third-party developer under any conditions.
+
+## Resources Submitted
+1. Submitted resources may not contain any piece of code with the intention of benefiting the developer from the user's hardware or software.
+2. All submitted resources must consist primarily of your code. If you are found to be plagiarizing code from elsewhere, we reserve the right to remove you from the position of a **Community Developer**. You are allowed to use third-party or licensed code if permission is granted, but you are required to disclose that you have used code from a third party and the original author of the used code.
+	- You are not allowed to publish addons explicitly created by a third-party developer, regardless of your connection to them.
+	- You are responsible for the safety and security of any third-party code you have included in your addons.
+3. You are responsible for keeping your codebase clean and free of bugs for the duration of your holding the title of **Community Developer**. Any unmaintained addons must be strictly disclosed to be unmaintained and therefore possibly prone to bugs and/or vulnerabilities.
+
+## Publishing resources
+1. Add verified resource should be published on the <u>verified marketplace</u>.
+	- You are able to request verification of any platform you want to publish your resources on.
+2. All threads for verified resources should include official branding for verified work.
+	- You are not allowed to use verified branding on resources that were not verified by BryanBot staff even if you are **Community Developer**.
+3. All published resources need to clearly state that they are made for BryanBot along with link to the official GitHub repository of the project.
+
+## Our Rights
+1. We reserve the right to remove you from the position of a **Community Developer** anytime, for any reason.
+	- Needless to say, we will always provide proper reasoning, but you must keep in mind that we do hold the right to do so.
+2. We hold the right to investigate your code without prior notice, for any reason, and you are obliged to respond positively. Exceptions will be handled on a case-by-case basis.
+
+## Your Rights
+1. You, naturally, reserve the right to resign from your position as **Community Developer**, forfeiting all benefits coming from said position.
+2. While BryanBot Development Team is fitting the definition of organizations engaged in **professional or commercial activity** as stated by the GDPR, <u>we do not</u> collect any data from our users for commercial purposes and therefore are not bound by GDPR; however, you, as a **Community Developer**, are unofficially eligible for requesting your data.
+3. You may inquire about the usage of collected information and how it is processed, anytime for any reason.
+4. You get to object to any of the lines within this document with proper reasoning provided, as well as to request changes; however, you must keep in mind that:
+	- We may veto your objections.
+	- Refuse to make any changes,
+5. All sales you make will be collected entirely by you; we will not intervene with the funds received by you.

blog/authors.yml

@@ -0,0 +1,27 @@
+---
+title: About
+sidebar_position: 1
+---
+
+# BryanBot Community
+BryanBot is a community-driven project. We are always looking for ways to improve the bot and to make it more accessible for the community. This page is dedicated to the community and the developers who are contributing to the project.
+
+## Community Support
+We have a [dedicated server for the BryanBot community](https://discord.gg/GvyuDDFeZU). If you have any questions, suggestions, or need help with the bot, feel free to join the server and ask for help. Our support team is always ready to help you with any issues you might have.
+
+## Community Developers
+We are focused on development made by the community. While we do not limit the independent development for the bot, we do run **Verified Community Developers** program. This program is designed to help developers to get their work recognized and to help them to get more users for their projects.
+
+### Joining the Program
+In order to join the program, you need to submit at least one resource for verification. More about the verification process can be found in the section below.
+
+### Addon Verification
+Verification is a process where we check the submitted resources for any malicious code, bugs, or other issues. We also check if the resource is following the guidelines set by the BryanBot Development Team. If the resource passes the verification process, it will be marked as verified and the developer will get the verified badge.
+
+#### Verification Process
+1. **Submit the resource** - You need to submit the resource for verification. You can do this through the [support server](https://discord.gg/GvyuDDFeZU).
+2. **Verification** - We will check the resource for any issues. If the resource passes the verification process, it will be marked as verified.
+3. **Publishing** - After the resource is verified, you can publish it on the verified marketplace.
+
+### Publishing Resources
+After resource verification, you can publish the resource on one of the verified marketplaces. More information about that can be found [here](/docs/community/marketplaces).

blog/tags.yml

@@ -0,0 +1,26 @@
+---
+title: Verified Marketplaces
+sidebar_position: 3
+---
+
+# Verified Marketplaces
+Verified addons made by **Community Developers** can only be published on the verified marketplaces.
+This is to ensure that both users and developers are safe from any malicious code or other issues.
+
+## Verified Marketplaces
+- [BuiltByBit](https://builtbybit.com/)
+
+## Requesting marketplace verification
+If you are a **Community Developer** and want to publish your resources on a marketplace that is not verified or you own/represent a marketplace that you want to get verified, you can request verification by contacting the BryanBot staff.
+
+### Requirements
+- The marketplace must have a clear and easy-to-understand terms of service and privacy policy.
+- It needs to operate for at least 6 months.
+- Interface must be user-friendly and easy to navigate.
+- The marketplace must have a system in place to handle disputes between users and developers.
+- It must be handled by a registered company or individual.
+
+## Other approved platforms
+You are allowed to publish your resources on the following platforms:
+- [GitHub](https://github.com/)
+- Your Discord server

docs/community/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Development",
+  "position": 4
+}

docs/community/addons.md

@@ -0,0 +1,12 @@
+---
+title: Introduction
+sidebar_position: 1
+---
+
+# Introduction
+
+:::danger Work in progress
+
+This section is still a work in progress. If you have any questions, feel free to ask in the [Discord server](https://discord.gg/bryanbot).
+
+:::

docs/community/guidelines.md

@@ -0,0 +1,8 @@
+{
+  "label": "Setup",
+  "position": 2,
+  "link": {
+    "type": "generated-index",
+    "description": "Learn how to set up your bot in a few simple steps."
+  }
+}