Remove EE + ArangoGraph tags

arangodb · Simran-B · Mar 19, 2025 · Mar 19, 2025 · Mar 19, 2025 · Mar 19, 2025
commit 1382926194163e99affacbf82b8cd4d124b06725
diff --git a/site/content/3.12/aql/functions/arangosearch.md b/site/content/3.12/aql/functions/arangosearch.md
@@ -1271,8 +1271,6 @@ FOR doc IN viewName
 
 ## Search Highlighting Functions
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 ### OFFSET_INFO()
 
 `OFFSET_INFO(doc, paths) → offsetInfo`

diff --git a/site/content/3.12/aql/graphs/traversals.md b/site/content/3.12/aql/graphs/traversals.md
@@ -189,8 +189,6 @@ If omitted or an empty array is specified, then there are no restrictions.
 
 #### `parallelism`
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 Parallelize traversal execution (number).
 
 If omitted or set to a value of `1`, the traversal execution is not parallelized.
@@ -206,8 +204,6 @@ execution.
 
 #### `maxProjections`
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 Specifies the number of document attributes per `FOR` loop to be used as
 projections (number). The default value is `5`.
 

diff --git a/site/content/3.12/aql/how-to-invoke-aql/with-arangosh.md b/site/content/3.12/aql/how-to-invoke-aql/with-arangosh.md
@@ -496,8 +496,6 @@ the entire query result in RAM, use a streaming query (see the
 
 #### `allowDirtyReads`
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 <small>Introduced in: v3.10.0</small>
 
 If you set this option to `true` and execute the query against a cluster
@@ -507,8 +505,6 @@ for details.
 
 #### `skipInaccessibleCollections`
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 Let AQL queries (especially graph traversals) treat collection to which a
 user has **no access** rights for as if these collections are empty.
 Instead of returning a *forbidden access* error, your queries execute normally.
@@ -518,8 +514,6 @@ accessible results by changing the access rights of users on collections.
 
 #### `satelliteSyncWait`
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 Configure how long a DB-Server has time to bring the SatelliteCollections
 involved in the query into sync. The default value is `60.0` seconds.
 When the maximal time is reached, the query is stopped.

diff --git a/site/content/3.12/components/tools/arangodump/examples.md b/site/content/3.12/components/tools/arangodump/examples.md
@@ -163,8 +163,6 @@ INFO [66c0e] {dump} Processed 2 collection(s) from 1 database(s) in 0.132990 s t
 
 ## Encryption
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 You can encrypt dumps using an encryption keyfile, which must contain exactly 32
 bytes of data (required by the AES block cipher).
 

diff --git a/site/content/3.12/components/tools/arangodump/maskings.md b/site/content/3.12/components/tools/arangodump/maskings.md
@@ -470,8 +470,6 @@ processed by a single masking function, ignoring any other rules below it.
 
 ## Masking Functions
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 - [Xify Front](#xify-front)
 - [Zip](#zip)
 - [Datetime](#datetime)

diff --git a/site/content/3.12/data-science/arangographml/deploy.md b/site/content/3.12/data-science/arangographml/deploy.md
@@ -54,8 +54,6 @@ To summarize, all you need to do is:
 
 ### Self-managed ArangoGraphML
 
-{{< tag "ArangoDB Enterprise Edition" >}}
-
 The self-managed solution enables you to deploy and manage ArangoML within your
 Kubernetes cluster using the [ArangoDB Kubernetes Operator](https://github.com/arangodb/kube-arangodb).
 

diff --git a/site/content/3.12/deploy/_index.md b/site/content/3.12/deploy/_index.md
@@ -37,8 +37,6 @@ You can deploy systems that dynamically scale up and down according to demand.
 
 ### OneShard
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 [OneShard deployments](oneshard.md) are cluster deployments but with the data of
 each database restricted to a single shard. This allows queries to run locally
 on a single DB-Server node for better performance and with transactional

diff --git a/site/content/3.12/deploy/oneshard.md b/site/content/3.12/deploy/oneshard.md
@@ -6,8 +6,6 @@ description: >-
   The OneShard feature offers a practicable solution that enables significantly
   improved performance and transactional guarantees for cluster deployments
 ---
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 The OneShard option for ArangoDB clusters restricts all collections of a
 database to a single shard so that every collection has `numberOfShards` set to `1`,
 and all leader shards are placed on one DB-Server node. This way, whole queries

diff --git a/site/content/3.12/develop/http-api/documents.md b/site/content/3.12/develop/http-api/documents.md
@@ -3072,8 +3072,6 @@ db._drop(cn);
 
 ## Read from followers
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 <small>Introduced in: v3.10.0</small>
 
 In an ArangoDB cluster, all reads and writes are performed via

diff --git a/site/content/3.12/develop/satellitecollections.md b/site/content/3.12/develop/satellitecollections.md
@@ -5,8 +5,6 @@ weight: 250
 description: >-
   Collections synchronously replicated to all servers, available in the Enterprise Edition
 ---
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 When doing joins in an ArangoDB cluster data has to be exchanged between different servers.
 
 Joins are executed on a Coordinator. It prepares an execution plan

diff --git a/site/content/3.12/develop/smartjoins.md b/site/content/3.12/develop/smartjoins.md
@@ -6,8 +6,6 @@ description: >-
   SmartJoins allow to execute co-located join operations among identically
   sharded collections
 ---
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 ## Cluster joins without being smart
 
 When doing joins in an ArangoDB cluster, data has to be exchanged between different servers.

diff --git a/site/content/3.12/graphs/enterprisegraphs/_index.md b/site/content/3.12/graphs/enterprisegraphs/_index.md
@@ -6,8 +6,6 @@ description: >-
   EnterpriseGraphs enable you to manage graphs at scale with automated sharding
   key selection
 ---
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 This chapter describes the `enterprise-graph` module, a specialized version of
 [SmartGraphs](../smartgraphs/_index.md).
 It will give a vast performance benefit for all graphs sharded

diff --git a/site/content/3.12/graphs/satellitegraphs/_index.md b/site/content/3.12/graphs/satellitegraphs/_index.md
@@ -5,8 +5,6 @@ weight: 90
 description: >-
   Graphs synchronously replicated to all servers, available in the Enterprise Edition
 ---
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 ## What is a SatelliteGraph?
 
 _SatelliteGraphs_ are a specialized _named graph_ type available for cluster

diff --git a/site/content/3.12/graphs/smartgraphs/_index.md b/site/content/3.12/graphs/smartgraphs/_index.md
@@ -5,8 +5,6 @@ weight: 95
 description: >-
   SmartGraphs enable you to manage graphs at scale using value-based sharding
 ---
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 SmartGraphs are specifically targeted at graphs that need scalability and
 high performance. The way SmartGraphs use the ArangoDB cluster sharding makes it
 extremely useful for distributing data across multiple servers with minimal

diff --git a/site/content/3.12/graphs/smartgraphs/testing-graphs-on-single-server.md b/site/content/3.12/graphs/smartgraphs/testing-graphs-on-single-server.md
@@ -6,8 +6,6 @@ description: >-
   Simulate SmartGraphs and SatelliteGraphs on a single server to make it easier
   to port them to an ArangoDB cluster later
 ---
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 ## General idea
 
 You can create SmartGraphs and SatelliteGraphs in a single server instance and

diff --git a/site/content/3.12/index-and-search/analyzers.md b/site/content/3.12/index-and-search/analyzers.md
@@ -1196,8 +1196,6 @@ db._query(`RETURN TOKENS("The quick brown Foxx", "wildcard_3")`).toArray();
 
 ### `minhash`
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 <small>Introduced in: v3.10.0</small>
 
 An Analyzer that computes so called MinHash signatures using a
@@ -1239,8 +1237,6 @@ db._query(`
 
 ### `classification`
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 <small>Introduced in: v3.10.0</small>
 
 {{< warning >}}
@@ -1299,8 +1295,6 @@ db._query(`LET str = "Which baking dish is best to bake a banana bread ?"
 
 ### `nearest_neighbors`
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 <small>Introduced in: v3.10.0</small>
 
 {{< warning >}}
@@ -1479,8 +1473,6 @@ db._query(`LET point = GEO_POINT(6.93, 50.94)
 
 ### `geo_s2`
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 <small>Introduced in: v3.10.5</small>
 
 An Analyzer capable of breaking up a GeoJSON object or coordinate array in

diff --git a/site/content/3.12/index-and-search/arangosearch/nested-search.md b/site/content/3.12/index-and-search/arangosearch/nested-search.md
@@ -7,8 +7,6 @@ description: >-
   each, and define how often these conditions should be fulfilled for the entire
   array
 ---
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 By default, `arangosearch` Views index arrays as if the parent attribute had
 multiple values at once. This is also supported for `search-alias` Views by enabling
 the `searchField` option. With `trackListPositions` set to `true`, every array

diff --git a/site/content/3.12/index-and-search/arangosearch/performance.md b/site/content/3.12/index-and-search/arangosearch/performance.md
@@ -624,8 +624,6 @@ Also see [Faceted Search with ArangoSearch](faceted-search.md).
 
 ## Field normalization value caching and caching of Geo Analyzer auxiliary data
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 <small>Introduced in: v3.9.5, v3.10.2</small>
 
 Normalization values are computed for fields which are processed with Analyzers

diff --git a/site/content/3.12/index-and-search/arangosearch/search-highlighting.md b/site/content/3.12/index-and-search/arangosearch/search-highlighting.md
@@ -6,8 +6,6 @@ description: >-
   You can retrieve the positions of matches within strings when querying
   Views with ArangoSearch, to highlight what was found in search results
 ---
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 ArangoSearch lets you search for terms and phrases in full-text, and more.
 It only returns matching documents, however. With search highlighting, you can
 get the exact locations of the matches.

diff --git a/site/content/3.12/operations/backup-and-restore.md b/site/content/3.12/operations/backup-and-restore.md
@@ -62,8 +62,6 @@ Logical backups can be created and restored with the tools
 
 ## Hot Backups
 
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 Hot backup and restore associated operations can be performed with the
 [_arangobackup_](../components/tools/arangobackup/_index.md) client tool and the
 [Hot Backup HTTP API](../develop/http-api/hot-backups.md).

diff --git a/site/content/3.12/operations/security/audit-logging.md b/site/content/3.12/operations/security/audit-logging.md
@@ -9,8 +9,6 @@ description: >-
 pageToc:
   maxHeadlineLevel: 3
 ---
-{{< tag "ArangoDB Enterprise Edition" >}}
-
 {{< tip >}}
 A similar feature is also available in the
 [ArangoGraph Insights Platform](../../arangograph/security-and-access-control/_index.md#using-an-audit-log).

diff --git a/site/content/3.12/operations/security/encryption-at-rest.md b/site/content/3.12/operations/security/encryption-at-rest.md
@@ -6,8 +6,6 @@ description: >-
   You can secure the physical storage media of an ArangoDB deployment by letting
   it encrypt the database directories
 ---
-{{< tag "ArangoDB Enterprise Edition" "ArangoGraph" >}}
-
 When you store sensitive data in your ArangoDB database, you want to protect
 that data under all circumstances. At runtime you will protect it with SSL
 transport encryption and strong authentication, but when the data is already