Merge pull request #6 from makeplane/remove-redirects

danciaclara · web-flow · commit 0c64c926dc22 · 2024-09-30T12:06:40.000+05:30
Fixed broken links
diff --git a/plane-one/governance/workspaces-and-teams.mdx b/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](/core-concepts/inbox), [Publish](/core-concepts/deploy), and [Pages](/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 [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.
 
 ## The short-term plan for One
 
diff --git a/plane-one/introduction.mdx b/plane-one/introduction.mdx
@@ -20,6 +20,6 @@ When you log in, you will see a list of your licenses. Clicking any will show yo
 <Tip>If you are yet to get a license, do that [here](https://plane.so/one).</Tip>
 
 ## Quickstart
-Plane One installs with a single command on your CLI. [Learn more](/plane-one/self-host/methods/one-command).
+Plane One installs with a single command on your CLI. [Learn more](/self-hosting/methods/docker-compose).
 
 
diff --git a/plane-one/self-host/methods/kubernetes.mdx b/plane-one/self-host/methods/kubernetes.mdx
@@ -224,7 +224,7 @@ title: Kubernetes
 | ssl.issuer | http |  | CertManager configuration allows user to create issuers using `http` or any of the other DNS Providers like `cloudflare`, `digitalocean`, etc. As of now Plane supports `http`, `cloudflare`, `digitalocean`|
 | ssl.token |  |  | To create issuers using DNS challenge, set the issuer api token of dns provider like cloudflare` or `digitalocean`(not required for http) |
 | ssl.server | [https://acme-v02.api.letsencrypt.org/directory](https://acme-v02.api.letsencrypt.org/directory) |  | Issuer creation configuration need the certificate generation authority server url. Default URL is the `Let's Encrypt` server|
-| ssl.email | [plane@example.com](plane@example.com) |  | Certificate generation authority needs a valid email id before generating certificate. Required when `ssl.createIssuer=true`  |
+| ssl.email | `plane@example.com` |  | Certificate generation authority needs a valid email id before generating certificate. Required when `ssl.createIssuer=true`  |
 | ssl.generateCerts | false |  | After creating the issuers, user can still not create the certificate untill sure of configuration. Setting this to `true` will try to generate SSL certificate and associate with ingress. Applicable only when `ingress.enabled=true` and `ssl.createIssuer=true` |
 
 ### Common Environment Settings
diff --git a/plane-one/self-host/overview.mdx b/plane-one/self-host/overview.mdx
@@ -5,7 +5,7 @@ sidebarTitle: Overview
 
 ## Methods
 <CardGroup cols={2}>
-  <Card title="Docker" icon="terminal" href="/plane-one/self-host/methods/one-command">
+  <Card title="Docker" icon="terminal" href="/self-hosting/methods/docker-compose">
     Run Plane One using docker with a single command
   </Card>
   <Card title="Kubernetes (Coming Soon!)" icon="gear" href="">
@@ -29,10 +29,10 @@ sidebarTitle: Overview
 </CardGroup> */}
 ## Manage
 <CardGroup cols={2}>
-  <Card title="Manage Licenses" icon="toolbox" href="/plane-one/self-host/manage/prime-client">
+  <Card title="Manage Licenses" icon="toolbox" href="https://docs.plane.so/workspaces-and-users/upgrade-plan">
     Learn how to configure your instance.
   </Card>
-  <Card title="Prime CLI" icon="star-of-life" href="/plane-one/self-host/manage/prime-cli">
+  <Card title="Prime CLI" icon="star-of-life" href="/self-hosting/manage/prime-cli">
     Setup authentication methods on your Plane instance.
   </Card>
 </CardGroup>
diff --git a/self-hosting/govern/instance-admin.mdx b/self-hosting/govern/instance-admin.mdx
@@ -24,9 +24,6 @@ God Mode features a few screens as shown below.
         Your instance name, admin’s email address, and the provision to add other instance admins show up on this screen. There’s also an option to report anonymous usage data so we can learn from how you use Plane and ship better product.
 
     -  **Email**
-
-        <Frame>![](/images/instance-admin/email-instance-settings.png)</Frame>
-
         Set up your SMTP server here so you can send essential emails—password resets, exports, changes to your instance—and Plane-enabled emails—onboarding, tips and tricks, new features— to all your users. [Learn more here](/self-hosting/govern/communication).
 
     -  **SSO and OAuth**
@@ -92,7 +89,7 @@ Soon, we will introduce God Mode for our Cloud users as well so they can manage
     </Accordion>
 
     <Accordion title="Is there a God Mode for Cloud admins, too?">
-    Not now, but soon enough, there will be a `God Mode` for Cloud admins. More [here](/self-hosting/instance-admin)
+    Not now, but soon enough, there will be a `God Mode` for Cloud admins.
 
     </Accordion>
 
diff --git a/self-hosting/manage/prime-cli.mdx b/self-hosting/manage/prime-cli.mdx
@@ -10,7 +10,7 @@ sidebarTitle: Prime CLI
 The Prime CLI is our own command-line interface to help you install, upgrade, and manage your Commercial edition instance without being a pro at Docker. 
 
 <Note>
-If you are on the Community edition and want to upgrade to the Commercial edition, see [Upgrade from Community](/self-hosting/manage-plans/upgrade-from-community).
+If you are on the Community edition and want to upgrade to the Commercial edition, see [Upgrade from Community](/self-hosting/upgrade-from-community).
 </Note>
 
 Bring up the Prime CLI with ```sudo prime-cli``` from any directory on your machine.
diff --git a/self-hosting/methods/docker-compose.mdx b/self-hosting/methods/docker-compose.mdx
@@ -30,7 +30,7 @@ Plane One and Plane Pro are enabled on this edition, so the Free plan on this ed
       - **Express**: Plane installs with the default configurations.
       - **Advanced**: You can customize the database, Redis, storage  and other settings.
    6. The installation will take a few minutes to complete and you will see the message **Plane has successfully installed**. You can access the Plane application on the domain you provided during the installation. 
-   7. If you want to upgrade to a paid plan, see [Plane upgrades](/workspaces-and-users/upgrade-plan).
+   7. If you want to upgrade to a paid plan, see [Plan upgrades](https://docs.plane.so/workspaces-and-users/upgrade-plan).
 
 ## Community Edition 
    To install our Community Edition, please follow these steps below.
diff --git a/self-hosting/methods/kubernetes.mdx b/self-hosting/methods/kubernetes.mdx
@@ -87,7 +87,7 @@ Plane One and Plane Pro are enabled on this edition, so the Free plan on this ed
                     --wait \
                     --wait-for-jobs 
             ```
-    5. If you want to upgrade to a paid plan, see [Plane upgrades](/workspaces-and-users/upgrade-plan).
+    5. If you want to upgrade to a paid plan, see [Plan upgrades](https://docs.plane.so/workspaces-and-users/upgrade-plan).
 
 <AccordionGroup>
    <Accordion title="Configuration settings">
