Search
⌃K
🅰

Glossary

A guide to all of the terms we use internally.
LFE
looking for engineer
LFD
looking for designer
LFR
looking for review
SIU
Super Important and Urgent. Use very carefully. (When typing you need to shout a SIUUUU)
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
A way for Cal.com to send data to an external server when something happens (e.g. booking created)
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
The setting that tells Cal.com which URL it’s hosted on
TypeScript
An extension of the language JavaScript, which can do things like check if values are the correct type
API
A way to get data and perform actions on the Cal.com service using code
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”}
​