-
-
Notifications
You must be signed in to change notification settings - Fork 0
Calendar and Events
Use the calendar for school events, appointments, training, routines, family plans, and anything that needs a date or time.
- month and week views
- event create, duplicate, edit, and delete
- recurring events with RRULE-compatible rules
- event colors and categories
- event locations and map links
- curated family-friendly event icons
- birthday indicators in the calendar
- day detail panel for focused daily planning
- ICS import/export
- CalDAV sync through Phone Sync
- Add the next few real household events.
- Use categories and colors for quick scanning.
- Add event icons for common family events such as sports, dentist, school, music, swimming, errands, or travel.
- Add locations when the event requires leaving the house.
- Add recurring rules only for routines that are stable.
- Add contacts with birthdays so birthday indicators appear automatically.
Use Duplicate event on an event card when a new event should start with the same details.
- Open the source event in the month or week view.
- Select Duplicate event.
- Adjust the prefilled title, date, time, location, assignment, color, or icon.
- Select Create event to save the copy.
Opening the duplicate form does not create an event. The new event is saved only after confirmation and remains independent from the source event. Imported calendar events can be used as templates, but the copy is created as a local Tribu event. Recurrence is not copied automatically.
Tribu supports CalDAV for calendar sync. Use a Personal Access Token as the DAV password.
Expected behavior:
- events created in Tribu can appear in a compatible phone calendar
- events created on a connected phone can sync back into Tribu when write scopes are enabled
- one family has one calendar URL
- reverse proxy rules must forward
/davand/.well-known/caldav
- Check that the DAV URL is copied from Settings > Phone sync.
- Use your Tribu email as username and a Personal Access Token as password.
- Confirm the token has
calendar:readorcalendar:writescopes. - Confirm your reverse proxy forwards
/davand/.well-known/caldavto the backend.
- Use icons only for event types that need fast recognition.
- Keep colors consistent by category.
- Prefer recurring events for stable routines, not temporary plans.
Birthdays come from the birthday/contact data model and are surfaced as calendar indicators. Normal events can use event icons and colors, but they remain calendar events.