LogoLogo
  • πŸ‘‹Cal.com Handbook
  • The Company
    • ❓What is Cal.com?
    • πŸ“ˆMission, Vision and Values
    • πŸ…°οΈGlossary
    • πŸ“ˆOrganization Chart
  • HR & Careers
    • πŸ‘·Contract-to-hire trials
    • πŸ›«Onboarding
    • πŸ†IC Levels
      • ⛰️Engineering Levels
        • πŸ•΅οΈIC1 Engineer (Code Cadet)
        • πŸ‘·β€β™€οΈIC2 Engineer (Code Craftsperson)
        • πŸ§˜β€β™€οΈIC3 Engineer (Code Connoisseur)
        • πŸ§™β€β™‚οΈIC4 Engineer (Code Wizard)
    • πŸ’‘Sharing your views
    • πŸ’ΈBonus & Equity Structure
  • Policies
    • πŸ–οΈVacations
    • πŸ’³Expenses
    • πŸ—£οΈCommunications
  • Engineering
    • πŸ””Managing Notifications
    • ⭐Valuable Bookmarks
    • πŸ›How to report issues
    • πŸ’»How we work on Tickets
    • πŸ”₯What to do during Emergencies
    • βœ…PR Reviews
    • β˜‘οΈSelf-reviews
    • πŸ“šKeeping Docs up-to-date
    • 🌐HTTPS & Subdomains
    • 🎯Best practices
      • Data fetching
      • Avoid Prop Drilling
      • Prefer defaultHandler for simple API handlers
      • Prefer inferred types over explicit ones
      • Prefer early returns
      • Avoid comparing multiple values with `includes`
      • Validate using zod instead of type casting
      • Prefer Composition over Prop Drilling
      • Prefer ternaries over Short Circuiting β€œ&&” for React Components
      • Don't modularize prematurely
      • Only select data you need
      • Disallowing the use of unrestricted Metadata fields
      • E2E Tests Best Practices
    • πŸ’»Codebase
      • πŸ”“Keeping the lock file in sync
      • 🚫Git Private Submodules
      • 🏎️Monorepo / Turborepo
      • 🌝Deploying to Production
      • ☁️Deployment
      • πŸ’»Debug Desktop App
      • 🚩Enabling/Disabling Features
    • πŸ”ΊResolving failed migration on Vercel Preview
    • πŸ”¦Cal.com Status Page
  • Customer Success
    • πŸ’ŸTone
  • Marketing
    • 🎬Media
    • ☝️How to add a new Tip to Sidebar
  • 🀲Sales
    • Operations Stack
Powered by GitBook
On this page

Was this helpful?

  1. The Company

Glossary

A guide to all of the terms we use internally.

LFE

looking for engineer

LFD

looking for designer

LFR

looking for review

SIU

Destination calendar

The calendar that events are created on

Monorepo

Multiple projects (e.g. app, docs and API) all in one GitHub repository

Commit

Addition to the code

Pull request (PR)

The way in which code is reviewed and then added to the codebase. A PR is made of commits

Merge

If a PR is good, it is merged, which accepts the changes and β€˜merges’ them into the codebase

i18n

Internationalization (translating text)

a11y

Accessibility

CTR

Click-Through Rate

UI

User Interface

UX

User Experience

Event types

Different events that you offer on your booking link. For instance, hiring (30 mins) and performance review (60 mins) are both examples of event types.

Opt-in booking

An event type where you must accept/deny the booking before it’s created

Slots

Time slots that are offered on your booking page that are determined to be free

RFC

Request for comments. Essentially a proposal, where we’re looping in the team to get their thoughts

Round robin

Schedules each person in the team. If a team is made up of persons A, B and C, the first booking goes to person A, second goes to B, third to C etc.

CalDAV

An open standard for calendars. Essentially a ton of different calendar providers (e.g. Yandex, NextCloud) all support CalDAV, which allows you to connect those providers to Cal.com

Kangaroo

A tall animal that hops around

Webhooks

SAML SSO

A way for enterprises to let everyone in their company log in to any application, including Cal.com

Vercel

The platform that builds our code and publishes it to the live site

e2e

End to end testing. Essentially a robot that checks if our application is working each time we push code

Linting

A way to make code look nice and neat

.env

A file where you configure settings for Cal.com, like your database and email servers

WEBAPP_URL

TypeScript

An extension of the language JavaScript, which can do things like check if values are the correct type

API

NPM package

Dependencies (things your app uses) can be packaged into NPM packages, which are bundles of code that you can use in other applications

Metadata

Data that is in a computer readable format, like JSON, which looks like {”make”: β€œVolvo”, β€œmodel”: β€œV40”}

PreviousMission, Vision and ValuesNextOrganization Chart

Last updated 2 years ago

Was this helpful?

Super Important and Urgent. Use very carefully. (When typing you need to shout a )

A way for to send data to an external server when something happens (e.g. booking created)

The setting that tells which URL it’s hosted on

A way to get data and perform actions on the service using code

SIUUUU
Cal.com
Cal.com
Cal.com
πŸ…°οΈ
Page cover image