Added a few .well-known examples.

matrix/element-call/README.md

@@ -363,7 +363,7 @@ necessary:
 
 Now tell the clients about this widget.  Create
 `.well-known/element/element.json`, which is opened by Element Web, Element Desktop
-and ElementX to find the Element Call widget. It should this:
+and ElementX to find the Element Call widget. It should look this:
 
 ```
 {

matrix/element-call/element.json

@@ -0,0 +1,6 @@
+{
+    "call":
+    {
+        "widget_url": "https://call.example.com"
+    }
+}

matrix/synapse/README.md

@@ -180,7 +180,11 @@ Pointing clients to the correct server needs this at
 Very important: both names (example.com and matrix.example.com) must be A
 and/or AAAA records in DNS, not CNAME.
 
-See [nginx](../nginx) for details about how to publish this data.
+You can also publish support data: administrator, security officer, helpdesk
+page. Publish that as `.well-known/matrix/support`.
+
+See the included files for more elaborate examples, and check
+[nginx](../nginx) for details about how to publish this data.
 
 
 # E-mail {#Email}

matrix/synapse/well-known-client.json

@@ -0,0 +1,12 @@
+{
+    "m.homeserver": {
+        "base_url": "https://matrix.example.com"
+    },
+
+    "org.matrix.msc4143.rtc_foci":[
+        {
+            "type": "livekit",
+            "livekit_service_url": "https://livekit.example.com"
+        }
+    ]
+}

matrix/synapse/well-known-server.json

@@ -0,0 +1 @@
+{"m.server": "matrix.example.com"}

matrix/synapse/well-known-support.json

@@ -0,0 +1,17 @@
+{
+    "contacts": [
+        {
+            "email_address": "admin@example.com",
+            "matrix_id": "@john:example.com",
+            "role": "m.role.admin"
+	},
+
+        {
+            "email_address": "security@example.com",
+            "matrix_id": "@bob:example.com",
+            "role": "m.role.security"
+        }
+    ],
+
+    "support_page": "https://support.example.com/"
+}