Calendar and contacts ā
The calendar shows the events of the folder open ā or, with no folder open, of the documents kept in the browser. Open it with š
Calendar on the start screen, š beside the small calendar of the folder panel, or Calendar in the command palette (Ctrl+Shift+P).
Events are notes ā
Each event is a Markdown note of the Events folder (CAL-001), filed in a folder per year, month and day, and named after its day and title (Events/2026/10/05/2026-10-05 Kick-off.md); moved to another day, its note moves to that day's folder, under the same name, so that the links to it still find it:
---
title: Kick-off
type: "[[Event]]"
start: 2026-10-05T09:30
end: 2026-10-05T10:30
location: Room 12
attendees:
- "[[Ada Lovelace]]"
calendar: Work
recurrence: FREQ=WEEKLY;BYDAY=MO
uid: 0b1cā¦@pwo
---
The agenda, the minutes: the text of the note.So an event is linked from other notes ([[2026-10-05 Kick-off]]), shows its attendees' notes as links (and appears in their backlinks), is found by the search and its tags, and its properties are shown and changed like those of any note. An event of whole days has a start and end without time ā the end being the day after the last one, as calendars count. Changing an event from the calendar keeps the other properties and the text of its note.
Views ā
- Month, Week, Day and Agenda (the next 30 days), today marked, and in the week and day views a red line at the time it is.
- ā¹ āŗ go back and forth, Today comes back; the keys
āā,t(today),mwda(the views) andn(a new event) do the same. - The events of a calendar (
calendar:of the note: Work, Homeā¦) have their colour.
Creating and changing events ā
- A click on a day of the month, or on an hour of the week or day, opens the window of a new event there; ļ¼ New event too.
- A click on an event opens its window: title, whole day, start and end (moving the start moves the end), repeat (every day, week, month, year), location, attendees (the notes of people are proposed), calendar and description. Open the note opens it; Delete removes it with its note.
- Dragged to another day or hour, an event moves ā its series with it, for a repeating event.
With the daily notes ā
A click on the date of a day opens its daily note (created if needed). A new daily note lists the events of its day in its events property, and an event created for a day whose daily note exists is added to it (CAL-005).
iCalendar files ā
āŖ imports a .ics file (from another calendar): each event becomes a note of Events; an event already imported is updated, not repeated. ā© exports the events as a .ics file (CAL-003). Times given in a time zone or in UTC are shown at your local time; repeating events follow their rule.
Contacts ā
š„ Contacts (start screen, command palette) shows the people of the folder: each is a note of the People folder (CONTACT-001):
---
title: Ada Lovelace
type: "[[Person]]"
first name: Ada
last name: Lovelace
emails:
- ada@example.org
phones:
- "+33 6 12 34 56 78"
organization: "[[Analytical Engines]]"
birthday: 1815-12-10
tags:
- person
---
What you know of her, met where, about what.- The list is searched by name, e-mail, organisation or
#tag(CONTACT-002); the card of a contact shows its fields ā an e-mail to write to, a number to call, its organisation's note ā then the events it attends and the notes linking to it, with the words around each link: write[[Ada Lovelace]]in a note, or name her among the attendees of an event. - ļ¼ New contact, Edit and Delete change the contacts; the name shown follows the first and last names until you write it.
- Birthdays are shown in the calendar, every year (CONTACT-004); a click opens the contact.
- āŖ imports a
.vcffile (vCard 3.0 or 4.0, from a phone or another address book) as notes; ā© exports the contacts as a.vcffile (CONTACT-003).
Reminders ā
An event can have a reminder (NOTIF-001): at the time, or 5 minutes to a day before ā Reminder in its window; new events take the one chosen in ā Settings ā General ā Reminder of new events. Reminders of a calendar imported or synchronised (its alarms) are kept, and written back.
Tick Notify the reminders of events in the settings: the browser asks whether the application may notify. While the application is open ā even in the background ā each reminder is shown once, by the system and in the application; a click opens the event.
Without a server, a closed application cannot notify: keep it open, or let the calendar of your phone remind you of the events synchronised by CalDAV. On a phone, notifications need the application installed to the home screen.
Interactions ā
The card of a contact gathers its interactions (CONTACT-006), the latest first: the events it attends, the lines of daily notes naming it, the other notes linking to it ā with First met and Last contact above.
š Add an interaction (a meeting, a call, an e-mail, a message) writes a line in the daily note of its day:
- 14:05 š Call ā [[Ada Lovelace]]: agreed on the review.The kind is yours to choose: type š½ Lunch, Visit of the lab ā an emoji first if you like. The kinds found in the daily notes of the contact and those you typed lately are offered again with the ones built in.
The journal stays where things happened, the contact finds them back by its link; its note keeps first met and last contact up to date.
AI agents ā
The assistant ā or an agent of yours reached through WebMCP, one reading your e-mail for example ā has tools for the calendar and the contacts while one of them is open (CAL-007, CONTACT-007): find a contact, read it with its interactions, create or update it, add an interaction (an e-mail read or sent goes to the daily note of its day; an unknown sender becomes a contact), list and create events. The tools that change notes are marked so, and ask before acting as the other tools of the assistant do.
Servers: CalDAV and CardDAV ā
The calendars and address books of a server ā Nextcloud, or any CalDAV / CardDAV server ā are kept in step with the notes, both ways (CAL-006, CONTACT-005):
- Add the account once, as for files: the address of the server, your user name and an app password.
- ā in the calendar (or the contacts) ā Find: the calendars of events (or the address books) of the account; tick those to keep, then Save.
- ā³ synchronises them now; they are also synchronised each time the calendar or the contacts open.
What happens:
- An event of the server becomes a note of
Events(itscalendarthe name of its calendar), a contact a note ofPeople; a new note of the folder goes to the calendar named by itscalendarā else the first one ticked ā and a new contact to the first address book. - A change on one side reaches the other at the next synchronisation. What the server holds besides the fields of the note ā reminders, organiser, the answers of attendees, a photo, the labels of phones ā is kept.
- Changed on both sides: the note takes the server's version, and yours is kept as a copy tagged
#conflict, named "⦠(conflict)", which is not sent: keep what you want, then remove the copy. - Removed on one side and unchanged on the other: removed there too.
- What was seen at the last synchronisation is kept in
.pwo/sync.jsonof the folder.
The server must allow the application's address (CORS) on its DAV paths, with the methods PROPFIND, REPORT, PUT and DELETE: see server setup.
Folders ā
Events go to Events and contacts to People, at the root of the folder open; both are notes like the others: move, rename or link them freely.