docs: /multiple-clients

Author: brillout

packages/telefunc.com/headings.ts

@@ -28,6 +28,10 @@ const headingsDetached: HeadingDetachedDefinition[] = [
     title: 'Initial Data',
     url: '/initial-data',
   },
+  {
+    title: 'Multiple Clients',
+    url: '/multiple-clients',
+  },
 ]
 
 const headings: HeadingDefinition[] = [

packages/telefunc.com/pages/event-based/+Page.mdx

@@ -263,8 +263,6 @@ Telefunc shows a warning if you don't follow the naming convention — you can r
 > [Feel free to reach out](https://github.com/brillout/telefunc/issues/new) if you have questions.
 
 
-## Exception: several clients
+## See also
 
-If your telefunctions are used by multiple clients, it can make sense to define a few generic telefunctions that cover all clients, instead of creating different telefunctions for each client.
-
-> Alternatively, you can deploy one Telefunc server per client to preserve the fast development speed of tailored telefunctions.
+- <Link href="/multiple-clients" />

packages/telefunc.com/pages/multiple-clients/+Page.mdx

@@ -0,0 +1,10 @@
+import { Link } from '@brillout/docpress'
+
+If your telefunctions are used by multiple clients, we recommend deploying one Telefunc server per client, in order to preserve all the <Link href="/event-based">benefits of event-based telefunctions</Link>. In other words, each client uses a different set of event-based telefunctions.
+
+That said, if the client needs are similar, it case make sense to <Link href="/event-based#opt-out">opt-out of event-based telefunctions</Link> and create telefunctions that are slight more generic.
+
+
+## See also
+
+- <Link href="/event-based" />