diff --git a/modules/ROOT/images/backup-chain-aggregation.svg b/modules/ROOT/images/backup-chain-aggregation.svg index 7323dc17d..bd59cae57 100644 --- a/modules/ROOT/images/backup-chain-aggregation.svg +++ b/modules/ROOT/images/backup-chain-aggregation.svg @@ -1 +1,25 @@ - + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/modules/ROOT/images/cluster-on-k8s.svg b/modules/ROOT/images/cluster-on-k8s.svg new file mode 100644 index 000000000..08fb8e674 --- /dev/null +++ b/modules/ROOT/images/cluster-on-k8s.svg @@ -0,0 +1,81 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/modules/ROOT/images/federation-sharding.png b/modules/ROOT/images/federation-sharding.png deleted file mode 100644 index a34e6af96..000000000 Binary files a/modules/ROOT/images/federation-sharding.png and /dev/null differ diff --git a/modules/ROOT/images/federation-sharding.svg b/modules/ROOT/images/federation-sharding.svg new file mode 100644 index 000000000..b95fe20fc --- /dev/null +++ b/modules/ROOT/images/federation-sharding.svg @@ -0,0 +1,73 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/modules/ROOT/images/manage-dbs-community.png b/modules/ROOT/images/manage-dbs-community.png deleted file mode 100644 index f3ff5068e..000000000 Binary files a/modules/ROOT/images/manage-dbs-community.png and /dev/null differ diff --git a/modules/ROOT/images/manage-dbs-community.svg b/modules/ROOT/images/manage-dbs-community.svg new file mode 100644 index 000000000..fd87ba36e --- /dev/null +++ b/modules/ROOT/images/manage-dbs-community.svg @@ -0,0 +1,9 @@ + + + + + + + + + diff --git a/modules/ROOT/images/manage-dbs-default.png b/modules/ROOT/images/manage-dbs-default.png deleted file mode 100644 index 24ddaeae2..000000000 Binary files a/modules/ROOT/images/manage-dbs-default.png and /dev/null differ diff --git a/modules/ROOT/images/manage-dbs-default.svg b/modules/ROOT/images/manage-dbs-default.svg new file mode 100644 index 000000000..fa3788270 --- /dev/null +++ b/modules/ROOT/images/manage-dbs-default.svg @@ -0,0 +1,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/modules/ROOT/images/manage-dbs-enterprise.png b/modules/ROOT/images/manage-dbs-enterprise.png deleted file mode 100644 index bb28c1489..000000000 Binary files a/modules/ROOT/images/manage-dbs-enterprise.png and /dev/null differ diff --git a/modules/ROOT/images/manage-dbs-enterprise.svg b/modules/ROOT/images/manage-dbs-enterprise.svg new file mode 100644 index 000000000..56926f92a --- /dev/null +++ b/modules/ROOT/images/manage-dbs-enterprise.svg @@ -0,0 +1,31 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/modules/ROOT/images/remote-alias-overview.svg b/modules/ROOT/images/remote-alias-overview.svg index 6a06a319e..d51cdcda9 100644 --- a/modules/ROOT/images/remote-alias-overview.svg +++ b/modules/ROOT/images/remote-alias-overview.svg @@ -1,43 +1,42 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/modules/ROOT/pages/database-administration/composite-databases/concepts.adoc b/modules/ROOT/pages/database-administration/composite-databases/concepts.adoc index 20806234e..e48095027 100644 --- a/modules/ROOT/pages/database-administration/composite-databases/concepts.adoc +++ b/modules/ROOT/pages/database-administration/composite-databases/concepts.adoc @@ -54,7 +54,7 @@ using a _proxy node_ modeling pattern, where nodes with a specific label must be In one of the graphs, nodes with that specific label contain all the data related to that label, while in the other graph, the same label is associated with a proxy node that only contains the `ID` property. The `ID` property allows you to link data across the graphs in this federation. -image::federation-sharding.png[title="Data federation and sharding", width=450, role=middle] +image::federation-sharding.svg[title="Data federation and sharding", width=450, role=popup] [TIP] ==== diff --git a/modules/ROOT/pages/database-administration/index.adoc b/modules/ROOT/pages/database-administration/index.adoc index e2536c089..bea952374 100644 --- a/modules/ROOT/pages/database-administration/index.adoc +++ b/modules/ROOT/pages/database-administration/index.adoc @@ -45,7 +45,7 @@ For details, see xref:database-administration/standard-databases/configuration-p The following image illustrates an installation of Neo4j containing the three standard databases, named `marketing`, `sales`, and `hr`, and the `system` database. The default database is `sales`: -image::manage-dbs-default.png[title="A multiple database Neo4j installation, with a default database.", role="middle"] +image::manage-dbs-default.svg[title="A multiple database Neo4j installation, with a default database.",role=popup] [NOTE] ==== @@ -78,10 +78,10 @@ Most of the available administrative commands are restricted to users with speci An example of configuring security privileges is described in xref:tutorial/access-control.adoc[Fine-grained access control]. .A default installation, including the `system` database and a single standard database named `neo4j`: -image::manage-dbs-community.png[title="A default Neo4j installation.", role="middle"] +image::manage-dbs-community.svg[title="A default Neo4j installation.",role=popup] .An installation of Neo4j with multiple active databases, named `marketing`, `sales`, and `hr`: -image::manage-dbs-enterprise.png[title="A multiple database Neo4j installation.", role="middle"] +image::manage-dbs-enterprise.svg[title="A multiple database Neo4j installation.",role=popup] == Composite databases diff --git a/modules/ROOT/pages/kubernetes/quickstart-cluster/server-setup.adoc b/modules/ROOT/pages/kubernetes/quickstart-cluster/server-setup.adoc index e55aa2fd3..da01b1484 100644 --- a/modules/ROOT/pages/kubernetes/quickstart-cluster/server-setup.adoc +++ b/modules/ROOT/pages/kubernetes/quickstart-cluster/server-setup.adoc @@ -9,7 +9,7 @@ By separating the charts up, users can create a different topology of Neo4j and The following diagram is a schematic representation of the Helm charts involved and the Kubernetes and Cloud resources they instantiate when installed: .Neo4j cluster setup -image:cluster-on-k8s.png[] +image::cluster-on-k8s.svg[Example of Neo4j cluster setup in Kubernetes,width=700,role=popup] The diagram shows an example of a Neo4j cluster setup with three servers. The Kubernetes setup includes a headless service for accessing the cluster from inside Kubernetes and a load-balancer service for accessing the cluster from outside Kubernetes.