7 |
8 | # Design Documentation
9 |
10 | The official design documentation, containing our custom design system that we use for all products and services. This documentation site runs on [Docusaurus](https://docusaurus.io), so you may refer to their documentation should you need information on anything that isn't covered here.
11 |
12 | ## Prerequisites
13 | - Git
14 | - Node.js & npm
15 | - Yarn
16 |
17 | ## Installation
18 | Firstly, clone the repository using Git:
19 | ```console
20 | git clone https://github.com/calendso/design.git
21 | ```
22 |
23 | Now, you can install the dependencies with yarn:
24 | ```console
25 | yarn install
26 | ```
27 |
28 | ## Editing
29 | To create, edit and delete documentation pages, you can simply create markdown (.md) files in the `docs/` 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.
30 |
31 | ## Local Development
32 |
33 | ```console
34 | docusaurus start
35 | ```
36 |
37 | This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
38 |
39 | ## Build
40 |
41 | ```console
42 | yarn build
43 | ```
44 |
45 | This command generates static content into the `build` directory and can be served using any static contents hosting service.
46 |
47 | ## Deployment
48 |
49 | ```console
50 | GIT_USER= USE_SSH=true yarn deploy
51 | ```
52 |
53 | If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.
54 |
--------------------------------------------------------------------------------
/babel.config.js:
--------------------------------------------------------------------------------
1 | module.exports = {
2 | presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
3 | };
4 |
--------------------------------------------------------------------------------
/blog/2019-05-28-first-blog-post.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: first-blog-post
3 | title: First Blog Post
4 | authors:
5 | name: Gao Wei
6 | title: Docusaurus Core Team
7 | url: https://github.com/wgao19
8 | image_url: https://github.com/wgao19.png
9 | tags: [hola, docusaurus]
10 | ---
11 |
12 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
13 |
--------------------------------------------------------------------------------
/blog/2019-05-29-long-blog-post.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: long-blog-post
3 | title: Long Blog Post
4 | authors: endi
5 | tags: [hello, docusaurus]
6 | ---
7 |
8 | This is the summary of a very long blog post,
9 |
10 | Use a `` comment to limit blog post size in the list view.
11 |
12 |
13 |
14 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
15 |
16 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
17 |
18 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
19 |
20 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
21 |
22 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
23 |
24 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
25 |
26 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
27 |
28 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
29 |
30 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
31 |
32 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
33 |
34 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
35 |
36 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
37 |
38 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
39 |
40 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
41 |
42 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
43 |
44 | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
45 |
--------------------------------------------------------------------------------
/blog/2021-08-01-mdx-blog-post.mdx:
--------------------------------------------------------------------------------
1 | ---
2 | slug: mdx-blog-post
3 | title: MDX Blog Post
4 | authors: [slorber]
5 | tags: [docusaurus]
6 | ---
7 |
8 | Blog posts support [Docusaurus Markdown features](https://docusaurus.io/docs/markdown-features), such as [MDX](https://mdxjs.com/).
9 |
10 | :::tip
11 |
12 | Use the power of React to create interactive blog posts.
13 |
14 | ```js
15 |
16 | ```
17 |
18 |
19 |
20 | :::
21 |
--------------------------------------------------------------------------------
/blog/2021-08-26-welcome/docusaurus-plushie-banner.jpeg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/calcom/design/7f58825b53ec10d796d155ada4d2e30d4a5221fc/blog/2021-08-26-welcome/docusaurus-plushie-banner.jpeg
--------------------------------------------------------------------------------
/blog/2021-08-26-welcome/index.md:
--------------------------------------------------------------------------------
1 | ---
2 | slug: welcome
3 | title: Welcome
4 | authors: [slorber, yangshun]
5 | tags: [facebook, hello, docusaurus]
6 | ---
7 |
8 | [Docusaurus blogging features](https://docusaurus.io/docs/blog) are powered by the [blog plugin](https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog).
9 |
10 | Simply add Markdown files (or folders) to the `blog` directory.
11 |
12 | Regular blog authors can be added to `authors.yml`.
13 |
14 | The blog post date can be extracted from filenames, such as:
15 |
16 | - `2019-05-30-welcome.md`
17 | - `2019-05-30-welcome/index.md`
18 |
19 | A blog post folder can be convenient to co-locate blog post images:
20 |
21 | 
22 |
23 | The blog supports tags as well!
24 |
25 | **And if you don't want a blog**: just delete this directory, and use `blog: false` in your Docusaurus config.
26 |
--------------------------------------------------------------------------------
/blog/authors.yml:
--------------------------------------------------------------------------------
1 | endi:
2 | name: Endilie Yacop Sucipto
3 | title: Maintainer of Docusaurus
4 | url: https://github.com/endiliey
5 | image_url: https://github.com/endiliey.png
6 |
7 | yangshun:
8 | name: Yangshun Tay
9 | title: Front End Engineer @ Facebook
10 | url: https://github.com/yangshun
11 | image_url: https://github.com/yangshun.png
12 |
13 | slorber:
14 | name: Sébastien Lorber
15 | title: Docusaurus maintainer
16 | url: https://sebastienlorber.com
17 | image_url: https://github.com/slorber.png
18 |
--------------------------------------------------------------------------------
/docs/alerts.md:
--------------------------------------------------------------------------------
1 | # Alerts
2 |
3 | Banners that draw the user's attention to an important message are called alerts. The icons and colors of an alert indicate the type and urgency of the message. Provide critical information in context with alerts to grab the user's attention.
4 |
5 | ## Placement
6 | Alerts should appear as toasts in the bottom right of the screen. The top right of the screen may instead display alerts under certain circumstances.
7 |
8 | 
--------------------------------------------------------------------------------
/docs/branding.md:
--------------------------------------------------------------------------------
1 | # Branding
2 |
3 | We use our own **Cal Sans** typography, made by [Mark Davis](https://twitter.com/MarkFonts) for our logo and every headline.
4 |
5 | ## Logos
6 |
7 | Download our Cal.com logo below:
8 |
9 |
10 |
25 |
26 | ## Press Kit
27 |
28 |
29 | Download
30 | our press kit including screenshots, logos and a photo of the founders.
31 |
32 | ## Brand colors
33 |
34 | | White | Off White | Black | Gray |
35 | | ---------------------- | ----------- | -------------------------- | -------------------------- |
36 | | #FFFFFF | #F5F5F5 | #292929 | #888888 |
37 |
38 |
--------------------------------------------------------------------------------
/docs/buttons.md:
--------------------------------------------------------------------------------
1 | # Buttons
2 | Buttons allow an application to communicate action and direct user intent. Consistent button styles make it easier for a user to recognize areas to take action across an application.
3 |
4 | ## Usage
5 | There are three types of buttons in Calendso. These are used to visually distinguish between the buttons in a hierarchy, and communicate actions and user intent.
6 |
7 | ### Solid buttons
8 | Solid buttons deliberately look heavy in order to direct the user's attention to the action that the application is encouraging the user to take.
9 |
10 | ### Outline buttons
11 | The outline button provides a lighter weight button style. It is commonly used to emphasize a secondary action that complements a primary action or to reduce visual clutter when a number of important actions appear on the page.
12 |
13 | ### Flat buttons
14 | The flat button can be used in multiple situations. It can be used as a tertiary button. It can also be used inline because it is distinct in style and can be recognized as a button.
15 |
16 | ## Buttons vs Links
17 | It is important to use a link (or anchor element) anytime clicking the element will direct you to another page. However, buttons can be given similar visual treatments.In the current page, you can interact by clicking buttons to refresh the content or submit a form.
18 |
19 | ## Placement
20 | There are two distinct patterns when it comes to the placement of a button.
21 |
22 | ### Z Pattern
23 | When tasks are organized from the top-left to the right bottom side of a container, followed by an action caller at the bottom-right of the container, the Z-pattern is a natural way for the user to navigate through content.
24 |
25 | Modals and Wizards follow the Z Pattern
26 |
27 | ### F Pattern
28 | The F-pattern is a natural way to go through content in an unconstrained container, such as a form on the page itself. The user will read the content line-by-line, arriving at a call to action at the end.
29 |
30 | Forms and Cards follow the F Pattern
31 |
32 | 
--------------------------------------------------------------------------------
/docs/colors.mdx:
--------------------------------------------------------------------------------
1 | # Colors
2 |
3 | The color palette for Calendso outlines the consistent set of colors we use to build our interfaces.
4 |
5 | export const Swatch = ({color}) => (
6 |