drennvinn
diff --git a/‎code_of_conduct.md
+3-60 b/‎code_of_conduct.md
+3-60
diff --git a/‎contributing.md
+2-122 b/‎contributing.md
+2-122
diff --git a/‎docs/.vitepress/config.js
+2-10 b/‎docs/.vitepress/config.js
+2-10
diff --git a/‎docs/contributing/code-of-conduct.md
+61 b/‎docs/contributing/code-of-conduct.md
+61
diff --git a/‎docs/contributing/feature-request-process.md
+32 b/‎docs/contributing/feature-request-process.md
+32
diff --git a/‎docs/contributing/github-ci.md
-55 b/‎docs/contributing/github-ci.md
-55
@@ -1,61 +1,4 @@
-# Contributor Covenant Code of Conduct
+# Code of Conduct
 
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making
-participation in our project and our community a harassment-free experience for everyone, regardless of age, body size,
-disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education,
-socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment include:
-
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-- The use of sexualized language or imagery and unwelcome sexual attention or advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take
-appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits,
-issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any
-contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the
-project or its community. Examples of representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed representative at an online or offline
-event. Representation of a project may be further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at
-[email protected]. All complaints will be reviewed and investigated and will result in a response that is deemed
-necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to
-the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent
-repercussions as determined by other members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at
-https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq
+Please see our code of conduct on
+[https://docs.directus.io/contributing/code-of-conduct](https://docs.directus.io/contributing/code-of-conduct)
@@ -1,124 +1,4 @@
 # Contributing
 
-Heya! Welcome to Directus, and thank you for taking the time to contribute back to Open Source Software! ❤️ We want
-everybody to be able to contribute to Directus, no matter your background or expertise. In order to facilitate that,
-we've put together a couple tips and tricks below. Our team truly appreciates every single contributor, community
-member, GitHub star, pull-request, bug report, and feature request. Keeping Directus completely open-source is our way
-of saying: **Thank you!**
-
-> We're here to help!
->
-> If you have _any_ questions along your contributor journey, please feel free to come chat with us on
-> [our Discord server](https://directus.chat).
-
-## Code of Conduct
-
-**The Directus [Code of Conduct](https://github.com/directus/directus/blob/main/code_of_conduct.md) is one of the ways
-we put our values into practice. We expect all of our staff, contractors and contributors to know and follow this
-code.**
-
-**Our contributors and maintainers work extremely hard to build Directus as premium open-source software. Please be
-respectful of those efforts throughout our ecosystem. Trolling, harassing, insulting, or other unacceptable behavior by
-participants will not be tolerated.**
-
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making
-participation in our project and community a harassment-free experience for everyone, regardless of age, body size,
-disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education,
-socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-Examples of behavior that contributes to creating a positive environment include:
-
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
-
-**Before continuing, please take a moment to read our full
-[Code of Conduct](https://github.com/directus/directus/blob/main/code_of_conduct.md).**
-
-## Ways to Contribute
-
-### Reporting Bugs
-
-If you happen to run into a bug, please post an Issue on our main GitHub Issue board:
-https://github.com/directus/directus/issues
-
-Please be as explicit and detailed as you can in the bug report. The more information available, the easier it is for
-other contributors to help you find the solution or fix. Consider adding a schema snapshot file, or a database dump.
-
-### Leaving Feedback
-
-If you have a great idea for an improvement of the platform, or any other feedback, please make sure to open a new
-Discussion on our GitHub Discussions board: https://github.com/directus/directus/discussions
-
-### Document the Project
-
-The [Directus Docs](https://github.com/directus/docs) are living documents that can always be improved on. Notice any
-parts of the docs in dire need of some tender love and care? Feel free to open a Pull Request!
-
-### Helping Others
-
-The Directus community is growing quickly, which also means there's more and more people that have questions. Helping
-out your fellow developers by answering questions on [Discord](https://directus.chat) or
-[GitHub Discussions](https://github.com/directus/directus/discussions/categories/q-a) is a great way to help the
-project.
-
-### Pull Requests
-
-Issues marked "Community" are ready to be implemented by anybody at any point! If you're looking to implement an issue
-that doesn't have that label, please make sure to ping the maintainers before getting started!
-
-#### Contributor License Agreement
-
-All code contributors are required to sign the Contributor License Agreement (CLA). When you start a pull request, a
-GitHub Action will prompt you to review the CLA and sign it by adding your name to contributors.yml
-
-#### Changesets
-
-To properly generate changelogs and determine the right version number after a change is merged, we rely on
-[changesets](https://github.com/changesets/changesets). Each PR should include a changeset that describes whether the
-change is a patch/minor/major version bump, and describe what the change is.
-
-#### Bug Fixes
-
-We treat Issues on the main repo as actionable items we want to get done. This also means that we welcome PRs for any
-Issue that has been labeled either "Bug", "Improvement", or "New Feature". Labeled issues are bugs or new features that
-have been triaged, accepted, and are ready to be implemented.
-
-#### Implementing Features
-
-With the continuous growth of Directus, more and more people are relying on Directus for (critical) data workloads in
-various use cases. This means we need to be careful with any changes that might affect the stability, security,
-performance, or scalability of Directus. For this reason, it's important that any new feature is properly thought
-through and discussed before being implemented.
-
-Before you start writing code to implement your new feature idea, please read through and understand our triaging
-process for new features before diving in. While we encourage and appreciate every code contribution, please understand
-that we can't merge every suggested code change.
-
-##### Triaging Process
-
-Feature Request Discussions that are deemed ready to be implemented with the discussed implementation details are marked
-"Accepted" and converted into an Issue, at which point the feature is ready to be implemented.
-
-New feature ideas reported directly to issues might be converted into a Discussion for further triaging at
-[the core team](https://github.com/orgs/directus/people)'s discretion first. This is often due to a lack of detail, or
-lack of proven interest.
-
-Each Pull Request that comes in is required to resolve [an open Issue](https://github.com/directus/directus/issues) that
-is labeled "Bug", "Improvement", or "New Feature". This ensures that any code change made implements a known actionable
-item, be it a feature or otherwise.
-
-### Reporting Security Vulnerabilities
-
-If you believe you have discovered a security issue within a Directus product or service, please reach out to us
-directly over email: [[email protected]](mailto:[email protected]). We will then open a
-[GitHub Security Advisory](https://github.com/directus/directus/security/advisories) for tracking the fix.
-
-We value the members of the independent security research community who find security vulnerabilities and work with our
-team so that proper fixes can be issued to users. Our policy is to credit all researchers in the fix's release notes. In
-order to receive credit, security researchers must follow responsible disclosure practices, including:
-
-- They do not publish the vulnerability prior to the Directus team releasing a fix for it
-- They do not divulge exact details of the issue, e.g., through exploits or proof-of-concepts
+Please see our contributing guidelines on
+[https://docs.directus.io/contributing/introduction](https://docs.directus.io/contributing/introduction)
@@ -603,21 +603,13 @@ function sidebar() {
 					link: '/contributing/introduction',
 					text: 'Introduction',
 				},
-				{
-					link: '/contributing/codebase-overview',
-					text: 'Codebase Overview',
-				},
 				{
 					link: '/contributing/running-locally',
 					text: 'Running Locally',
 				},
 				{
-					link: '/contributing/github-ci',
-					text: 'GitHub CI',
-				},
-				{
-					link: '/contributing/translations',
-					text: 'Translating the App',
+					link: '/contributing/codebase-overview',
+					text: 'Codebase Overview',
 				},
 			],
 		},
 
@@ -0,0 +1,61 @@
+# Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making
+participation in our project and our community a harassment-free experience for everyone, regardless of age, body size,
+disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education,
+socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take
+appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits,
+issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the
+project or its community. Examples of representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed representative at an online or offline
+event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at
+[email protected]. All complaints will be reviewed and investigated and will result in a response that is deemed
+necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to
+the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent
+repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at
+https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq
@@ -0,0 +1,32 @@
+# Request a Feature
+
+If you have a great idea for an improvement of the platform, or any other feedback, please make sure to open a new
+Discussion on [our GitHub Discussions board](https://github.com/directus/directus/discussions).
+
+## Opening a New Feature Request
+
+New feature requests can be opened under the Feature Requests section of
+[GitHub Discussions](https://github.com/directus/directus/discussions). Feature Requests follow a Request-for-Comment
+(RFC) format that allows anybody to fully understand what you're proposing, and help speed up the review and triaging
+process.
+
+**While the form might seem intimidating at first, please do fill out all sections with as much detail as possible. The
+less ambiguity around _how_ a feature should work, the easier it is to review, triage, and develop a feature.**
+
+## Review Process
+
+Once a feature request gets 15 or more upvotes, it will be moved to the "Under Review" status at which point the
+Directus Core team will review it, and decide if it will be approved, denied, or if changes are required. If the feature
+request is accepted, it will be moved to the "Approved Requests" status, at which point the feature is ready to be
+implemented.
+
+However, if a feature request doesn't reach at least 15 upvotes within 3 months of it being created, it will be closed
+due to a lack of community interest.
+
+## Implementing Accepted Feature Requests
+
+It's important to note that Accepted Feature Requests are _not_ an ordered list of things that will be worked on next.
+Even though we strive to prioritize what's being worked on based on community feedback, it's likely that there will be
+times when a feature request is blocked by something else that's prioritized by the team. The implementation of accepted
+feature request is triaged based on a combination of popularity, team availability, timelines, scope of the feature, and
+overall project goals.