Remove page aliases; fix page headers

Author: eric-schneider

modules/ROOT/pages/astream-custom-roles.adoc

@@ -1,6 +1,4 @@
 = Manage custom roles
-:slug: manage-custom-user-roles
-:page-aliases: docs@astra-streaming::astream-custom-roles.adoc
 :page-tag: astra-streaming,security,secure,pulsar
 
 Within *Settings* > *Users*, you can see the permissions for a specific role by hovering over the number in the *Roles* column of the table. This will show the permissions granted to the role.
@@ -21,7 +19,7 @@ You can also create custom roles using the DevOps API.
 . From *Settings* page, select *Roles*.
 . Select *Add Custom Role*.
 . Enter the name you want to use for your custom role. This name should help you easily identify when you want to assign this role to users.
-. Select the Organization, Keyspace, Table, and API permissions you want to assign to your custom role. 
+. Select the Organization, Keyspace, Table, and API permissions you want to assign to your custom role.
 +
 [NOTE]
 ====

modules/ROOT/pages/astream-faq.adoc

@@ -1,5 +1,4 @@
 = {product_name} FAQs
-:page-aliases: docs@astra-streaming::astream-faq.adoc
 :page-tag: astra-streaming,dev,admin,planner,plan,pulsar
 
 == How do I sign up for the {product_name}?

modules/ROOT/pages/astream-org-permissions.adoc

@@ -1,6 +1,4 @@
 = User permissions
-:slug: user-permissions
-:page-aliases: docs@astra-streaming::astream-org-permissions.adoc
 :page-tag: astra-streaming,security,secure,pulsar
 
 Default and xref:astream-custom-roles.adoc[custom roles] allow admins to manage unique permissions for users based on your organization and database requirements.

modules/ROOT/pages/astream-subscriptions-exclusive.adoc

@@ -1,5 +1,4 @@
 = Exclusive subscriptions in Pulsar
-:page-aliases: docs@astra-streaming::astream-subscriptions-exclusive.adoc
 :page-tag: pulsar-subscriptions,quickstart,admin,dev,pulsar
 
 *Subscriptions* in Pulsar describe which consumers are consuming data from a topic and how they want to consume that data. +
@@ -18,9 +17,9 @@ This example uses the `pulsarConsumer` object in `SimplePulsarConsumer.java` bel
 [source,java]
 ----
 pulsarConsumer = pulsarClient.newConsumer(Schema.JSON(DemoBean.class))
-    .topic("persistent://" 
-            + conf.getTenantName() + "/" 
-            + conf.getNamespace() + "/" 
+    .topic("persistent://"
+            + conf.getTenantName() + "/"
+            + conf.getNamespace() + "/"
             + conf.getTopicName())
     .startMessageIdInclusive()
     .subscriptionInitialPosition(SubscriptionInitialPosition.Earliest)
@@ -32,7 +31,7 @@ pulsarConsumer = pulsarClient.newConsumer(Schema.JSON(DemoBean.class))
 ====
 Pulsar creates an exclusive subscription by default when no `subscriptionType` is declared.
 ====
- 
+
 . Open the `pulsar-subscription-example` repo in the IDE of your choice and run `SimplePulsarConsumer.java` to begin consuming messages. +
 The confirmation message and a cursor appear to indicate the consumer is ready.
 +
@@ -43,7 +42,7 @@ The confirmation message and a cursor appear to indicate the consumer is ready.
 [pulsar-client-io-1-1] INFO org.apache.pulsar.client.impl.ConsumerImpl - [persistent://<tenant_name>/<namespace>/in][SimplePulsarConsumer] Subscribed to topic on <service_url> -- consumer: 0
 ----
 
-. In a new terminal window, run `SimplePulsarProducer.java` to begin producing messages. 
+. In a new terminal window, run `SimplePulsarProducer.java` to begin producing messages.
 +
 [source,bash]
 ----
@@ -52,7 +51,7 @@ The confirmation message and a cursor appear to indicate the consumer is ready.
 [main] INFO com.datastax.pulsar.SimplePulsarProducer - Message 68306175 sent
 ----
 
-. The consumer begins consuming the produced messages. 
+. The consumer begins consuming the produced messages.
 +
 [source,bash]
 ----
@@ -61,7 +60,7 @@ The confirmation message and a cursor appear to indicate the consumer is ready.
 [main] INFO com.datastax.pulsar.SimplePulsarConsumer - Message received: {"show_id":68306175,"cast":"LeBron James, Anthony Davis, Kyrie Irving, Damian Lillard, Klay Thompson...","country":"United States","date_added":"July 16, 2021","description":"NBA superstar LeBron James teams up with Bugs Bunny and the rest of the Looney Tunes for this long-awaited sequel.","director":"Malcolm D. Lee","duration":"120 min","listed_in":"Animation, Adventure, Comedy","rating":"PG","release_year":2021,"title":"Space Jam: A New Legacy","type":"Movie"}
 ----
 
-. Open a new terminal window and try to run `SimplePulsarConsumer.java`. 
+. Open a new terminal window and try to run `SimplePulsarConsumer.java`.
 +
 [source,bash]
 ----

modules/ROOT/pages/astream-subscriptions-failover.adoc

@@ -1,5 +1,4 @@
 = Failover subscriptions in Pulsar
-:page-aliases: docs@astra-streaming::astream-subscriptions-failover.adoc
 :page-tag: pulsar-subscriptions,quickstart,admin,dev,pulsar
 
 *Subscriptions* in Pulsar describe which consumers are consuming data from a topic and how they want to consume that data. +
@@ -14,14 +13,14 @@ include::partial$subscription-prereq.adoc[]
 [#example]
 == Failover subscription example
 
-To try out a Pulsar failover subscription, add `.subscriptionType(SubscriptionType.Failover)` to the `pulsarConsumer` in `SimplePulsarConsumer.java`. 
+To try out a Pulsar failover subscription, add `.subscriptionType(SubscriptionType.Failover)` to the `pulsarConsumer` in `SimplePulsarConsumer.java`.
 
 [source,java]
 ----
 pulsarConsumer = pulsarClient.newConsumer(Schema.JSON(DemoBean.class))
-    .topic("persistent://" 
-        + conf.getTenantName() + "/" 
-        + conf.getNamespace() + "/" 
+    .topic("persistent://"
+        + conf.getTenantName() + "/"
+        + conf.getNamespace() + "/"
         + conf.getTopicName())
     .startMessageIdInclusive()
     .subscriptionInitialPosition(SubscriptionInitialPosition.Earliest)
@@ -41,7 +40,7 @@ The confirmation message and a cursor appear to indicate the consumer is ready.
 [pulsar-client-io-1-1] INFO org.apache.pulsar.client.impl.ConsumerImpl - [persistent://<tenant_name>/<namespace>/in][SimplePulsarConsumer] Subscribed to topic on <service_url> -- consumer: 0
 ----
 
-. In a new terminal window, run `SimplePulsarProducer.java` to begin producing messages. 
+. In a new terminal window, run `SimplePulsarProducer.java` to begin producing messages.
 +
 [source,bash]
 ----
@@ -53,7 +52,7 @@ The confirmation message and a cursor appear to indicate the consumer is ready.
 [main] INFO com.datastax.pulsar.SimplePulsarProducer - Message 42372149 sent
 ----
 
-. The primary consumer begins consuming messages. 
+. The primary consumer begins consuming messages.
 +
 [source,bash]
 ----
@@ -76,7 +75,7 @@ The confirmation message and a cursor appear to indicate the consumer is ready.
 
 === Failover subscription video
 
-Follow along with this video from our *Five Minutes About Pulsar* series to see failover subscriptions in action. 
+Follow along with this video from our *Five Minutes About Pulsar* series to see failover subscriptions in action.
 
 video::ckB87OLs5eM[youtube, list=PL2g2h-wyI4SqeKH16czlcQ5x4Q_z-X7_m, height=445px,width=100%]
 

modules/ROOT/pages/astream-subscriptions-keyshared.adoc

@@ -1,5 +1,4 @@
 = Key_Shared subscriptions in Pulsar
-:page-aliases: docs@astra-streaming::astream-subscriptions-keyshared.adoc
 :page-tag: pulsar-subscriptions,quickstart,admin,dev,pulsar
 
 *Subscriptions* in Pulsar describe which consumers are consuming data from a topic and how they want to consume that data. +
@@ -9,7 +8,7 @@ Pulsar's xref:astream-subscriptions-shared.adoc[shared subscription] model trade
 *Keys* are generated with *hashing*, which converts arbitrary values like "topic-name" or JSON blobs into fixed integer values. These hashed values are then assigned to subscribed consumers in one of two ways:
 
 * *Auto hash* - uses *consistent hashing* to balance range values across available consumers, without requiring manual setup of hash ranges.
-* *Sticky hash* - the client manually assigns consumer range values. All hashes within a configured range go to one consumer. 
+* *Sticky hash* - the client manually assigns consumer range values. All hashes within a configured range go to one consumer.
 
 This document explains how to use Pulsar's Key_Shared subscription model to manage your topic consumption.
 
@@ -19,28 +18,28 @@ include::partial$subscription-prereq.adoc[]
 == Key_Shared subscription example
 
 To try out a Pulsar Key_Shared subscription, add `.subscriptionType(SubscriptionType.Key_Shared)` to the `pulsarConsumer` in `SimplePulsarConsumer.java`. +
-You must also tell Pulsar what `keySharedPolicy` this subscription will use. The example below uses the auto-hashing `keySharedPolicy`. 
+You must also tell Pulsar what `keySharedPolicy` this subscription will use. The example below uses the auto-hashing `keySharedPolicy`.
 
 [source,java]
 ----
 pulsarConsumer = pulsarClient.newConsumer(Schema.JSON(DemoBean.class))
-    .topic("persistent://" 
-        + conf.getTenantName() + "/" 
-        + conf.getNamespace() + "/" 
+    .topic("persistent://"
+        + conf.getTenantName() + "/"
+        + conf.getNamespace() + "/"
         + conf.getTopicName())
     .startMessageIdInclusive()
     .subscriptionInitialPosition(SubscriptionInitialPosition.Earliest)
     .subscriptionName("SimplePulsarConsumer")
     .subscriptionType(SubscriptionType.Key_Shared)
     .keySharedPolicy(KeySharedPolicy.autoSplitHashRange())
-    .subscribe();  
+    .subscribe();
 ----
 
-Running multiple consumers with auto-hashing balances the messaging load across all available consumers. 
+Running multiple consumers with auto-hashing balances the messaging load across all available consumers.
 
 === Manually set stickyHashRange
 
-You can manually set a hash range with `KeySharedPolicy.stickyHashRange()`. 
+You can manually set a hash range with `KeySharedPolicy.stickyHashRange()`.
 
 To test out sticky hashed Key_Shared subscriptions, you need to first import some additional classes.
 
@@ -67,9 +66,9 @@ import org.apache.pulsar.client.api.HashingScheme;
 ----
 pulsarProducer = pulsarClient
     .newProducer(Schema.JSON(DemoBean.class))
-    .topic("persistent://" 
-                + conf.getTenantName() + "/" 
-                + conf.getNamespace() + "/" 
+    .topic("persistent://"
+                + conf.getTenantName() + "/"
+                + conf.getNamespace() + "/"
                 + conf.getTopicName())
     .batcherBuilder(BatcherBuilder.KEY_BASED)
     .hashingScheme(HashingScheme.JavaStringHash)
@@ -94,7 +93,7 @@ The confirmation message and a cursor appear to indicate the consumer is ready.
 [pulsar-client-io-1-1] INFO org.apache.pulsar.client.impl.ConsumerImpl - [persistent://<tenant_name>/<namespace>/in][SimplePulsarConsumer] Subscribed to topic on <service_url> -- consumer: 0
 ----
 
-. In a new terminal window, run `SimplePulsarProducer.java` to begin producing messages. 
+. In a new terminal window, run `SimplePulsarProducer.java` to begin producing messages.
 +
 [source,bash]
 ----
@@ -104,15 +103,15 @@ The confirmation message and a cursor appear to indicate the consumer is ready.
 [main] INFO com.datastax.pulsar.SimplePulsarProducer - Message 57467766 sent
 ----
 
-. The consumer begins receiving messages. 
+. The consumer begins receiving messages.
 +
 [source,bash]
 ----
 [main] INFO com.datastax.pulsar.SimplePulsarConsumer - Message received: {"show_id":55794190,"cast":"LeBron James, Anthony Davis, Kyrie Irving, Damian Lillard, Klay Thompson...","country":"United States","date_added":"July 16, 2021","description":"NBA superstar LeBron James teams up with Bugs Bunny and the rest of the Looney Tunes for this long-awaited sequel.","director":"Malcolm D. Lee","duration":"120 min","listed_in":"Animation, Adventure, Comedy","rating":"PG","release_year":2021,"title":"Space Jam: A New Legacy","type":"Movie"}
 [main] INFO com.datastax.pulsar.SimplePulsarConsumer - Message received: {"show_id":41791865,"cast":"LeBron James, Anthony Davis, Kyrie Irving, Damian Lillard, Klay Thompson...","country":"United States","date_added":"July 16, 2021","description":"NBA superstar LeBron James teams up with Bugs Bunny and the rest of the Looney Tunes for this long-awaited sequel.","director":"Malcolm D. Lee","duration":"120 min","listed_in":"Animation, Adventure, Comedy","rating":"PG","release_year":2021,"title":"Space Jam: A New Legacy","type":"Movie"}
 ----
 
-. Open a new terminal window and try to run `SimplePulsarConsumer.java`. 
+. Open a new terminal window and try to run `SimplePulsarConsumer.java`.
 +
 [source,bash]
 ----
@@ -136,7 +135,7 @@ video::_49wlA53L_8[youtube, list=PL2g2h-wyI4SqeKH16czlcQ5x4Q_z-X7_m, height=445p
 
 == What's next?
 
-For more on subscriptions, see: 
+For more on subscriptions, see:
 
 * xref:astream-subscriptions.adoc[Subscriptions in Pulsar]
 * xref:astream-subscriptions-exclusive.adoc[Exclusive subscriptions]

modules/ROOT/pages/astream-subscriptions-shared.adoc

@@ -1,11 +1,10 @@
 = Shared subscriptions in Pulsar
-:page-aliases: docs@astra-streaming::astream-subscriptions-shared.adoc
 :page-tag: pulsar-subscriptions,quickstart,admin,dev,pulsar
 
 *Subscriptions* in Pulsar describe which consumers are consuming data from a topic and how they want to consume that data. +
 
 A *shared* subscription allows *multiple consumers* to consume messages from a *single topic* in round-robin fashion. +
-More consumers in a shared subscription can increase your Pulsar deployment's rate of message consumption, but at the cost of losing message ordering guarantees and acknowledgement schemes. 
+More consumers in a shared subscription can increase your Pulsar deployment's rate of message consumption, but at the cost of losing message ordering guarantees and acknowledgement schemes.
 
 This document explains how to use Pulsar's shared subscription model to manage your topic consumption.
 
@@ -14,14 +13,14 @@ include::partial$subscription-prereq.adoc[]
 [#example]
 == Shared subscription example
 
-To try out a Pulsar shared subscription, add `.subscriptionType(SubscriptionType.Shared)` to the `pulsarConsumer` in `SimplePulsarConsumer.java`. 
+To try out a Pulsar shared subscription, add `.subscriptionType(SubscriptionType.Shared)` to the `pulsarConsumer` in `SimplePulsarConsumer.java`.
 
 [source,java]
 ----
 pulsarConsumer = pulsarClient.newConsumer(Schema.JSON(DemoBean.class))
-    .topic("persistent://" 
-        + conf.getTenantName() + "/" 
-        + conf.getNamespace() + "/" 
+    .topic("persistent://"
+        + conf.getTenantName() + "/"
+        + conf.getNamespace() + "/"
         + conf.getTopicName())
     .startMessageIdInclusive()
     .subscriptionInitialPosition(SubscriptionInitialPosition.Earliest)
@@ -40,7 +39,7 @@ The confirmation message and a cursor appear to indicate the consumer is ready.
 [pulsar-client-io-1-1] INFO org.apache.pulsar.client.impl.ConsumerImpl - [persistent://<tenant_name>/<namespace>/in][SimplePulsarConsumer] Subscribed to topic on <service_url> -- consumer: 0
 ----
 
-. In a new terminal window, run `SimplePulsarProducer.java` to begin producing messages. 
+. In a new terminal window, run `SimplePulsarProducer.java` to begin producing messages.
 +
 [source,bash]
 ----
@@ -51,7 +50,7 @@ The confirmation message and a cursor appear to indicate the consumer is ready.
 [main] INFO com.datastax.pulsar.SimplePulsarProducer - Message 51277375 sent
 ----
 
-. The consumer begins receiving messages. 
+. The consumer begins receiving messages.
 +
 [source,bash]
 ----
@@ -75,7 +74,7 @@ Since this test uses shared subscriptions, you can attach multiple consumers to
 
 == Shared subscription video
 
-Follow along with this video from our *Five Minutes About Pulsar* series to see shared subscriptions in action. 
+Follow along with this video from our *Five Minutes About Pulsar* series to see shared subscriptions in action.
 
 video::mmukXqGsauA[youtube, list=PL2g2h-wyI4SqeKH16czlcQ5x4Q_z-X7_m, height=445px,width=100%]
 

modules/ROOT/pages/astream-subscriptions.adoc

@@ -1,15 +1,14 @@
 = Subscriptions in Pulsar
-:page-aliases: docs@astra-streaming::astream-subscriptions.adoc
 :page-tag: pulsar-subscriptions,quickstart,admin,dev,pulsar
 
 *Subscriptions* in Pulsar describe which consumers are consuming data from a topic and how they want to consume that data. +
 
-Subscriptions are managed in the broker as a collection of metadata about a topic and its subscribed consumers. This metadata includes: 
+Subscriptions are managed in the broker as a collection of metadata about a topic and its subscribed consumers. This metadata includes:
 
 * Topic name - which topic the consumer wants data from
 * Subscription name - a string representing a qualified name for the subscription
 * Subscription type - which type of subscription is being used
-* Subscription cursor - a representation of the consumer's current place in the subscribed topic log 
+* Subscription cursor - a representation of the consumer's current place in the subscribed topic log
 
 For example, the Pulsar consumer below has a *shared* subscription starting at the *earliest* cursor position in `my-subscription` to `my-topic`:
 
@@ -30,7 +29,7 @@ Read on to use Pulsar's four types of subscriptions to manage your topic consump
 * xref:astream-subscriptions-failover.adoc[Failover subscriptions]
 * xref:astream-subscriptions-keyshared.adoc[Key_shared subscriptions]
 
-== What's next? 
+== What's next?
 
 * Follow our xref:getting-started:index.adoc[simple guide] to get started with Astra now.
 * For using Kafka with {product_name}, see xref:developing:astream-kafka.adoc[Starlight for Kafka].

modules/ROOT/pages/index.adoc

@@ -1,8 +1,6 @@
 = What is DataStax {product_name}?
-:slug: what-is-datastax-astra-streaming
-:page-aliases: docs@astra-streaming::index.adoc
-:page-tag: astra-streaming,planner,admin,dev,pulsar
 :navtitle: Astra Streaming
+:page-tag: astra-streaming,planner,admin,dev,pulsar
 
 {product_name} is a cloud native data streaming and event stream processing
 service tightly integrated into the {astra_ui} and powered by Apache Pulsar™.

modules/apis/pages/index.adoc

@@ -1,10 +1,6 @@
 = API References
-:slug: astream-api
 :description: Astra provides APIs to manage both DB and Streaming instances
-:keywords: datastax astra
-:meta-description: Astra provides APIs to manage both DB and Streaming instances
 :page-tag: astra-streaming,dev,develop,pulsar
-:page-aliases: docs@astra-streaming::api.adoc, astra-streaming-docs::api.adoc, astra-streaming-docs::astream-use-devops.adoc
 
 Management of Pulsar tenants and its resources are seperated into 2 APIs. The DevOps API is used to manage higher level objects associated with your account. The Pulsar Admin API is used to manage specific resources such as namespaces, topics, and subscriptions within a specific tenant.