add images + fix favicons + replace images and new names

content/enterprise/first-things-first.md

@@ -38,7 +38,7 @@ The major key differentiators compared to to other solutions are:
 
 To provide our customer with the high availability and fail over requirements they have, Kerberos Enterprise was built on top of Kubernetes (k8s). This container orchestrator allows us to scale a video surveillance landscape horizontally, and deliver a never-seen high available video surveillance system.
 
-![architecture kubernetes](../../public/images/kerberos-agent-architecture-kubernetes.png)
+<img src="/images/prologue/deployments/onpremise-more-then-5.svg" style="width: 100%"/>
 
 Kerberos Enterprise is installed inside a Kubernetes cluster. It will create pods/deployments for every surveillance camera you want to monitor. Kubernetes will scale and distrubute these pods across your nodes (VM's/Baremetal machines).
 
@@ -50,7 +50,7 @@ By having the power to add nodes to your cluster, you can anticipate to the ever
 
 You install Kerberos Enterprise inside a Kubernetes cluster, but there are no limitations where this cluster will be actually running. This means that whatever security policy you have within your company, you can run it where you want: on-premise, public cloud, private cloud, etc.
 
-![architecture kubernetes](../../public/images/kerberos-agent-architecture-kubernetes-cloud.png)
+<img src="/images/prologue/deployments/cloud-more-then-5.svg" style="width: 100%"/>
 
 ## Licensing
 

content/enterprise/get-started.md

@@ -26,7 +26,7 @@ Important to note is that this web app is relying on the Golang Kubernetes SDK,
 
 Once you open a browser, and navigate to the Factory web application (see installation for the url), you will land on the login page.
 
-![Factory](../../public/images/factory/login.gif)
+<img src="/images/factory/login.gif" style="width: 100%"/><br/>
 
 The default username password of the Factory web applications is:
 
@@ -41,7 +41,7 @@ On the overview page you will find an intuitive overview of the different pages
 
 When working with Kubernetes, Kerberos Enterprise agents are deployed as a deployment. When working with Docker, Kerberos Enterprise agents are deployed as traditional Docker containers.
 
-![Factory](../../public/images/factory/docker-kubernetes.gif)
+<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
 
 ## Kubernetes
 
@@ -56,18 +56,21 @@ On the left menu you will find the Kubernetes section. In this section 3 sub men
 The nodes section lists all the available nodes inside your Kubernetes cluster. It shows a limited amount of information such as the version, the number of Docker images installed on the node, and some basic hardware information.
 
 ![Factory](../../public/images/factory/kerberos-factory-nodes.png)
+<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
 
 ## Deployments
 
 The deployments section will list all the Kerberos Enterprise agents (running as deployments) that you have deployed inside your cluster. This page gives you access to deploy new Kerberos Enterprise agents one by one or in bulk. Next to that you can easily upgrade Kerberos Enterprise agents to a newer version, reboot them, view logging and update the configuration options of the Kerberos Enterprise agent.
 
 ![Factory](../../public/images/factory/kerberos-factory-deployments.png)
+<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
 
 ### Adding a new deployment
 
 There are two options to add a new deployment, single deployments and bulk deployment.
 
 ![Factory](../../public/images/factory/single-bulk-deployment.gif)
+<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
 
 - single deployment
 
@@ -80,12 +83,14 @@ By importing an Excel file, deployments can be created in bulk.
 By specifying the name and corresponding RTSP url in multiple rows, you can deploy your deployments in bulk.
 
 ![Factory](../../public/images/factory/kerberos-factory-add-bulk-deployment-excel.png)
+<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
 
 ### Configuring a deployment
 
 Once you have a running deployment, you should see a green circle next to the deployment, indicating that it is succesfully running. At any time you can configure your deployments by clicking on the <SettingsIcon className="pointer"/> icon. This will open a popup, allowing you to change some settings.
 
 ![Factory](../../public/images/factory/deployment-configuration.gif)
+<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
 
 Following settings can be changed:
 
@@ -93,7 +98,7 @@ Following settings can be changed:
 - Time based conditions,
 - Pre- and postrecording
 - Continious recording
-- Linking to [Kerberos Cloud](/cloud) or [Kerberos Storage](/storage/introduction)
+- Linking to [Kerberos Hub](/hub/first-things-first) or [Kerberos Vault](/vault/first-things-first)
 
 ### Global configuration
 
@@ -102,6 +107,7 @@ Configuration can be specified on a Kerberos Enterprise agent level, this means
 By specifying configurations at a higher level, any Kerberos Enterprise agents will inherit from that configuration, improving the overall maintenance and management of your Kerberos Enterprise agents.
 
 ![Factory Global Config](../../public/images/factory/global-configuration.gif)
+<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
 
 ### Upgrade or reboot a Kerberos Enterprise agent
 
@@ -110,61 +116,63 @@ At Kerberos.io we have fast development cycles, which means that new versions wi
 At any moment you can reboot your Kerberos Enterprise agent. When pressing the reboot button, next to your deployment, Kubernetes will destroy the pod of your deployment, and schedule a new one. This comes in handy, when you noticed one of your Kerberos Enterprise agents is in a stale state.
 
 ![Upgrade and reboot](../../public/images/factory/upgrade-reboot.gif)
-
+<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
 
 ## Pods
 
 When creating a Kerberos Enterprise agent, Kubernetes will create a deployment and schedule a pod. This pod will be  managed by your deployment, and deployed as a Docker container to one of your available nodes. Once a pod dies/ crashes, or whatever unexpected scenario, the deployment will make sure it is deployed again to a different (or the same) node. This makes sure the Kerberos Enterprise agent is in a healthy state at all times.
 
 ![Factory](../../public/images/factory/kerberos-factory-pods.png)
-
+<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
 
 ## Storage and video management
 
 Kerberos Enterprise allows you to scale your video landscape horizontally, using the concept of Kubernetes, and brings a strong backbone for stability and performance. It allows you to avoid reinventing the wheel, and get stuck in the numerious challenges of making an intelligent VMS yourself (we worked on this for 2 years with experienced engineers).
 
-Kerberos Enterprise stores its recordings locally for a short amount of time. This means that long-term storage is not included in the solution. On top of that it also **does not** have a visual component, which allows you te review dashboards or recordings. To overcome these two challenges, long-term storage with extensibility/integration capabilities and visualisation features, following solutions were developed [Kerberos Storage](/storage/introduction) and [Kerberos Cloud](/cloud).
+Kerberos Enterprise stores its recordings locally for a short amount of time. This means that long-term storage is not included in the solution. On top of that it also **does not** have a visual component, which allows you te review dashboards or recordings. To overcome these two challenges, long-term storage with extensibility/integration capabilities and visualisation features, following solutions were developed [Kerberos Vault](/storage/introduction) and [Kerberos Hub](/cloud).
 
-### Kerberos Storage
+### Kerberos Vault
 
-[Kerberos Storage](/storage/introduction) is a solution which makes it able to store recordings from Kerberos Enterprise agents (accross different clusters) at a central place, on the storage provider you want. You can store your recordings in the cloud (AWS S3, Google Cloud Storage, Azure Blob storage) or on premise (Minio).
+[Kerberos Vault](/vault/first-things-first) is a solution which makes it able to store recordings from Kerberos Enterprise agents (accross different clusters) at a central place, on the storage provider you want. You can store your recordings in the cloud (AWS S3, Google Cloud Storage, Azure Blob storage) or on premise (Minio).
 
-On the other hand it's an open platform, as it allows you build extensions and integrations (web apps, mobile apps, machine learning services much more). Kerberos Storage ships with the ability of real-time messaging (Kafka) and a REST API (documented as Swaggger).
+On the other hand it's an open platform, as it allows you build extensions and integrations (web apps, mobile apps, machine learning services much more). Kerberos Vault ships with the ability of real-time messaging (Kafka) and a REST API (documented as Swaggger).
 
 ![architecture storage](../../public/images/kerberos-storage.png)
+<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
 
-To connect one or more Kerberos Enterprise agents to your Kerberos Storage instance, you should open the configuration option and navigate to the `cloud` tab. Once selected you need to fill-in the credentials from your Kerberos Storage account.
+To connect one or more Kerberos Enterprise agents to your Kerberos Vault instance, you should open the configuration option and navigate to the `cloud` tab. Once selected you need to fill-in the credentials from your Kerberos Vault account.
 
-- Storage URI: this is the API endpoint of your Kerberos Storage instance. Typically this is in the following format: `http(s)://api.yourdomain.com/storage`. Where `api.yourdomain.com` should match your Kerberos Storage API endpoint.
+- Storage URI: this is the API endpoint of your Kerberos Vault instance. Typically this is in the following format: `http(s)://api.yourdomain.com/storage`. Where `api.yourdomain.com` should match your Kerberos Vault API endpoint.
 
-- Provider: the name of the provider, which you created on the Kerberos Storage providers page, to which you want to send your recordings to.
+- Provider: the name of the provider, which you created on the Kerberos Vault providers page, to which you want to send your recordings to.
 
-- Directory: this is the subdirectory in which your files will be stored. At the time of writing this should also equal your Kerberos Cloud username, if you plan to upload to Kerberos Cloud.
+- Directory: this is the subdirectory in which your files will be stored. At the time of writing this should also equal your Kerberos Hub username, if you plan to upload to Kerberos Hub.
 
-- Access Key: this should match the access key of one of your Kerberos Storage accounts.
+- Access Key: this should match the access key of one of your Kerberos Vault accounts.
 
-- Secret Access Key: this should match the secret access key of one of your Kerberos Storage accounts.
+- Secret Access Key: this should match the secret access key of one of your Kerberos Vault accounts.
 
 
-![kerberos storage configuration](../../public/images/factory/kerberos-enterprise-storage-setup.gif)
+![Kerberos Vault configuration](../../public/images/factory/kerberos-enterprise-storage-setup.gif)
+<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
 
-### Kerberos Cloud
+### Kerberos Hub
 
-For the visualisation part Kerberos Cloud comes into the picture. Kerberos Cloud is a web app, backed up with a number of microservices, that shows dashboards, live streams, filter recordings and much more. Learn more [about the features and functions here](/cloud).
+For the visualisation part Kerberos Hub comes into the picture. Kerberos Hub is a web app, backed up with a number of microservices, that shows dashboards, live streams, filter recordings and much more. Learn more [about the features and functions here](/cloud).
 
-You have two choices when using Kerberos Cloud, either you send your recordings from your Kerberos Enterprise agents directly to Kerberos Cloud, or you send your recordings to Kerberos Storage, and connect Kerberos Storage to Kerberos Cloud. About the latter more is explained on the [Kerberos Storage page](/storage/get-started).
+You have two choices when using Kerberos Hub, either you send your recordings from your Kerberos Enterprise agents directly to Kerberos Hub, or you send your recordings to Kerberos Vault, and connect Kerberos Vault to Kerberos Hub. About the latter more is explained on the [Kerberos Vault page](/storage/get-started).
 
-Select the Kerberos Cloud option, and copy-paste the credentials from your Kerberos Cloud subscription.
-
-![kerberos storage configuration](../../public/images/factory/kerberos-enterprise-to-cloud.gif)
+Select the Kerberos Hub option, and copy-paste the credentials from your Kerberos Hub subscription.
 
+![Kerberos Vault configuration](../../public/images/factory/kerberos-enterprise-to-cloud.gif)
+<img src="/images/factory/docker-kubernetes.gif" style="width: 100%"/><br/>
 
 - Region: this is the region where your recordings will be stored. Only `eu-west-1` for now (will change, on the roadmap).
 
-- Bucket: the name of the Kerberos Cloud bucket.  Only `kerberosaccept` for now (will change, on the roadmap).
+- Bucket: the name of the Kerberos Hub bucket.  Only `kerberosaccept` for now (will change, on the roadmap).
 
-- Directory: this is your personal directory, and matches your Kerberos Cloud username.
+- Directory: this is your personal directory, and matches your Kerberos Hub username.
 
-- Public Key: this should match the public key of your Kerberos Cloud subscription.
+- Public Key: this should match the public key of your Kerberos Hub subscription.
 
-- Secret Access Key: this should match the private key of your Kerberos Cloud subscription.
+- Secret Access Key: this should match the private key of your Kerberos Hub subscription.

content/opensourcev3/announcement.md

@@ -19,7 +19,7 @@ Kerberos Open Source (v3) is the next generation of Kerberos.io, and is the succ
 
 At the bottom line, we are rebuilding the project from scratch using a different technology stack. We are saying goodbye to C++, PHP (Laravel), BackboneJS and saying hello to Golang and React. Despite the technology changes, we are also changing the architecture, we have put in place a couple of years ago. The biggest change is to run the show inside a single repository, and no longer over seperate repos (machinery and web). Read more about this in the FAQ.
 
-![Kerberos Open Source v2 - vs - v3](../public/images/kerberos-agent-v2-v3.png)
+<img src="/images/opensourcev3/opensource-version2-version3.svg" style="width: 100%"/>
 
 ## FAQ
 

content/opensourcev3/prologue/how.md

@@ -15,7 +15,6 @@ toc: true
 
 When you install Kerberos Open Source or Kerberos Enterprise we will refer to it as the Kerberos Agent. A Kerberos Agent, is a software solution that consist of two pieces: Front-End and Back-End. The Back-End processes the video stream of a single surveillance camera, makes recordings and takes actions (for example sending notifications). The Front-End allows you to review recordings, and configure the Back-End.
 
-
 <img src="/images/prologue/agent-explanation.svg" style="width: 100%"/>
 
 ## Front-End

content/vault/first-things-first.md

@@ -13,23 +13,23 @@ weight: 300
 toc: true
 ---
 
-Kerberos Open Source and Kerberos Enterprise both store recordings on the local disk. To centralise your data at a single place, additional solutions are available.
+Kerberos Opensource and Kerberos Enterprise both store recordings on the local disk. To centralise your data at a single place, additional solutions are available.
 
 ## The options 
 
-### Kerberos Cloud
+### Kerberos Hub
 
-One or more Kerberos Enterprise agents, can store their data directly on [Kerberos Cloud](/cloud), and benefit from the visualisation layer Kerberos Cloud offers. When doing this your recordings will be uploaded inside the Kerberos datacenter (which is a black box for you).
+One or more Kerberos Enterprise agents, can store their data directly on [Kerberos Hub](/cloud), and benefit from the visualisation layer Kerberos Hub offers. When doing this your recordings will be uploaded inside the Kerberos datacenter (which is a black box for you).
 
 ### Kerberos Storage
 
-In addition to that you have the option to Bring Your Own Storage (BYOS), using Kerberos Storage. Kerberos Storage allows you to configure the storage providers you want, and allows you to connect to [Kerberos Cloud](/cloud) in parrallel. These storage provider could live in the cloud such as AWS S3, GCP storage and Azure Blob store, or can be located on premise - at the edge - such as Minio.
+In addition to that you have the option to Bring Your Own Storage (BYOS), using Kerberos Storage. Kerberos Storage allows you to configure the storage providers you want, and allows you to connect to [Kerberos Hub](/cloud) in parrallel. These storage provider could live in the cloud such as AWS S3, GCP storage and Azure Blob store, or can be located on premise - at the edge - such as Minio.
 
 Despite the flexible storage capabilities, Kerberos Storage is also an open platform, which can be used to build extensions (mobile apps, web apps, machine learning services, etc) and integrations. It allows you to leverage a scalable and stable system as a strong backbone for your video analytics solutions, machine learning algorithms, and more.
 
-## Kerberos Cloud
+## Kerberos Hub
 
-Within Kerberos Open Source an Kerberos Enterprise you can upload your recordings to our [Kerberos Cloud](/cloud) environment. This means that your data will be hosted and processed (metadata) in our Kerberos datacenter. For more information about how Kerberos Cloud works [can be found here](/cloud).
+Within Kerberos Open Source an Kerberos Enterprise you can upload your recordings to our [Kerberos Hub](/cloud) environment. This means that your data will be hosted and processed (metadata) in our Kerberos datacenter. For more information about how Kerberos Hub works [can be found here](/cloud).
 
 ![cloud](../../public/images/kerberos-architecture.png)
 
@@ -71,7 +71,7 @@ A couple of usecases are the following ones:
 
 - Continious recording: having continious recordings stored in your Kerberos Storage on premise, you don't want to replicate all your recordings to a Kerberos Storage provider in the cloud (to make them public available). Therefore you could implement custom logic, for example based on a machine learning algorithm, to only replicate recordings which matche a specific scenario.
 
-- On-Demand request: Having Kerberos Cloud, an end-user could initiate a request for upload. By default no recordings are forwarded from your Kerberos Storage on premise to your Kerberos Storage in the cloud. Only when an end user requests one or more recordings, the
+- On-Demand request: Having Kerberos Hub, an end-user could initiate a request for upload. By default no recordings are forwarded from your Kerberos Storage on premise to your Kerberos Storage in the cloud. Only when an end user requests one or more recordings, the
   upload will start for the requested recordings.
 
 ### Open API

layouts/partials/head/favicons.html

@@ -1,5 +1,5 @@
 <meta name="theme-color" content="{{ $.Site.Params.themeColor }}">
-<link rel="apple-touch-icon" sizes="180x180" href="{{ "apple-touch-icon.png" | relURL }}">
-<link rel="icon" type="image/png" sizes="32x32" href="{{ "favicon-32x32.png" | relURL }}">
-<link rel="icon" type="image/png" sizes="16x16" href="{{ "favicon-16x16.png" | relURL }}">
+<link rel="apple-touch-icon" sizes="180x180" href="{{ "favicons/apple-touch-icon.png" | relURL }}">
+<link rel="icon" type="image/png" sizes="32x32" href="{{ "favicons/favicon-32x32.png" | relURL }}">
+<link rel="icon" type="image/png" sizes="16x16" href="{{ "favicons/favicon-16x16.png" | relURL }}">
 <link rel="manifest" href="{{ "site.webmanifest" | relURL }}">

static/doks.svg

@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 36 36"><path fill="#E1E8ED" d="M32.415 9.586l-9-9C23.054.225 22.553 0 22 0c-1.104 0-1.999.896-2 2 0 .552.224 1.053.586 1.415l-3.859 3.859 9 9 3.859-3.859c.362.361.862.585 1.414.585 1.104 0 2.001-.896 2-2 0-.552-.224-1.052-.585-1.414z"/><path fill="#CCD6DD" d="M22 0H7C4.791 0 3 1.791 3 4v28c0 2.209 1.791 4 4 4h22c2.209 0 4-1.791 4-4V11h-9c-1 0-2-1-2-2V0z"/><path fill="#99AAB5" d="M22 0h-2v9c0 2.209 1.791 4 4 4h9v-2h-9c-1 0-2-1-2-2V0zm-5 8c0 .552-.448 1-1 1H8c-.552 0-1-.448-1-1s.448-1 1-1h8c.552 0 1 .448 1 1zm0 4c0 .552-.448 1-1 1H8c-.552 0-1-.448-1-1s.448-1 1-1h8c.552 0 1 .448 1 1zm12 4c0 .552-.447 1-1 1H8c-.552 0-1-.448-1-1s.448-1 1-1h20c.553 0 1 .448 1 1zm0 4c0 .553-.447 1-1 1H8c-.552 0-1-.447-1-1 0-.553.448-1 1-1h20c.553 0 1 .447 1 1zm0 4c0 .553-.447 1-1 1H8c-.552 0-1-.447-1-1 0-.553.448-1 1-1h20c.553 0 1 .447 1 1zm0 4c0 .553-.447 1-1 1H8c-.552 0-1-.447-1-1 0-.553.448-1 1-1h20c.553 0 1 .447 1 1z"/></svg>

static/favicons/browserconfig.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="utf-8"?>
+<browserconfig>
+    <msapplication>
+        <tile>
+            <square150x150logo src="/favicons/mstile-150x150.png?v=1"/>
+            <TileColor>#b4524e</TileColor>
+        </tile>
+    </msapplication>
+</browserconfig>

static/favicons/safari-pinned-tab.svg

@@ -0,0 +1,46 @@
+<?xml version="1.0" standalone="no"?>
+<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 20010904//EN"
+ "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd">
+<svg version="1.0" xmlns="http://www.w3.org/2000/svg"
+ width="700.000000pt" height="700.000000pt" viewBox="0 0 700.000000 700.000000"
+ preserveAspectRatio="xMidYMid meet">
+<metadata>
+Created by potrace 1.14, written by Peter Selinger 2001-2017
+</metadata>
+<g transform="translate(0.000000,700.000000) scale(0.100000,-0.100000)"
+fill="#000000" stroke="none">
+<path d="M3278 6996 c-1 -2 -39 -6 -83 -10 -123 -9 -292 -34 -400 -58 -197
+-43 -473 -126 -580 -173 -16 -7 -46 -19 -65 -26 -69 -27 -397 -196 -487 -253
+-348 -216 -684 -521 -932 -845 -257 -335 -450 -710 -574 -1111 -25 -80 -48
+-161 -53 -180 -4 -19 -8 -37 -9 -40 -12 -48 -34 -163 -40 -204 -2 -15 -7 -35
+-9 -45 -3 -9 -8 -43 -11 -76 -4 -33 -8 -67 -10 -75 -19 -71 -27 -583 -12 -730
+15 -148 19 -176 38 -285 26 -151 26 -151 64 -299 47 -183 111 -371 175 -511
+15 -33 30 -70 34 -83 4 -12 10 -22 14 -22 4 0 40 147 80 328 41 180 75 334 77
+342 33 141 136 457 265 810 119 325 255 726 293 865 25 90 32 131 42 277 7 94
+10 108 36 223 54 236 173 515 257 605 46 49 56 53 99 51 36 -2 140 -116 176
+-193 18 -37 35 -68 38 -68 3 0 19 28 35 62 54 115 118 203 167 230 37 19 82
+-51 234 -362 220 -450 215 -440 243 -446 127 -28 275 -99 381 -181 l69 -53 11
+27 c25 67 113 337 139 429 29 103 36 150 45 288 16 248 147 635 271 803 52 70
+95 92 139 71 16 -9 84 -76 124 -124 15 -18 53 -97 61 -124 6 -22 10 -18 40 45
+69 140 153 250 188 243 39 -7 85 -88 262 -453 45 -93 102 -211 128 -261 l45
+-92 77 -20 c258 -69 469 -245 636 -528 52 -89 55 -92 126 -127 113 -55 303
+-128 538 -207 118 -40 244 -86 279 -102 163 -77 223 -206 157 -340 -40 -81
+-126 -212 -176 -267 -114 -126 -281 -225 -431 -257 -86 -18 -131 -25 -179 -30
+-51 -4 -76 -7 -170 -19 -19 -2 -71 -7 -115 -11 -44 -3 -91 -7 -105 -9 -14 -1
+-61 -5 -105 -9 -99 -8 -179 -17 -182 -20 -1 -1 -18 -47 -38 -102 -39 -109 -89
+-289 -100 -359 -6 -43 -27 -171 -31 -195 -3 -22 -7 -59 -18 -186 -2 -26 8 -45
+51 -99 50 -63 153 -226 153 -244 0 -9 213 -111 233 -111 7 0 17 -4 23 -9 11
+-10 240 -94 444 -162 237 -79 305 -118 355 -203 49 -84 38 -156 -46 -295 -76
+-124 -94 -148 -176 -228 -136 -133 -320 -213 -548 -238 -27 -3 -66 -8 -85 -11
+-19 -2 -60 -7 -90 -9 -139 -11 -197 -16 -220 -20 -14 -2 -61 -7 -105 -10 -44
+-4 -93 -8 -110 -10 -16 -1 -42 -3 -56 -4 -24 -1 -29 -10 -62 -103 -52 -147
+-66 -200 -98 -358 -26 -130 -38 -211 -45 -305 -3 -44 -7 -86 -9 -92 -5 -16
+-14 -16 86 2 192 36 506 125 614 175 11 5 61 25 110 45 121 49 299 141 442
+228 65 39 123 75 128 79 6 4 60 44 120 87 266 190 536 458 744 736 271 362
+472 781 586 1219 32 123 57 243 70 329 22 153 23 166 32 262 10 117 10 495 0
+610 -9 99 -11 116 -22 190 -4 28 -8 59 -10 70 -8 59 -49 252 -71 335 -226 844
+-739 1560 -1462 2041 -57 38 -105 69 -107 69 -3 0 -28 15 -57 34 -76 48 -302
+160 -432 213 -249 103 -535 184 -771 219 -27 4 -57 9 -65 10 -8 2 -42 6 -76 9
+-33 4 -74 9 -90 11 -32 5 -540 14 -546 10z"/>
+</g>
+</svg>

static/favicons/site.webmanifest

@@ -0,0 +1,19 @@
+{
+    "name": "Kerberos.io",
+    "short_name": "Kerberos.io",
+    "icons": [
+        {
+            "src": "/favicons/android-chrome-192x192.png?v=1",
+            "sizes": "192x192",
+            "type": "image/png"
+        },
+        {
+            "src": "/favicons/android-chrome-512x512.png?v=1",
+            "sizes": "512x512",
+            "type": "image/png"
+        }
+    ],
+    "theme_color": "#ffffff",
+    "background_color": "#ffffff",
+    "display": "standalone"
+}

theme.toml

@@ -1,12 +1,11 @@
-name = "Doks"
+name = "Kerberos.io"
 license = "MIT"
-licenselink = "https://github.com/h-enk/doks/blob/master/LICENSE"
-description = "Hugo theme helping you build modern documentation websites that are secure, fast, and SEO-ready — by default."
-homepage = "https://getdoks.org/"
-tags = ["landing page", "documentation", "blog", "minimal", "modern", "customizable", "search", "dark mode", "bootstrap"]
-features = ["security aware", "fast by default", "seo-ready", "development tools", "bootstrap framework", "netlify-ready", "full text search", "page layouts", "dark mode"]
+description = "Kerberos.io is a scalable and cloud agnostic video surveillance and analytics system, which is open for integrations."
+homepage = "https://doc.kerberos.io/"
+tags = ["kerberos.io", "video surveillance", "video analytics", "scalable"]
+features = ["scalable", "high available", "docker", "kubernetes", "opensource", "bring your own storage", "on premise video surveillance"]
 min_version = "0.75.0"
 
 [author]
-  name = "Henk Verlinde"
-  homepage = "https://henkverlinde.com/"
+  name = "Cedric Verstraeten"
+  homepage = "https://kerberos.io/"