aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonas Smedegaard <dr@jones.dk>2021-04-04 20:27:04 +0200
committerJonas Smedegaard <dr@jones.dk>2021-04-04 20:27:04 +0200
commitb9c9764dfe5e36f9679c450f7861336d8d27b8cc (patch)
tree4d0ad312417de8c803afb0750a4a09a5fe7d627a
parent96796201fa8b4133f170fb4698ccf0c2ac6a635e (diff)
use mustache templates
-rw-r--r--USE.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/USE.md b/USE.md
index 3dbb71b..59f8d2e 100644
--- a/USE.md
+++ b/USE.md
@@ -1,6 +1,6 @@
# Calendaring introduction
-Anyone can read calendars shared publicly at [[!template id=realm]].
+Anyone can read calendars shared publicly at {{organisation}}.
Your personal [[account]] grants read-only access to closed-group shared calendars.
@@ -23,7 +23,7 @@ When you only need to read a calendar,
the best (most efficient) is to subscribe to an **iCal** calender:
1. Copy address of relevant calendar from web page
- <http://[[!template id=eventhost]]/>.
+ <http://{{eventhost}}/>.
2. Open calendaring client, and add new account profile of type "ical".
3. Paste the calendar address as server address.
@@ -37,14 +37,14 @@ To both read a calendar and help maintain its content,
you need to setup a **CalDAV** profile:
1. Open calendaring client, and add new account profile of type "CalDAV".
- 2. Server address: **[[!template id=eventhost]]:8443**
+ 2. Server address: **{{eventhost}}:8443**
3. Username and password: Either personal or calendar-group account credentials.
If above fails, or if you want to specifically pick a single calender,
use this alternative approach:
1. Copy address of relevant calendar from web page
- **https://[[!template id=eventhost]]:8443/calendars/users/USERNAME/**
+ **https://{{eventhost}}:8443/calendars/users/USERNAME/**
(replace USERNAME with either personal or calendar-group account name)
2. Open calendaring client, and add new account profile of type "CalDAV".
3. Paste the calendar address as server address.