Ecosystem Improvements Part 2

content/ecosystem/hosting/index.md → content/ecosystem/hosting/_index.md

@@ -1,6 +1,8 @@
 +++
 title = "Hosting"
 template = "ecosystem/hosting.html"
+page_template = "ecosystem/hosting-provider.html"
+sort_by = "title"
 weight = 6
 extra.summary = """
 Everyone can host their Matrix server, but not everybody wants to. These are the providers the Matrix.org Foundation knows about. 
@@ -9,8 +11,8 @@ Everyone can host their Matrix server, but not everybody wants to. These are the
 
 ## Why not matrix.org?
 
-Matrix could be described as what happens when email, instant messaging and
-encryption meet. To be able to use Matrix, you need a Matrix account which is
+[Matrix](@/docs/matrix-concepts/elements-of-matrix/_index.md) could be described as what happens when email, instant messaging and
+encryption meet. To be able to use Matrix, you need a [Matrix account](@/docs/chat_basics/matrix-for-im/_index.md#creating-a-matrix-account) which is
 provided by... a provider! The Matrix accounts identifiers look like
 `@username:example.com`. People on different providers can talk to one another,
 in the same way you can send emails to someone using another email provider.
@@ -19,18 +21,15 @@ Matrix.org is the largest, free provider of Matrix accounts. Many people have an
 identifier like `@username:matrix.org`. This also means that the Matrix.org
 servers are crowded. Using your own provider **as an individual** can not only
 make your Matrix experience snappier, but also give you access to a set of
-pre-configured [bridges](/ecosystem/bridges/) to talk to friends on other networks such as Signal
+pre-configured [bridges](@/ecosystem/bridges/_index.md) to talk to friends on other networks such as Signal
 or WhatsApp.
 
 **Organisations and community managers** will be interested in providers for two
 main reasons: they can proudly display their identity with their own domain
-in username and rooms identifiers, and their administrators remain in control
-of the data of their organisation.
+in username and rooms identifiers when [getting started with a community](@/docs/communities/getting-started/_index.md),
+and their administrators remain in control of the data of their organisation
+through [room administration](@/docs/communities/administration/_index.md) tools.
 
 The following providers have been brought to the attention of The Matrix.org
 Foundation. Please note that The Matrix.org Foundation doesn't endorse them,
 nor provides any warranties for using them.
-
-## Known providers
-
-{{ hosting_providers() }}

content/ecosystem/hosting/communick.md

@@ -0,0 +1,14 @@
++++
+title = "Communick"
+
+[extra]
+image = "communick.png"
+website = "https://communick.com"
+operating_since = "2018"
+b2b = false
+b2c = true
++++
+
+Communick is a service provider for open source messaging and social media platforms. Hosted in Germany, it provides fully managed Synapse homeservers for those looking to be in control of their media presence and also provides a flagship instance at [matrix.communick.com](https://matrix.communick.com) for subscribers that value decentralization and are just looking for a stable, less popular server. As a form to support open source, Communick pledges to give 20% of its profits to the open source projects that it offers, so by becoming a customer you'll be also directly ensuring the continued development of the Matrix ecosystem.
+
+For information about different hosting plans, please check our [Matrix service webpage](https://communick.com/services/matrix).

content/ecosystem/hosting/datanauten.md

@@ -0,0 +1,15 @@
++++
+title = "Datanauten"
+
+[extra]
+image = "datanauten.png"
+website = "https://datanauten.de/"
+operating_since = "2022"
+b2b = true
+b2c = true
++++
+
+- Hosted Homeservers
+- Bridge Solutions: Installation and configuration of Bridges including Slack, Teams, Telegram, and WhatsApp.
+
+The Datanauten Matrix Homeserver offers an easy entry into the open and interoperable communication system of the future.

content/ecosystem/hosting/etke.md

@@ -0,0 +1,23 @@
++++
+title = "etke.cc"
+
+[extra]
+image = "etke.cc.png"
+website = "https://etke.cc"
+operating_since = "2021"
+b2b = true
+b2c = true
++++
+
+- Hosted Homeservers
+- Cloud or on-premises (BYOS)
+- Fully [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) (based on [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-docker-ansible-deploy)). See [our code](https://gitlab.com/etke.cc)
+- [Per-complexity](https://etke.cc/news/lnyorh4ggeh9xadrob_rtuuqu_jj-s-ojfvvfzlmxpm/#pricing-model-changes) pricing (not per-user)
+- 15+ [Matrix bridges & bots](https://etke.cc/order/#matrix-bridges)
+- [Matrix addons](https://etke.cc/order/#matrix-addons) (S3, SSO, workers, etc.)
+- 15+ [Non-Matrix addons](https://etke.cc/order/#non-matrix-addons) (email, VPN, etc.)
+- Fully-managed, but still yours (root SSH)
+
+etke.cc is the only fully FOSS-based Matrix Hosting service. It's operated by a [team](https://etke.cc/about/) of active members of the self-hosting community. Based on [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-docker-ansible-deploy), but hassle-free (SaaS) and contains improvements, extra addons and [support](https://etke.cc/services/support/). Get hosted on rented servers or use your own infra (on any provider) in a non-vendor-lock-in way.
+
+[Matrix Space](https://matrix.to/#/#service:etke.cc) | [Announcements on Matrix](https://matrix.to/#/#news:etke.cc)

content/ecosystem/hosting/fairkom.md

@@ -0,0 +1,23 @@
++++
+title = "fairkom"
+
+[extra]
+image = "fairkom_4c_quer.svg"
+website = "https://fairkom.eu"
+operating_since = "2015"
+b2b = true
+b2c = false
++++
+
+- Hosting (large) homeservers
+- Consulting for Matrix based messenger solutions
+- Customization of clients and apps
+- Voice & video call integration
+- Standard and custom bridges
+- Scalable deployments on kubernetes
+- On premise deployment and operations support
+- Integration with Identity Management Systems
+
+fairkom has been building and hosting chat solutions with various open source frameworks. We are now focussing on Matrix based solutions as interoperability is a key demand of customers and users. Our largest deployment scales for half a million pupils, for whom we developed an app for smartphones with additional educational features. Hosting is climate neutral and GDPR compliant.
+
+[Try fairmatrix](https://www.fairkom.eu/fairmatrix)

content/ecosystem/hosting/federated-computer.md

@@ -0,0 +1,14 @@
++++
+title = "Federated Computer"
+
+[extra]
+image = "federated.png"
+website = "https://federated.computer"
+operating_since = "2022"
+b2b = true
+b2c = true
++++
+
+- Hosted Homeservers
+
+Federated Computer provides Element and Matrix hosting as part of a team collaboration suite (including Nextcloud, Jitsi, Listmonk, Vaultwarden, Baserow, Gitea, Caddy, Castopod, Wireguard, and single-sign-on LDAP).

content/ecosystem/hosting/indiehosters.md

@@ -0,0 +1,15 @@
++++
+title = "IndieHosters"
+
+[extra]
+image = "indiehosters.png"
+website = "https://indiehosters.net"
+operating_since = "2016"
+b2b = true
+b2c = false
++++
+
+- Hosted Homeservers
+- Hosted collaborative tools
+
+We are a French collective specialized in hosting FOSS software and aimed at building a digital common, with a particular emphasis on collaboration.

content/ecosystem/hosting/ossrox.md

@@ -0,0 +1,14 @@
++++
+title = "Ossrox"
+
+[extra]
+image = "ossrox.svg"
+website = "https://ossrox.org"
+operating_since = "2022"
+b2b = true
+b2c = true
++++
+
+- Hosted Homeservers
+
+Ossrox is a company from Germany dedicated to hosting open-source services. Not only has the company name been derived from the motto "Open-Source Software Rocks", but also their corporate culture. The three most important principles of the company are security, privacy and sustainability - thanks to open-source software. In addition to Matrix, Ossrox also provides many other solutions e.g. in the messaging, groupware and web meeting segments.

content/ecosystem/hosting/ungleich.md

@@ -0,0 +1,16 @@
++++
+title = "Ungleich.ch"
+
+[extra]
+image = "ungleich_zerocarbonmatrix.jpg"
+website = "https://matrix.zerocarbon.shop"
+operating_since = "2020"
+b2b = false
+b2c = true
++++
+
+- Hosted Homeservers
+- [Bridge solutions: bridging Slack, Telegram, Whatsapp, IRC and more](https://ungleich.ch/en-us/cms/matterbridge-matrix/)
+- [Customised Matrix development: Custom Authentication/Login, Integration into private networks](https://ungleich.ch/u/products/matrix-custom-development/)
+
+Zero Carbon Matrix is provided by ungleich.ch in Switzerland, in their own Datacenter (datacenterlight.ch) with a strong focus on sustainability. Operating within a repurposed historic building, they utilise pre-owned server systems, passive cooling techniques, and 100% renewable energy. ungleich.ch also specialises in customised Matrix development for communities and organisations.

content/ecosystem/sdks/index.md

@@ -9,17 +9,15 @@ do all the heavy lifting.
 """
 +++
 
-SDKs are pieces of software meant for developers, that take care of the
-technical Matrix protocol calls behind the scenes. They allow them to focus on
-where they can add the most value. If you're not a developer, this section of
-the website is probably not for you.
+SDKs are pieces of software meant for developers: they take care of the
+technical Matrix protocol calls behind the scenes, so you can focus on what
+makes your project unique. If you're not a developer, this section probably
+isn't for you.
 
-There are two fundamental types of SDKs: clients and appservices. This
-distinction is quite academical, and we went for a more pragmatic approach. You
-will find below SDKs by type of product you may want to create (namely: clients,
-bots, bridges). Don't be surprised if the same SDK appears in several sections!
-
-If you are a developer and are not sure what the difference between clients and
-appservices is, please head to [the developers documentation](/docs/matrix-concepts/).
+Pick what you want to build below and we'll show you the SDKs for it. Don't be
+surprised if the same SDK appears under more than one option - most SDKs cover
+several use cases. Not sure which applies to you? Check the
+[developer documentation](/docs/matrix-concepts/) for the difference between
+clients and appservices.
 
 {{ sdk_deck() }}

partials/sdks/bot.md

@@ -1,3 +1,2 @@
-Bot SDKs are used to develop bots no humans will interact with. They handle all
-the Matrix heavy lifting so the developer can focus on what the bot is actually
-useful for. 
+Bot SDKs handle the Matrix heavy lifting for automated accounts nobody talks
+to directly, leaving you free to focus on what the bot actually does.

partials/sdks/bridge.md

@@ -1,3 +1,2 @@
-Bridge SDKs are used to develop appservices meant to either connect a Matrix
-community to a third party chat platform, or to exchange data with another
-platform. 
+Bridge SDKs handle the Matrix heavy lifting for appservices that connect a
+Matrix community to a third-party platform, or exchange data with one.

partials/sdks/client.md

@@ -1,2 +1,2 @@
-Client SDKs are used to develop clients humans will interact with. They handle
-all the Matrix heavy lifting and leave it up to the developer to implement a UI.
+Client SDKs handle the Matrix heavy lifting for apps humans interact with
+directly, leaving you free to focus on the UI.

sass/_base.scss

@@ -18,6 +18,9 @@
     --borders-color: #ddd;
 
     --notice-box-color: #ffcb006b;
+
+    // Used by the shared breadcrumb component (_breadcrumb.scss).
+    --color-text-muted: #555;
 }
 
 * {
@@ -291,13 +294,39 @@ a>code {
 }
 
 .call-to-action {
+    display: inline-flex;
+    align-items: center;
+    gap: 0.4em;
     background-color: #000;
     border: 2px solid #000;
     color: #fff;
     font-size: 1.125rem;
     font-weight: 600;
     border-radius: 1000px;
-    padding: .6em 2em;
+    padding: 0.6em 2em;
+
+    svg {
+        width: 1.1em;
+        height: 1.1em;
+        flex-shrink: 0;
+
+        .fillme {
+            fill: currentcolor;
+            stroke: currentcolor;
+        }
+
+        .fillme-inverse {
+            stroke: #000;
+        }
+    }
+
+    &.secondary svg .fillme-inverse {
+        stroke: #fff;
+    }
+
+    &.secondary:hover svg .fillme-inverse {
+        stroke: #000;
+    }
 
     &.inverted {
         border: 2px solid #fff;
@@ -310,7 +339,7 @@ a>code {
 
             &:hover {
                 background-color: #fff;
-                color: #000
+                color: #000;
             }
         }
     }

sass/_breadcrumb.scss

@@ -0,0 +1,81 @@
+// Breadcrumb navigation
+// Used via macros/breadcrumb.html. Two contexts:
+//   1. Inside .page-header (dark background) - text is white/muted-white
+//   2. Inside .detail-page (light background) - text is muted grey
+
+.breadcrumb {
+    ol {
+        display: flex;
+        flex-wrap: wrap;
+        align-items: center;
+        list-style: none;
+        margin: 0;
+        padding: 0;
+        gap: 0.25rem;
+        font-size: 0.85rem;
+    }
+
+    li {
+        display: flex;
+        align-items: center;
+
+        // Chevron separator before every item except the first
+        & + li::before {
+            content: "/";
+            margin-right: 0.25rem;
+            opacity: 0.45;
+        }
+    }
+
+    a,
+    span {
+        text-decoration: none;
+        line-height: 1;
+    }
+
+    // Dark context (inside .page-header)
+    .page-header & {
+        margin-bottom: 0.75rem;
+
+        a {
+            color: rgb(255 255 255 / 70%);
+
+            &:hover {
+                color: #fff;
+            }
+        }
+
+        // 45% white only clears ~4.4:1 against the black hero background,
+        // just under AA's 4.5:1 for text; 60% keeps it safely above.
+        span {
+            color: rgb(255 255 255 / 60%);
+        }
+
+        li + li::before {
+            color: rgb(255 255 255 / 45%);
+        }
+    }
+
+    // Light context (inside .detail-page)
+    .detail-page & {
+        margin-bottom: 1.25rem;
+
+        a {
+            color: var(--color-text-muted);
+
+            &:hover {
+                color: var(--color-text);
+            }
+        }
+
+        // The current-page label is text, not decoration, so it still needs
+        // to clear WCAG AA (4.5:1); #aaa on white only manages ~2.3:1.
+        span {
+            color: var(--color-text-light);
+        }
+
+        li + li::before {
+            color: #ccc;
+        }
+    }
+}