Merge pull request #20 from makeplane/api-intake

Changed inbox to intake in api reference

Author: danciaclara

api-reference/inbox-issue/add-inbox-issue.mdx

@@ -1,6 +1,6 @@
 ---
-title: Add inbox issue
-description: Adds an inbox issue in a project
+title: Add intake issue
+description: Adds an intake issue in a project
 api: POST /api/v1/workspaces/{workspace-slug}/projects/{project_id}/inbox-issues/
 ---
 

api-reference/inbox-issue/delete-inbox-issue.mdx

@@ -1,6 +1,6 @@
 ---
-title: Delete inbox issue
-description: Deletes an inbox issue
+title: Delete intake issue
+description: Deletes an intake issue
 api: DELETE /api/v1/workspaces/{workspace-slug}/projects/{project_id}/inbox-issues/{issue_id}
 ---
 

api-reference/inbox-issue/get-inbox-issue-detail.mdx

@@ -1,6 +1,6 @@
 ---
-title: Get inbox issue detail
-description: Gets the details of an inbox issue
+title: Get intake issue detail
+description: Gets the details of an intake issue
 api: GET /api/v1/workspaces/{workspace-slug}/projects/{project_id}/inbox-issues/{issue_id}
 ---
 

api-reference/inbox-issue/list-inbox-issues.mdx

@@ -1,6 +1,6 @@
 ---
-title: List inbox issues
-description: Gets all the inbox issue of a project
+title: List intake issues
+description: Gets all the intake issue of a project
 api: GET /api/v1/workspaces/{workspace-slug}/projects/{project_id}/inbox-issues/
 ---
 

api-reference/inbox-issue/overview.mdx

@@ -2,7 +2,7 @@
 title: Overview
 ---
 
-To enable an inbox, the user can hit a PATCH request on the project api with the body as
+To enable the intake feature, the user can hit a PATCH request on the project api with the body as
 
 ```http
 GET    /api/v1/workspaces/:workspace-slug/projects/:project_id/inbox-issues/
@@ -18,7 +18,7 @@ DELETE /api/v1/workspaces/:workspace-slug/projects/:project_id/inbox-issues/:iss
 }
 ```
 
-To create an inbox issue, the payload should be sent in the below format
+To create an intake issue, the payload should be sent in the below format
 
 ```json
 {
@@ -29,7 +29,7 @@ To create an inbox issue, the payload should be sent in the below format
 }
 ```
 
-### Inbox Issue Object
+### Intake Issue Object
 
 **Attribute**
 
@@ -57,7 +57,7 @@ To create an inbox issue, the payload should be sent in the below format
 
 - `source`
 
-  The source describes the type inbox issue from
+  The source describes the type intake issue from
 
 - `created_by` , `updated_by` _uuid_
 
@@ -73,7 +73,7 @@ To create an inbox issue, the payload should be sent in the below format
 
 - `inbox`
 
-  inbox id of the issue
+  intake id of the issue
 
 - `issue`
 

api-reference/inbox-issue/update-inbox-issue-detail.mdx

@@ -1,6 +1,6 @@
 ---
-title: Update inbox issue detail
-description: Updates the details of an inbox issue
+title: Update intake issue detail
+description: Updates the details of an intake issue
 api: PATCH /api/v1/workspaces/{workspace-slug}/projects/{project_id}/inbox-issues/{issue_id}
 ---
 

api-reference/project/overview.mdx

@@ -86,7 +86,7 @@ DELETE /api/v1/workspaces/:workspace-slug/projects/:project_id/
 
 - `inbox_view` _bool_
 
-  Enable disable inbox for the project in the UI
+  Enable disable intake for the project in the UI
 
 - `page_view` _bool_
 

mint.json

@@ -220,7 +220,7 @@
           ]
         },
         {
-          "group": "Inbox issue",
+          "group": "Intake issue",
           "pages": [
             "api-reference/inbox-issue/overview",
             "api-reference/inbox-issue/add-inbox-issue",

plane-one/governance/workspaces-and-teams.mdx

@@ -14,7 +14,7 @@ To align the product better with the ethos of collaboration, we will introduce T
 
 ## Why this change
 
-Plane was conceived, designed, and built for cross-functional collaboration, going beyond just your team or company to include customers. Features like [Inbox](https://docs.plane.so/core-concepts/inbox), [Publish](https://docs.plane.so/core-concepts/deploy), and [Pages](https://docs.plane.so/core-concepts/pages/overview) unlock that unique-to-Plane collaboration and will work with other forthcoming paid features. While workspaces have enabled essential separation of team- or org-specific data, we have come to realize they create silos that render our collaboration features moot.
+Plane was conceived, designed, and built for cross-functional collaboration, going beyond just your team or company to include customers. Features like [Intake](https://docs.plane.so/core-concepts/inbox), [Publish](https://docs.plane.so/core-concepts/deploy), and [Pages](https://docs.plane.so/core-concepts/pages/overview) unlock that unique-to-Plane collaboration and will work with other forthcoming paid features. While workspaces have enabled essential separation of team- or org-specific data, we have come to realize they create silos that render our collaboration features moot.
 
 ## The short-term plan for One