@workos/mcp-docs-server 0.1.0

package/.docs/organized/docs/custom-domains/authkit.mdx

@@ -0,0 +1,36 @@
+---
+title: AuthKit Domain
+description: Guidance on configuring a custom domain for AuthKit.
+showNextPage: true
+originalPath: .tmp-workos-clone/packages/docs/content/custom-domains/authkit.mdx
+---
+
+## Configuring a domain
+
+The domain for AuthKit will consist of a randomly generated phrase plus the domain `authkit.app`, for instance `youthful-ginger-43.authkit.app`.
+
+This is the default in the staging environment, in Production environments a custom domain can be configured via the dashboard.
+
+> You must configure an [Authentication API domain](/custom-domains/auth-api) first in order for your custom AuthKit domain to work properly.
+
+### (1) Navigate to Domains configuration
+
+With the production environment selected, navigate to the _Domains_ section of the [WorkOS Dashboard](https://dashboard.workos.com/).
+
+![Dashboard displaying domain configuration settings](https://images.workoscdn.com/images/f04be28f-4af8-4a2e-a812-815d1a441674.png?auto=format&fit=clip&q=80)
+
+### (2) Add an AuthKit domain
+
+Click the _Configure AuthKit domain_ button and enter the domain you would like to use.
+
+![Dashboard displaying a domain entry input](https://images.workoscdn.com/images/b7e45bfe-2948-4d5e-a7ee-be3eb223d710.png?auto=format&fit=clip&q=80)
+
+### (3) Create CNAME records
+
+You will be prompted to add a CNAME record to your DNS provider. If your DNS provider is Cloudflare, ensure the CNAME record is configured as DNS-only and is not proxied. To manage custom domains, WorkOS uses Cloudflare, who prohibit domains from being proxied across accounts.
+
+![Dashboard displaying CNAME entries](https://images.workoscdn.com/images/68d96188-8d68-4a89-8843-5d21d9b739c5.png?auto=format&fit=clip&q=80)
+
+> It can take some time for DNS changes to take effect. If the initial verification attempt is not successful, WorkOS will continue trying to verify your domain for 72 hours.
+
+Once your domain is successfully verified, users signing in via AuthKit will be redirected to your custom domain.

package/.docs/organized/docs/custom-domains/email.mdx

@@ -0,0 +1,41 @@
+---
+title: Email Domain
+description: Guidance on configuring a custom domain for emails.
+showNextPage: true
+originalPath: .tmp-workos-clone/packages/docs/content/custom-domains/email.mdx
+---
+
+## Configuring a domain
+
+Several User Management features require sending emails:
+
+- Magic Auth
+- Email verification
+- Password resets
+- Invitations
+
+While developing with WorkOS in a staging environment, WorkOS will send User Management emails from `workos.dev`.
+
+In production environments, emails are sent from a custom domain when configured or from `workos-mail.com` by default.
+
+### (1) Navigate to Domains configuration
+
+With the production environment selected, navigate to the _Domains_ section of the [WorkOS Dashboard](https://dashboard.workos.com/).
+
+![Dashboard displaying domain configuration settings](https://images.workoscdn.com/images/1b02397b-89b0-451d-9d6d-d222db5635b9.png?auto=format&fit=clip&q=80)
+
+### (2) Add an email domain
+
+Click the _Add Domain_ button and enter the domain you would like to use for sending emails.
+
+![Dashboard displaying a domain entry input](https://images.workoscdn.com/images/2e7840fb-1a05-444c-a68f-52f3ac3eceb5.png?auto=format&fit=clip&q=80)
+
+### (3) Create CNAME records
+
+You will be prompted to create 3 CNAME records with your DNS provider. After creating these DNS records, click _Verify now_.
+
+![Dashboard displaying CNAME entries](https://images.workoscdn.com/images/0d85fad9-2af7-425d-8b4b-55c407a0db83.png?auto=format&fit=clip&q=80)
+
+> It can take some time for DNS changes to take effect. If the initial verification attempt is not successful, WorkOS will continue trying to verify your domain for 72 hours.
+
+Once your domain is successfully verified, authentication emails and Admin Portal invites will be sent from `no-reply@your-domain.com`. It’s important to keep the CNAME records in place to ensure that WorkOS can deliver mail on your behalf.

package/.docs/organized/docs/custom-domains/index.mdx

@@ -0,0 +1,19 @@
+---
+title: Custom Domains
+description: Configure your integration to match your brand identity.
+showNextPage: true
+originalPath: .tmp-workos-clone/packages/docs/content/custom-domains/index.mdx
+---
+
+## Overview
+
+By default, a WorkOS domain will be used for services such as sending email and hosting AuthKit. In the staging environment these will always use a WorkOS domain, however in production you have the option to provide your own custom domain.
+
+This is a paid service, for which you can find additional details on our [pricing page](https://workos.com/pricing).
+
+Custom domains can be set for:
+
+- [Email](/custom-domains/email)
+- [AuthKit](/custom-domains/authkit)
+- [Admin Portal](/custom-domains/admin-portal)
+- [Authentication API](/custom-domains/auth-api)

package/.docs/organized/docs/dashboard.mdx

@@ -0,0 +1,244 @@
+---
+title: Dashboard
+description: "Set up your account on the\_WorkOS\_Dashboard."
+breadcrumb:
+  title: Home
+  url: /
+originalPath: .tmp-workos-clone/packages/docs/content/dashboard.mdx
+---
+
+## Manage your team
+
+You can manage your team from your [team settings](https://dashboard.workos.com/settings/team).
+
+![A screenshot showing team information in the WorkOS Dashboard.](https://images.workoscdn.com/images/07f59c6e-b1e3-430c-adf8-61d89bee1b8e.png?auto=format&fit=clip&q=50)
+
+### Change your team name
+
+To edit your team name select the “Edit” button under team details.
+
+### Change your team's support email address
+
+To edit your team's support email address for Admin Portal emails sent to your customers, select the “Edit” button under team details.
+
+### Invite team members
+
+To invite members, select the “Invite team member” button under team members. When adding a member, you’ll be prompted to select a role for this new member. The following roles are available:
+
+- **Admin** – Admins are able to invite members, change roles of existing members, and revoke access, in addition to capabilities available to a Developer.
+- **Developer** – Developers are able to view and edit configuration for the Environment, including resources like API keys, Redirect URI’s, or OAuth credentials. In addition, they have all of the capabilities available to a Support user.
+- **Support** – Support users are able to view and edit customer-level resources like Organizations, Connections, and Directories. Support users are not able to view or edit Environment-level settings, like API keys or OAuth credentials.
+
+![A screenshot showing the "Add Member" modal in the WorkOS dashboard.](https://images.workoscdn.com/images/191bc084-95d3-4ec4-9271-79de8a7daab4.png?auto=format&fit=clip&q=50)
+
+---
+
+## Manage your billing
+
+You can manage billing from your [account settings page](https://dashboard.workos.com/settings/billing). Select the “Workspace” left menu option from the main dashboard, and then select the “Billing” tab.
+
+If you don’t have billing set up, you can input your billing address and credit card information. This also unlocks access to your Production environment in the dashboard. If you have billing set up, you’ll be able to update your billing address and credit card information.
+
+![A screenshot showing the "Billing" tab of the WorkOS dashboard.](https://images.workoscdn.com/images/507756e0-e81e-4c3c-a5bf-b8c9deac13a6.png?auto=format&fit=clip&q=50)
+
+---
+
+## Manage your user account
+
+You can manage your user account from the [profile page](https://dashboard.workos.com/profile). Select the dropdown menu under your name in the top right corner, and then select the “User Settings” menu option.
+
+![A screenshot showing where to find "User Settings" in the WorkOS dashboard.](https://images.workoscdn.com/images/22f46329-4c05-4cd7-a27c-efc52399d3b2.png?auto=format&fit=clip&q=50)
+
+On the Profile page, you can update your email notification settings. At this time, it’s not possible to update your user information. [Reach out to us](mailto:support@workos.com) if you need this information updated.
+
+---
+
+## Set up a support email address
+
+Add a support email in the Dashboard to streamline communication with your customers’ organization admins. This email will be included in the footer of messages sent to them and set as the reply-to address, making it easy for admins to reach out with any questions. Learn how to update the support email in [team settings](/dashboard/manage-your-team).
+
+![A screenshot showing an email with a custom support email address](https://images.workoscdn.com/images/8eb036ab-5fd0-44fe-81f3-6a69a8c38530.png?auto=format&fit=clip&q=50)
+
+---
+
+## Add the Organization admin email address
+
+You can add the email addresses of your organization’s IT administrators directly to an organization. This enables you to send Admin Portal setup links directly to an organization's admin. Additionally, WorkOS will automatically email admins about important organization-related events that require their attention.
+
+The organization admin email addresses can be set on the Settings page of each organization.
+
+![A screenshot showing an Organization with Admin emails modal](https://images.workoscdn.com/images/b7a83d5a-5fb6-4655-b367-ba23e414fe6d.png?auto=format&fit=clip&q=80)
+
+## Automated emails for Organization admins
+
+Once added to an organization, the organization admin can receive the following types of automated emails:
+
+- **X509 certificate expiration**: Sent when the X509 certificate for a SAML connection is about to expire or has already expired.
+- **SSO connection misconfiguration**: Sent when a SAML connection is misconfigured in the Identity Provider.
+- **Admin Portal setup**: Sent when an admin is invited to set up various products in the Admin Portal, such as SSO, Directory Sync, and more.
+
+## Change the theme
+
+You can change the dashboard theme from the dropdown menu under your name in the top right corner.
+
+![A screenshot showing how to change the theme in the WorkOS Dashboard.](https://images.workoscdn.com/images/8a551570-39bb-4557-bd92-cf75367663e8.png?auto=format&fit=clip&q=50)
+
+---
+
+## Client ID
+
+Navigate to the Configuration page on your WorkOS Dashboard to see your [Client ID](/glossary/client-id). This is needed in many API calls, including the [Get Authorization URL endpoint](/reference/sso/get-authorization-url). The Client ID is specific to the environment in the WorkOS dashboard.
+
+![A screenshot showing where to find the Client ID in the WorkOS Dashboard.](https://images.workoscdn.com/images/64e889d7-2845-4b83-b913-ec120e0a3841.png?auto=format&fit=clip&q=50)
+
+---
+
+## Redirect URIs
+
+Set your allowed Redirect URIs on the Configuration page. The Redirect URI is the callback route where you’ll receive a `code` if a user successfully authenticates. You can then exchange this code for a user profile via the [Get Profile and Token API endpoint](/reference/sso/profile/get-profile-and-token).
+
+![A screenshot showing where to find the Redirect URIs in the WorkOS Dashboard.](https://images.workoscdn.com/images/40703fd3-faca-4a05-820c-835e3cfa1be3.png?auto=format&fit=clip&q=50)
+
+Check out our [Redirect URI tutorial](/sso/redirect-uris) for information on Redirect URI best practices.
+
+---
+
+## Configure global OAuth providers
+
+You can configure global settings for Google OAuth and Microsoft OAuth on the Configuration page. These providers allow anyone that can log in to Google or Microsoft to authenticate to your application. Our provider documentation on [Google OAuth](/integrations/google-oauth), [Microsoft OAuth](/integrations/microsoft-oauth), [GitHub OAuth](/integrations/github-oauth), and [Sign in with Apple](/integrations/apple) can help you set up these authentication methods.
+
+![A screenshot showing global OAuth providers in the WorkOS Dashboard.](https://images.workoscdn.com/images/4af69027-fd2f-4685-8ef2-2568bd5312fa.png?auto=format&fit=clip&q=50)
+
+---
+
+## Configure the Admin Portal
+
+You can set the Admin Portal Redirect Link on the Configuration page. This is where users will be directed after setting up a connection in the Admin Portal. We also offer custom labeling of the Admin Portal. [Reach out to us](mailto:support@workos.com) to learn more.
+
+![A screenshot showing where to find the "Edit Admin Portal Redirect Link" button on the WorkOS Dashboard.](https://images.workoscdn.com/images/cdc042b9-3cb0-496b-a969-aea1305a98eb.png?auto=format&fit=clip&q=50)
+
+---
+
+## Set up custom attributes
+
+On the “Custom Attributes” tab of the Configuration page, you can define custom standardized attributes for your Directory Sync connections. By default, fields like `first_name` and `email` are standardized in Directory Sync. However, you may want to standardize other fields, such as manager. On the Configuration page, you can set the custom attributes you’d like to standardize.
+
+![A screenshot showing the "Custom Attributes" tab in the WorkOS Dashboard.](https://images.workoscdn.com/images/be232fd2-b00c-4987-8f1b-3a45a12f29dd.png?auto=format&fit=clip&q=50)
+
+When custom attributes are configured, you can map them to a specific attribute for a given directory sync connection.
+
+![A screenshot showing where to find "Attribute Mapping" for an organization in the WorkOS Dashboard.](https://images.workoscdn.com/images/9397d3e8-dfed-438a-8801-6d52f19e31e7.png?auto=format&fit=clip&q=50)
+
+The attribute mapped needs to be found in the raw data from the directory, and once mapped to a custom attribute, you’ll see it in the `custom_attributes` for a [Directory User](/reference/directory-sync/directory-user). Check out our [blog post on custom attributes](https://workos.com/blog/custom-attributes) for more information.
+
+---
+
+## SAML Sessions
+
+To assist users in debugging their SAML SSO connections, there is a “Sessions” tab in the Connection Details view for all SAML SSO connections.
+
+Here you can see logs for SAML sessions from these connections which enables you to quickly understand the status and health of each connection. You can see the details of each session, its status, if there are any errors, and what those errors are.
+
+The Sessions tab is available on the Connection Overview page of each SAML based connection.
+
+![A screenshot showing where to find the "Sessions" tab in the WorkOS Dashboard.](https://images.workoscdn.com/images/03c0b73a-2c7f-44d4-b19d-fef774a599df.png?auto=format&fit=clip&q=50)
+
+### Sessions Tab
+
+When you navigate to the Sessions tab, you are presented with a list of recent user sessions for the given connection in chronological order from newest to oldest. Some basic information is available here, including the state, error message, user, truncated session ID, and when the session was created.
+
+![A screenshot of the "Sessions" tab in the WorkOS Dashboard.](https://images.workoscdn.com/images/9beba29d-23b7-40e3-9dfd-38d21dd90673.png?auto=format&fit=clip&q=50)
+
+### Session Details
+
+To find more detail for each session, click on the individual session entry. This will navigate you to the Session Details page where you can find the full Session ID along with other more in depth information about the user authenticating via the session.
+
+![A screenshot showing Session Details in the WorkOS Dashboard.](https://images.workoscdn.com/images/b225723b-9a34-4e5f-b267-9cb7eb564696.png?auto=format&fit=clip&q=50)
+
+One of the most useful aspects of this tool is that it exposes the error messages when a session is not successful. When there are errors, you are presented with the details of the error for review.
+
+![A screenshot showing an error in the SAML Session Details in the WorkOS Dashboard.](https://images.workoscdn.com/images/6c8fb17b-ea75-4b48-8b4c-2cf4fc6e2d23.png?auto=format&fit=clip&q=50)
+
+---
+
+## SAML Errors
+
+There are 5 different errors that can be returned: “Invalid Attributes”, “Invalid X509 Certificate”, “Malformed SAML Response”, “Profile Not Allowed Outside Organization”, and “Decryption Failed”.
+
+### Invalid Attributes
+
+WorkOS requires that there are certain user attributes included in each SAML Response at minimum. In most cases `firstName`, `lastName`, `email`, and `id` are required. If these attributes are not present in the SAML Response, the Invalid Attributes error is thrown. The received attributes will appear in the error details so you can see what attributes may be missing.
+
+### Invalid X.509 Certificate
+
+This error occurs when the X.509 Certificate provided by the Identity Provider in the SAML Response does not match the X.509 Certificate that has been uploaded to WorkOS for the connection. If you receive this error, you’ll want to double check that the certificates match between the IdP and WorkOS for this connection and that the certificate is not expired.
+
+You can view the X.509 certificate that is being sent by the IdP in the SAML Response Body which is provided below, within the `<X509Certificate>` tags. The X.509 certificate that is uploaded to WorkOS can be found in the Connection’s settings page. These two values should match exactly.
+
+![A screenshot showing a X509Certificate tag.](https://images.workoscdn.com/images/94070f56-665f-49af-be0e-a92b8b1c5808.png?auto=format&fit=clip&q=50)
+
+### Malformed SAML Response
+
+This error means that there is an issue with the SAML Response structure or contents and the SAML Response is unable to be validated. There are many factors that could lead to this error, however, there will need to be steps taken on the IdP side in order to resolve it. If you receive this error, please contact [support@workos.com](mailto:support@workos.com) for help.
+
+### Profile Not Allowed Outside Organization
+
+This error occurs when a user with an email domain that does not appear on the Organization’s User Email Domains allowlist attempts to authenticate with the connection.
+
+To resolve this error there are 2 options. The user’s domain can be added to the Organization’s allowlist, or if you do not wish to restrict the Organization to specific domains, you can select the option to allow users with any domain to authenticate with the Organization. Both of these options can be configured on the Organization Overview page.
+
+![A screenshot showing how to add a user’s domain to the Organization's allowlist in the WorkOS Dashboard.](https://images.workoscdn.com/images/6e8eef69-0fb7-47c7-a102-84aa14ff3762.png?auto=format&fit=clip&q=50)
+
+### Decryption Failed
+
+This error can occur if you are encrypting the SAML Response and WorkOS is unable to successfully decrypt the response. This most often occurs when there is an X.509 certificate used to encrypt the response has a mismatch between the Identity Provider and WorkOS. A good first step towards resolution in this case is to ensure that the certificates in the IdP and WorkOS match.
+
+---
+
+## SAML Request & SAML Response
+
+The Session Detail page also shows the raw SAML Request and SAML Response.
+
+### SAML Request
+
+The SAML Request is the XML request that is sent to the Identity Provider from a Service Provider (SP), WorkOS in this case, to initiate the login attempt. This will only appear for SP-Initiated login attempts.
+
+![A screenshot showing a SAML Request Body in the WorkOS Dashboard.](https://images.workoscdn.com/images/612ee70c-62a0-4811-a84b-55378c8b941e.png?auto=format&fit=clip&q=50)
+
+### SAML Response
+
+The SAML Response is what is returned to WorkOS from the Identity Provider after a user has authenticated with the IdP. It will contain the user attributes that get processed into the user Profile object.
+
+![A screenshot showing a SAML Response in the WorkOS Dashboard.](https://images.workoscdn.com/images/39f482d3-e278-45a9-b53e-05c97f0df899.png?auto=format&fit=clip&q=50)
+
+## SAML Session States
+
+### Started
+
+Indicates a user began the authentication process, and a SAML request was sent to the IdP, however, we have yet to receive a SAML response.
+
+### Authorized
+
+Indicates the user successfully authenticated through the IdP and we returned an auth code to the callback route, but it hasn't exchanged the auth code for a profile.
+
+### Successful
+
+Indicates a successful login where WorkOS was able to exchange the callback auth code for a profile.
+
+### Failed
+
+Indicates that there was a successful SAML Request and a Response was provided from the IdP, however, WorkOS was not able to generate a profile from the data in the SAML response.
+
+---
+
+## Compliance Documents
+
+You can download the following documents from the [Compliance Documents page](https://dashboard.workos.com/settings/compliance-documents):
+
+- **SIG Lite**
+- **SOC 3**
+- **SOC 2 Type 2**
+
+> Only users with the Workspace Admin role are able to download documents from the Compliance Documents page.
+
+![A screenshot showing Compliance Documents in the WorkOS dashboard.](https://images.workoscdn.com/images/40d8414a-e084-4b4a-8a13-252f9a869f23.png?auto=format&fit=clip&q=50)

package/.docs/organized/docs/demo/_navigation.mdx

@@ -0,0 +1,26 @@
+---
+title: Docs
+links:
+  - title: Demo
+    url: /demo
+  - title: Accordion
+    url: /demo/accordion
+  - title: Checklist
+    url: /demo/checklist
+  - title: Code Block
+    url: /demo/code-block
+  - title: Definition List
+    url: /demo/definition-list
+  - title: Punctuation
+    url: /demo/punctuation
+  - title: Replacements
+    url: /demo/replacements
+  - title: Share Images
+    url: /demo/share-images
+  - title: Table
+    url: /demo/table
+  - title: Tabs
+    url: /demo/tabs
+originalPath: .tmp-workos-clone/packages/docs/content/demo/_navigation.mdx
+---
+

package/.docs/organized/docs/demo/accordion.mdx

@@ -0,0 +1,34 @@
+---
+title: Accordion
+description: Test page for the accordion component
+originalPath: .tmp-workos-clone/packages/docs/content/demo/accordion.mdx
+---
+
+## Accordion syntax stress test
+
+Adjacent lists shouldn’t be mangled.
+
+- ### One?
+  Two.
+- ### Three?
+  Four.
+- ### Five?
+  Six.
+- ### Seven?
+  Eight.
+- Nine
+- Ten
+- Eleven
+- Twelve
+- ### `dsync.deactivated` <Small>A Directory Sync connection is activated.</Small>
+  Accordion content goes here.
+- ### `dsync.activated` <Small>A Directory Sync connection is activated.</Small>
+  Accordion content goes here.
+- ### `dsync.deactivated` <Small>A Directory Sync connection is deactivated.</Small>
+  Accordion content goes here.
+- ### `dsync.deleted` <Small>A Directory Sync connection is deleted.</Small>
+  Accordion content goes here.
+- One
+- Two
+- Four
+- Three

package/.docs/organized/docs/demo/checklist.mdx

@@ -0,0 +1,33 @@
+---
+title: Checklist
+description: Test page for the checklist component
+originalPath: .tmp-workos-clone/packages/docs/content/demo/checklist.mdx
+---
+
+## Checklist syntax stress test
+
+Adjacent lists shouldn’t be mangled.
+
+- [ ] One two.
+- [x] Three four.
+- [ ] Five six.
+- [ ] Seven eight.
+- Nine
+- Ten
+- Eleven
+- Twelve
+
+- [ ] Implement an SSO UI/UX. See our guide for ideas – [UI/UX Best Practices for IdP & SP-Initiated SSO](/)
+- [ ] Unlock your Production environment by adding your billing information
+  > Only enterprise connections in your Production environment will be charged. Any Google OAuth, Microsoft OAuth, GitHub OAuth, Sign in with Apple, or Magic Link connections will be free.
+- [ ] Set your Production Client’s ID and API Key as environment variables
+- [ ] Secure your Production Project’s API key
+- [ ] Configure production redirect URI(s) in your Product Project. Verify the default redirect URI is correct
+- [ ] Ensure that your application can receive redirects from WorkOS.
+      Depending on your network architecture, you may need to allowlist incoming redirect traffic from `api.workos.com` → WorkOS currently cannot promise that redirect traffic will originate from a static set of IP addresses.
+- [ ] Add Connections for your customers in the Production Environment
+
+- one
+- two
+- three
+- four

package/.docs/organized/docs/demo/code-block.mdx

@@ -0,0 +1,185 @@
+---
+title: Code Block
+description: Test page for the code block component
+originalPath: .tmp-workos-clone/packages/docs/content/demo/code-block.mdx
+---
+
+## From file
+
+<CodeBlock file="install-sdk" title="Install SDK" />
+<CodeBlock file="auth-endpoint" title="Add authentication endpoint" />
+<CodeBlock file="directory-user-example" />
+
+## From markdown
+
+```js language="js" title="Example Code"
+const express = require('express');
+const { WorkOS } = require('@workos-inc/node');
+
+const app = express();
+
+const workos = new WorkOS(process.env.WORKOS_API_KEY);
+const clientId = process.env.WORKOS_CLIENT_ID;
+
+app.get('/callback', async (req, res) => {
+  const { code } = req.query;
+
+  const { profile } = await workos.sso.getProfileAndToken({
+    code,
+    clientId,
+  });
+
+  // Use the information in `profile` for further business logic.
+
+  res.redirect('/');
+});
+```
+
+## From JSX and markdown
+
+<CodeBlock title="Test Code Block">
+
+```js language="js" title="Console JS"
+console.warn('This is a warning!');
+```
+
+```xml language="java"
+<dependency>
+  <groupId>com.workos</groupId>
+  <artifactId>workos</artifactId>
+  <version>{version}</version>
+</dependency>
+```
+
+```jsx
+<Box>
+  {/* highlight-start */}
+  Hello world
+  {/* highlight-end */}
+</Box>
+```
+
+</CodeBlock>
+
+## Without title
+
+```js
+console.log();
+```
+
+## Empty code block
+
+```plain
+
+```
+
+## With tabs across all languages
+
+Input:
+
+```html
+<CodeBlock>
+  <CodeBlockTab file="get-organization-request" title="Request" />
+  <CodeBlockTab file="get-organization-response" title="Response" />
+</CodeBlock>
+```
+
+Output:
+
+<CodeBlock>
+
+```js language="js" title="Request" tab="1"
+import { WorkOS } from '@workos-inc/node';
+
+const workos = new WorkOS('sk_example_123456789');
+
+const organization = await workos.organizations.getOrganization(
+  'org_01EHZNVPK3SFK441A1RGBFSHRT',
+);
+```
+
+```java language="java" title="Request" tab="1"
+import com.workos.WorkOS;
+
+WorkOS workos = new WorkOS("sk_example_123456789");
+
+Organization org = workos.organizations.getOrganization("org_01EHZNVPK3SFK441A1RGBFSHRT");
+```
+
+```go language="go" title="Request" tab="1"
+import "github.com/workos/workos-go/v3/pkg/organizations"
+
+organizations.SetAPIKey("sk_example_123456789")
+
+org, err := organizations.GetOrganization(
+  context.Background(),
+  organizations.GetOrganizationOpts {
+    Organization: "org_01EHZNVPK3SFK441A1RGBFSHRT"
+  }
+)
+```
+
+```json language="json" title="Response" tab="2"
+{
+  "id": "org_01EHZNVPK3SFK441A1RGBFSHRT",
+  "object": "organization",
+  "name": "Foo Corp",
+  "allow_profiles_outside_organization": false,
+  "created_at": "2021-06-25T19:07:33.155Z",
+  "updated_at": "2021-06-25T19:07:33.155Z",
+  "domains": [
+    {
+      "id": "org_domain_01EHZNVPK2QXHMVWCEDQEKY69A",
+      "object": "organization_domain",
+      "domain": "foo-corp.com"
+    }
+  ]
+}
+```
+
+</CodeBlock>
+
+## One language with tabs
+
+Only Java should have tabs here.
+
+Input:
+
+```html
+<CodeBlock file="install-sdk">
+  <CodeBlockTab language="java" file="install-sdk-maven" title="Maven" />
+  <CodeBlockTab language="java" file="install-sdk-gradle" title="Gradle" />
+</CodeBlock>
+```
+
+Output:
+
+<CodeBlock>
+
+```bash language="js" title="Install the WorkOS SDK"
+npm install workos-node
+```
+
+```bash language="dotnet" title="Install the WorkOS SDK"
+nuget install WorkOS.net
+```
+
+```bash language="go" title="Install the WorkOS SDK"
+go get -u github.com/workos/workos-go/...
+```
+
+```xml language="java" title="Maven" tab="java-1"
+<dependency>
+  <groupId>com.workos</groupId>
+  <artifactId>workos</artifactId>
+  <version>VERSION</version>
+</dependency>
+```
+
+```json language="java" title="Gradle" tab="java-2"
+dependencies {
+  implementation 'com.workos:workos:VERSION'
+}
+```
+
+</CodeBlock>

package/.docs/organized/docs/demo/definition-list.mdx

@@ -0,0 +1,35 @@
+---
+title: Definition List
+description: Demo example of a definition list.
+originalPath: .tmp-workos-clone/packages/docs/content/demo/definition-list.mdx
+---
+
+Not a definition item.
+
+Term 1
+: Definition 1
+
+Not a definition item.
+
+Term 2
+: Definition 2
+
+**Term 3**
+: _Definition_ 3
+
+**Term 4**
+: Definition 4
+
+Term 5
+: `Definition 5`
+
+Term 6
+: Definition `6`
+
+Term `7`
+: Definition 7
+
+: Not a definition item.
+
+Not a term
+:

package/.docs/organized/docs/demo/index.mdx

@@ -0,0 +1,7 @@
+---
+title: Demo page
+description: This will be SEO description.
+originalPath: .tmp-workos-clone/packages/docs/content/demo/index.mdx
+---
+
+These pages are for demo purposes only. They are not meant to be used in production.