diff --git a/docs/developing/guides/appstore-and-integration/build-a-greeter-app.mdx b/docs/developing/guides/appstore-and-integration/build-a-greeter-app.mdx index fa2d1b6b16..079c55b185 100644 --- a/docs/developing/guides/appstore-and-integration/build-a-greeter-app.mdx +++ b/docs/developing/guides/appstore-and-integration/build-a-greeter-app.mdx @@ -74,7 +74,7 @@ title: "Build a greeter app" ; ``` - + A sample line where I used the component in the demo @@ -92,4 +92,4 @@ title: "Build a greeter app" -That's it. You now have a fully functional Greeter app. This is the simplest possible demonstration of how you can build an app and what it can do. There are simply no restrictions on what an app can achieve. \ No newline at end of file +That's it. You now have a fully functional Greeter app. This is the simplest possible demonstration of how you can build an app and what it can do. There are simply no restrictions on what an app can achieve. diff --git a/docs/developing/guides/appstore-and-integration/build-an-app.mdx b/docs/developing/guides/appstore-and-integration/build-an-app.mdx index f789a5bfe2..367bc109b3 100644 --- a/docs/developing/guides/appstore-and-integration/build-an-app.mdx +++ b/docs/developing/guides/appstore-and-integration/build-an-app.mdx @@ -21,7 +21,7 @@ You just need to provide a few inputs and then you will have your app created wi There is pretty much no restriction on what an App can do. For example: - + - Hooking into existing functionalities to enhance them - _In all these cases you need to first check if the app is installed or not. There is_ `_useApp(appSlug)_` _react hook to do that. It gives you the app details if the app is installed._ - Apps that need to connect with third parties like Google Calendar, Apple Calendar, Google Meet. - A very powerful app that has its own data and pages - [Routing Forms App](https://github.com/calcom/cal.com/tree/main/packages/app-store/ee/routing_forms) is a great example of this. @@ -71,7 +71,7 @@ yarn app-store edit --slug APP_NAME * If app-store cli fails at this step, try to run this command manually first. Solve that problem and then re-run cli. The command can fail because there are Prisma migrations that can't be applied automatically. - + A sample failure in create command @@ -83,4 +83,4 @@ A sample failure in create command Once your app is working in your environment, you can publish it to Cal.com App Store by opening a PR [here](https://github.com/calcom/cal.com). -If you need any help feel free to join us on [Discord](https://go.cal.com/discord). \ No newline at end of file +If you need any help feel free to join us on [Discord](https://go.cal.com/discord). diff --git a/docs/developing/guides/auth-and-provision/how-to-setup-oidc-with-okta.mdx b/docs/developing/guides/auth-and-provision/how-to-setup-oidc-with-okta.mdx index 1eeafda6a9..3ae1b163b7 100644 --- a/docs/developing/guides/auth-and-provision/how-to-setup-oidc-with-okta.mdx +++ b/docs/developing/guides/auth-and-provision/how-to-setup-oidc-with-okta.mdx @@ -5,13 +5,13 @@ title: "Setting up OIDC with okta" For example, in Okta, once you create an account, you can click on Applications on the sidebar menu: - + - + - + Enter the Sign in redirect URL (or auth URL) as: @@ -22,7 +22,7 @@ title: "Setting up OIDC with okta" ``` https://app.cal.com/auth/login ``` - + Now you should have the Client Secret and Client ID with you. You would also need the Well Known URL which for Okta is generally of the type: @@ -39,11 +39,11 @@ title: "Setting up OIDC with okta" Visit `https://app.cal.com/settings/organizations/sso` and you should see something like this: - + Click on Configure SSO with OIDC, and then enter the Client Secret, Client ID, and Well Known URL from Step 5, and click save. - + diff --git a/docs/developing/guides/auth-and-provision/how-to-setup-scim-with-okta.mdx b/docs/developing/guides/auth-and-provision/how-to-setup-scim-with-okta.mdx index 0a6dcab4ed..e00d6024ab 100644 --- a/docs/developing/guides/auth-and-provision/how-to-setup-scim-with-okta.mdx +++ b/docs/developing/guides/auth-and-provision/how-to-setup-scim-with-okta.mdx @@ -1,35 +1,35 @@ For example, in Okta, once you create an account, you can click on Applications on the sidebar menu: - + - + Note you will have to fill in the appropriate fields for the SAML or OIDC setup to continue. - [SAML Setup](/developing/guides/auth-and-provision/sso-setup#setting-up-saml-login) - [OIDC Setup](/developing/guides/auth-and-provision/sso-setup#setting-up-oidc-login) - + Once the application is created, under General -> App Settings, click "Edit" and then the checkbox "Enable SCIM provisioning". - + Next, go to your instance of Cal.com and navigate to `https://app.cal.com/settings/organization/dsync` and click configure. - + In the "Configure Directory Sync" form, choose a directory sync name and select "Okta SCIM v2.0" as the "Directory Provider". - + - + In Okta, go to your application. Navigate to the "Provisioning" tab and click "Integration" under "Settings". - + - Under "SCIM connector base URL" enter the "SCIM Base URL" from Cal.com - Under "Unique identifier field for users" enter "email" - Under "Supported provisioning actions" enable: @@ -60,7 +60,7 @@ Set each of these properties to "Map from Okta Profile" and the related field. Under "Apply On" select "Create and Update". - + You can now assign users and groups to the app. @@ -79,4 +79,4 @@ The group name must be spelled exactly as it is shown on Okta. When you push the group to your organization, those users will automatically be added to the team. - + diff --git a/docs/developing/guides/auth-and-provision/sso-setup.mdx b/docs/developing/guides/auth-and-provision/sso-setup.mdx index ac440eb3ef..85a219f6a0 100644 --- a/docs/developing/guides/auth-and-provision/sso-setup.mdx +++ b/docs/developing/guides/auth-and-provision/sso-setup.mdx @@ -63,11 +63,11 @@ This guide explains the settings you need to use to configure SAML with your Ide Visit `/settings/organizations/sso` and you should see something like this: - + Click on Configure SSO with OIDC, enter the Client Secret, Client ID, and Well Known URL from Step 1, and click save. - + Now, when you try to login with SSO, your OIDC provider will handle the authentication. diff --git a/docs/developing/introduction.mdx b/docs/developing/introduction.mdx index 77f6fb2dcc..f6f102670f 100644 --- a/docs/developing/introduction.mdx +++ b/docs/developing/introduction.mdx @@ -3,7 +3,7 @@ title: "Introduction" icon: "presentation-screen" --- - + diff --git a/docs/developing/local-development.mdx b/docs/developing/local-development.mdx index 72552ed466..ceeb4a465e 100644 --- a/docs/developing/local-development.mdx +++ b/docs/developing/local-development.mdx @@ -103,7 +103,7 @@ yarn playwright show-report test-results/reports/playwright-html-report When you're testing out the enterprise features locally, you should see a warning shown in the image below, clarifying the need to purchase a license for such features in production. - + diff --git a/docs/developing/open-source-contribution/introduction.mdx b/docs/developing/open-source-contribution/introduction.mdx index bafdccaeea..6da7c0b7c2 100644 --- a/docs/developing/open-source-contribution/introduction.mdx +++ b/docs/developing/open-source-contribution/introduction.mdx @@ -7,14 +7,14 @@ Contributions are what make the open source community such an amazing place to l - Before jumping into a PR be sure to search [existing PRs](https://github.com/calcom/cal.com/pulls) or [issues](https://github.com/calcom/cal.com/issues) for an open or closed item that relates to your submission. -### Priorities +### Priorities | Type of issue | Priority | | :-------------------------------------------------------------- | :-------------------------------------------------- | -| Minor improvements, non-core feature requests | | -| Confusing UX (... but working) | | -| Core Features (Booking page, availabilty, timezone calculation) | | -| Core Bugs (Login, Booking page, Emails are not working) | | +| Minor improvements, non-core feature requests | | +| Confusing UX (... but working) | | +| Core Features (Booking page, availabilty, timezone calculation) | | +| Core Bugs (Login, Booking page, Emails are not working) | | ### Developing @@ -134,4 +134,4 @@ If `yarn.lock` was committed a while ago and there have been several commits sin - Then push the updated branch: ```git git push origin - ``` \ No newline at end of file + ``` diff --git a/docs/self-hosting/sso-setup.mdx b/docs/self-hosting/sso-setup.mdx index 8d3b42d050..5097cfe30e 100644 --- a/docs/self-hosting/sso-setup.mdx +++ b/docs/self-hosting/sso-setup.mdx @@ -62,7 +62,7 @@ http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname -> lastName 3. Keep handy the Client Secret, Client ID and Well Known URL with you for the next step. 4. Spin up cal.com on your server and login with the Admin user (the email ID of which was provided in step 2 for SAML_ADMINS environment variable). 5. Visit `{BASE_URL}/settings/security/sso` and you should see something like this: - + 6. Click on Configure SSO with OIDC, and then enter the Client Secret, Client ID and Well known URL from the Step 3, and click save. - -7. That's it. Now when you try to login with SSO, your OIDC provider will handle the auth. \ No newline at end of file + +7. That's it. Now when you try to login with SSO, your OIDC provider will handle the auth.