cal.pub0.org/apps/docs
Omar López c5444c84fc
Migrate docs to mono repo (#1814)
* Initial commit

Created from https://vercel.com/new

* Update config

* Homepage

* Self-hosting

* Integrations

* More docs pages

* Developer docs

* Update billing.mdx

* Update install.mdx

* Fix install guide

* More fixes

* Adding CSS guide

* Fix capitalisation on Microsoft page

* Added delete account update

* Added Zapier integration question

* Added GMeet integration part

* Added Delete Account to Settings

* unnecessary question mark

* Added a link to Settings

* Added stuff in Billing

* Added a link to cal.com/signup

* Capitalization

* Added language change

* Added more stuff in Event Types

* Added how to change email

* Added FAQ page

* Spelling mistake

* Added a title to FAQ

* Added more stuff to Billing

* Availability multi-booking

* Deleted from Availability added to FAQ

* Added to FAQ

* Removed the dot

* Added stuff to FAQ

* Add license warning to adding CSS page

* Update docker.mdx

* Add import instructions

* removed readme until we have our own

* updated favicon, added cal sans

* added new cal sans

* Create README.md

* renamed all github links

* renamed more github links

* Added team's Event Types

* Clarified the Google Meet integration

* Spelling error

* Added primary calendar tutorial

* Removed tutorial

* primary calendar selection

* Moved to subdirectory

* Matching configs

* Shares eslint config between web and docs

* Removes format-schemas

* Updates env file location in turbo

* [docs] updates monorepo intructions

Co-authored-by: baileypumfleet <pumfleet@hey.com>
Co-authored-by: Peer Richelsen <peeroke@gmail.com>
Co-authored-by: milospuac <97884287+milospuac@users.noreply.github.com>
Co-authored-by: Peer Richelsen <peeroke@richelsen.net>
2022-02-11 12:33:35 -07:00
..
pages Migrate docs to mono repo (#1814) 2022-02-11 12:33:35 -07:00
public Migrate docs to mono repo (#1814) 2022-02-11 12:33:35 -07:00
.eslintrc.js Migrate docs to mono repo (#1814) 2022-02-11 12:33:35 -07:00
.gitignore Migrate docs to mono repo (#1814) 2022-02-11 12:33:35 -07:00
.nvmrc Migrate docs to mono repo (#1814) 2022-02-11 12:33:35 -07:00
.prettierignore Migrate docs to mono repo (#1814) 2022-02-11 12:33:35 -07:00
LICENSE Migrate docs to mono repo (#1814) 2022-02-11 12:33:35 -07:00
README.md Migrate docs to mono repo (#1814) 2022-02-11 12:33:35 -07:00
next.config.js Migrate docs to mono repo (#1814) 2022-02-11 12:33:35 -07:00
package.json Migrate docs to mono repo (#1814) 2022-02-11 12:33:35 -07:00
theme.config.js Migrate docs to mono repo (#1814) 2022-02-11 12:33:35 -07:00
yarn.lock Migrate docs to mono repo (#1814) 2022-02-11 12:33:35 -07:00

README.md

Cal.com Documentation

The official product, support and developer documentation, containing information and guides about using the product as well as support for self-hosted installations. This documentation site runs on Nextra, so you may refer to their documentation should you need information on anything that isn't covered here.

Prerequisites

  • Git
  • Node.js & npm
  • Yarn

Installation

Firstly, clone the repository using Git:

git clone https://github.com/calcom/docs.git

Now, you can install the dependencies with yarn:

yarn install

Editing

To create, edit and delete documentation pages, you can simply create markdown (.mdx) files in the pages/ folder. You can edit Markdown with any text editor, but VS Code and WebStorm have side-by-side previews so you can see your formatted content whilst writing markdown.

You will also need to add it as an entry to the meta.json file found in whichever directory that the .mdx file is in.

Local Development

yarn dev

This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.

Build

yarn build

This command generates static content into the build directory and can be served using any static content hosting service.

How to easily contribute

Existing Page

  1. From the documentation's GitHub repository, head to the folder called 'pages' and open it.
  2. From here you can view all current pages on the documentation site. Select the page you would like to contribute to.
  3. You should now be able to view the page you have selected. Located at the top right of the page will be a pencil icon. Pressing this will bring you up an editor to edit and make changes. You can add formatting using the buttons at the top, which will automatically insert the relevant markdown content needed to style the text.
  4. From here make the changes you wish to make.
  5. At the bottom of the screen will be a 'Propose Changes' box, fill in all the relevant details such as title and description then press the green 'Propose Changes' button.
  6. Your changes have been saved, to submit them for review, located on your screen, press the green 'Create Pull Request' button.
  7. Fill in all the relevant details such as title and description and after finalize the submission.

You have now successfully edited and submitted changes to our documentation site.

Creating a New Page

  1. From the documentation's GitHub repository, head to the folder called 'pages' and open it.
  2. From here you can view all current pages on the documentation site. At the top of your screen press the 'New file' button.
  3. You should now be able to view the page you have created. Remember when renaming the document to put .mdx at the end of the file name.
  4. From here make the changes you wish to make. Such as creating a title, sub-title and body text.
  5. At the bottom of the screen will be a 'Propose Changes' box, fill in all the relevant details such as title and description then press the green 'Propose Changes' button.
  6. Your changes have been saved, to submit them for review, located on your screen, press the greem 'Create Pull Request' button.
  7. Fill in all the relevant details such as title and description and after finalize the submission.

You have now successfully created and submitted changes to our documentation site.