Calendar

Your own calendar, the ones you share, and one for everybody.

Star · 0 Nobody has starred it yet

What it does

A calendar of your own, made the first time you look, named after you
One calendar everybody on the server sees and writes in
Shared calendars: make one, add people, and they are told
Every calendar you can see drawn at once, each in its own colour
Times on the wall clock: ten o'clock is ten o'clock, in June and in October
All-day events that run over as many days as they need

Add it to your cloud

$ cm quill add calendar

Or, as an administrator, open Administration → Quills in the app and choose Calendar. Either way your cloud shows you everything below and waits for your yes.

Standard. The installer offers Calendar when you set up a new cloud, so you may have it already. How installing works

What it adds to your cloud

Datamodels

The kinds of data it works with. Records belong to the people who write them, not to the quill: removing it leaves every one where it is.

Uses

Calendar `calendar`

foundational

Your own, one you share, or everybody's.

Name name text, one linerequired Encrypted
Colour colour text, one line Encrypted

Uses

Event `event`

foundational

A title and two moments, on a calendar. Times are wall-clock times.

Calendar calendar link to Calendarrequired · deleted with its calendar Indexed
Title title text, one linerequired Encrypted
Starts at starts_at date and timerequired Indexed
Ends at ends_at date and time Indexed
All day all_day yes or no Indexed
Location location text, one line Encrypted
Notes notes Markdown Encrypted

Indexed fields are kept plain, so your cloud can sort and filter by them. Encrypted fields are encrypted before they reach the disk.

Screens

CalendarA calendar of events. This kind of screen is drawn in a later release.

Each is a tab, drawn by your cloud itself on every surface:

Phonethe web app, made for the phone
Webthe full web app, in a browser
Terminalthe terminal app
Command linecm calendar
Assistanttools for your assistant, as you

Comes with

A calendar for each person, the first time they open Calendar.yours · “your name”

A calendar, when it is installed.everybody · “Everybody”

Its own code

None. Everything it does is declared in quill.toml and run by your cloud itself.

In its own words

A Quill for Cloudmorrow: your own calendar, the ones you share with the people you live or work with, and one the whole server shares.

Yours. Everybody has exactly one, made the first time they look and named after them. Nobody else sees it.
Shared. Anybody can make one and put people in it. There is no invitation to accept: they are added, they are told, and they can leave.
Everybody's. One calendar the whole server sees and writes in, and nobody can leave.

Every calendar you can see is drawn at once, each event in the colour of the calendar it is on — a calendar you have to switch between is one that lets you double-book yourself.

Times are the times on the wall. "The dentist at ten" is stored as 2026-10-01T10:00, with no zone, and is at ten on every screen in October and in June alike. An all-day event is a bare date, and its end is the last day it is on.

What it adds to your Cloudmorrow


Datamodels	uses the foundational `calendar` (a space: personal, shared or public) and `event` (in a calendar), domain Calendars
Screens	one calendar: a month and the day's list on the phone, a week and a month on the web app, a month and the day in the terminal, `cm calendar list --from --to` and `add`, and to your assistant
Jobs	none
Datasets	`yours`: a personal calendar for each person, named after them; `everybody`: one public calendar for the server
Services, webhooks, APIs	none

It contains no code: everything above is declared in quill.toml.

Working on it

See CLAUDE.md. In short: cm quill check, then cm quill dev.

Licence

AGPL-3.0-or-later.