Phase 1: Adding documentation metadata tags (#6274)

* Add metadata tags for documentation

* Add classification for about 2/3rds of docs (func + eventing)

* Add classification for remainder of docs (serving+install)

docs/about-analytics-cookies.md

@@ -2,6 +2,9 @@
 title: "Learn about Google Analytics cookies"
 linkTitle: "Learn about cookies"
 type: "docs"
+audience: developer
+components: []
+function: community
 ---
 
 By using this website, you are confirming that you accept our use of cookies for

docs/about/case-studies/README.md

@@ -1,6 +1,11 @@
 ---
 hide:
   - toc
+audience: buyer
+components:
+  - eventing
+  - serving
+function: marketing
 ---
 
 # Knative Case Studies

docs/about/case-studies/deepc.md

@@ -1,6 +1,10 @@
 ---
 hide:
   - toc
+audience: buyer
+components:
+  - eventing
+function: marketing
 ---
 <h1 style="color:#0071c7;font-size: 3em;">deepc Case Study</h1>
 <table style="border: 0;">

docs/about/case-studies/ibm.md

@@ -1,6 +1,10 @@
 ---
 hide:
   - toc
+audience: buyer
+components:
+  - eventing
+function: marketing
 ---
 <h1 style="color:#0071c7;font-size: 3em;">IBM Case Study</h1>
 <table style="border: 0;">

docs/about/case-studies/outfit7.md

@@ -1,6 +1,10 @@
 ---
 hide:
   - toc
+audience: buyer
+components:
+  - serving
+function: marketing
 ---
 <h1 style="color:#0071c7;font-size: 3em;">Outfit7 Case Study</h1>
 <table style="border: 0;">

docs/about/case-studies/pnc.md

@@ -1,6 +1,11 @@
 ---
 hide:
   - toc
+audience: buyer
+components:
+  - eventing
+  - serving
+function: marketing
 ---
 <h1 style="color:#0071c7;font-size: 3em;">PNC Bank Case Study</h1>
 <table style="border: 0;">

docs/about/case-studies/puppet.md

@@ -1,6 +1,10 @@
 ---
 hide:
   - toc
+audience: buyer
+components:
+  - serving
+function: marketing
 ---
 <h1 style="color:#0071c7;font-size: 3em;">Puppet Case Study</h1>
 <table style="border: 0;">

docs/about/case-studies/sva.md

@@ -1,6 +1,10 @@
 ---
 hide:
   - toc
+audience: buyer
+components:
+  - eventing
+function: marketing
 ---
 <h1 style="color:#0071c7;font-size: 3em;">SVA System Vertrieb Alexander GmbH Case Study</h1>
 <table style="border: 0;">

docs/about/testimonials.md

@@ -1,3 +1,11 @@
+---
+audience: buyer
+components:
+  - eventing
+  - serving
+function: marketing
+---
+
 <div class="testimonials">
   <h1>Testimonials</h1>
   <h3><b>Enterprise-grade Serverless on your own terms</b></h3>

docs/bookstore/create-slack-workspace/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: tutorial
+---
+
 # Creating a Slack Workspace
 
 ![Image](images/image5.png)

docs/bookstore/disclaimer/README.md

@@ -1,3 +1,9 @@
+---
+audience: developer
+components: []
+function: tutorial
+---
+
 # **Disclaimer**
 
 ![image](images/image2.png)

docs/bookstore/extra-challenge/README.md

@@ -1,3 +1,12 @@
+---
+audience: developer
+components:
+  - eventing
+  - serving
+  - functions
+function: tutorial
+---
+
 # **Extra Challenges**
 
 ![image](images/image5.png)

docs/bookstore/page-0.5/environment-setup.md

@@ -1,3 +1,11 @@
+---
+audience: developer
+components:
+  - eventing
+  - serving
+function: tutorial
+---
+
 # Environment Setup
 
 ![Image](images/image20.png)

docs/bookstore/page-0/welcome-knative-bookstore-tutorial.md

@@ -1,3 +1,12 @@
+---
+audience: developer
+components:
+  - eventing
+  - functions
+  - serving
+function: tutorial
+---
+
 # Welcome: Knative Bookstore Tutorial
 
 ![Welcome Image](images/1.png)

docs/bookstore/page-1/send-review-comment-to-broker.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: tutorial
+---
+
 # Send Review Comment to Broker
 
 ![Image](images/image25.png)

docs/bookstore/page-2/sentiment-analysis-service-for-bookstore-reviews.md

@@ -1,3 +1,11 @@
+---
+audience: developer
+components:
+  - functions
+  - serving
+function: tutorial
+---
+
 # Sentiment Analysis Service for Bookstore Reviews
 
 ![Image1](images/image1.png)

docs/bookstore/page-3/create-bad-word-filter-service.md

@@ -1,3 +1,11 @@
+---
+audience: developer
+components:
+  - functions
+  - serving
+function: tutorial
+---
+
 # Create Bad Word Filter Service
 
 ![Image 4](images/image4.png)

docs/bookstore/page-3/solution-create-bad-word-filter-service.md

@@ -1,3 +1,11 @@
+---
+audience: developer
+components:
+  - functions
+  - serving
+function: tutorial
+---
+
 # Solution - Create Bad Word Filter Service
 
 ![image](images/image4.png)

docs/bookstore/page-4/create-sequence-to-streamline-ML-workflows.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: tutorial
+---
+
 # **Create Knative Sequence to Streamline ML Workflows**
 
 ![image](images/image8.png)

docs/bookstore/page-5/deploy-database-service.md

@@ -1,3 +1,9 @@
+---
+audience: developer
+components: []
+function: tutorial
+---
+
 # **Deploy the Database Service**
 
 ![image1](images/image1.png)

docs/bookstore/page-6/advanced-event-filtering.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: tutorial
+---
+
 # **Advanced Event Filtering**
 
 ![Image](images/image4.png)

docs/bookstore/page-7/slack-sink-learning-knative-eventing-and-apache-camel-K-integration.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: tutorial
+---
+
 # **Slack sink - Learning Knative Eventing and the Apache Camel K integration**
 
 ![image](images/image2.png)

docs/client/README.md

@@ -1,3 +1,12 @@
+---
+audience: developer
+components:
+  - eventing
+  - functions
+  - serving
+function: explanation
+---
+
 # CLI tools
 
 The following CLI tools are supported for use with Knative.

docs/client/configure-kn.md

@@ -1,3 +1,12 @@
+---
+audience: developer
+components:
+  - eventing
+  - functions
+  - serving
+function: reference
+---
+
 # Customizing kn
 
 You can customize your `kn` CLI setup by creating a `config.yaml` configuration file. You can provide this configuration by using the `--config` flag, otherwise the configuration is picked up from a default location. The default configuration location conforms to the [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html), and is different for Unix systems and Windows systems.

docs/client/install-kn.md

@@ -1,3 +1,12 @@
+---
+audience: developer
+components:
+  - eventing
+  - functions
+  - serving
+function: how-to
+---
+
 # Installing the Knative CLI
 
 This guide provides details about how you can install the Knative `kn` CLI.

docs/client/kn-plugins.md

@@ -1,3 +1,12 @@
+---
+audience: developer
+components:
+  - eventing
+  - functions
+  - serving
+function: reference
+---
+
 # kn plugins
 
 The `kn` CLI supports the use of plugins. Plugins enable you to extend the functionality of your `kn` installation by adding custom commands and other shared commands that are not part of the core distribution of `kn`.

docs/community/README.md

@@ -1,3 +1,12 @@
+---
+audience: contributor
+components:
+  - eventing
+  - functions
+  - serving
+function: community
+---
+
 # How to Get Involved
 
 <!-- TODO: what is community, what are the touchpoints -->

docs/community/contributing.md

@@ -1,3 +1,12 @@
+---
+audience: contributor
+components:
+  - eventing
+  - functions
+  - serving
+function: community
+---
+
 # Contribute to Knative
 
 This is the starting point for becoming a contributor - improving code, improving docs, giving talks, etc.

docs/community/governance.md

@@ -1,3 +1,9 @@
+---
+audience: contributor
+components: []
+function: community
+---
+
 # Community Rules and Practices
 
 This page provides links to documents for common Knative community practices and

docs/concepts/README.md

@@ -7,7 +7,7 @@ components:
 function: explanation
 ---
 
-# Knative Technical Overview
+# Concepts
 
 This comprehensive overview explains what Knative is, what problems it solves, and how its components work together. Whether you're evaluating Knative for your use case or need background information to understand the rest of the documentation, this section provides the conceptual foundation you need.
 

docs/concepts/duck-typing.md

@@ -1,3 +1,11 @@
+---
+audience: developer
+components:
+  - eventing
+  - serving
+function: explanation
+---
+
 # Duck typing
 
 Knative enables [loose coupling](https://en.wikipedia.org/wiki/Loose_coupling) of its components by using [duck typing](https://en.wikipedia.org/wiki/Duck_typing).

docs/concepts/eventing-resources/brokers.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: explanation
+---
+
 # Brokers
 
 --8<-- "about-brokers.md"

docs/concepts/serving-resources/revisions.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - serving
+function: explanation
+---
+
 # Revisions
 
 --8<-- "about-revisions.md"

docs/eventing/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: explanation
+---
+
 # Knative Eventing - The Event-driven application platform for Kubernetes
 
 --8<-- "about-eventing.md"

docs/eventing/brokers/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: explanation
+---
+
 # About Brokers
 
 --8<-- "about-brokers.md"

docs/eventing/brokers/broker-developer-config-options.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: reference
+---
+
 # Developer configuration options
 
 ## Broker configuration 

docs/eventing/brokers/broker-types/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: reference
+---
+
 # Available Broker types
 
 The following broker types are available for use with Knative Eventing.

docs/eventing/brokers/broker-types/channel-based-broker/README.md

@@ -1,3 +1,11 @@
+---
+audience: developer
+# And audience: administrator for install
+components:
+  - eventing
+function: how-to
+---
+
 # Channel based Broker
 
 The Channel based Broker (`MTChannelBasedBroker`) uses [Channels](../../../channels) for event routing. It is shipped by default with Knative Eventing.

docs/eventing/brokers/broker-types/kafka-broker/README.md

@@ -1,3 +1,11 @@
+---
+audience: developer
+# And audience: administrator for install
+components:
+  - eventing
+function: how-to
+---
+
 # Knative Broker for Apache Kafka
 
 The Knative Broker for Apache Kafka is an implementation of the Knative Broker API natively targeting Apache Kafka to reduce network hops and offering a better integration with Apache Kafka for the Broker and Trigger API model.

docs/eventing/brokers/broker-types/kafka-broker/configuring-kafka-features.md

@@ -1,3 +1,10 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 # Configuring Kafka Features
 
 There are many different configuration options for how Knative Eventing and the Knaitve Broker for Apache Kafka interact with the Apache Kafka clusters.

docs/eventing/brokers/broker-types/rabbitmq-broker/README.md

@@ -1,3 +1,11 @@
+---
+audience: developer
+# And audience: administrator for install
+components:
+  - eventing
+function: explanation
+---
+
 # Creating a RabbitMQ Broker
 
 This topic describes how to create a RabbitMQ Broker.

docs/eventing/brokers/create-broker.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # Creating a Broker
 
 Once you have installed Knative Eventing and a Broker implementation, you can create an instance of a Broker.

docs/eventing/channels/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: explanation
+---
+
 # Channels
 
 Channels are Kubernetes [custom resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) that define a single event forwarding and persistence layer.

docs/eventing/channels/channel-types-defaults.md

@@ -1,3 +1,10 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 # Channel types and defaults
 
 Knative uses two types of Channels:

docs/eventing/channels/channels-crds.md

@@ -1,3 +1,9 @@
+---
+audience: developer
+components:
+  - eventing
+function: reference
+---
 <!--
 This is a generated file and should not be changed manually. All changes should follow the
 procedure:

docs/eventing/channels/create-default-channel.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # Creating a Channel using cluster or namespace defaults
 
 Developers can create Channels of any supported implementation type by creating an instance of a

docs/eventing/channels/generator/ReadmeTemplate.gomd

@@ -1,3 +1,9 @@
+---
+audience: developer
+components:
+  - eventing
+function: reference
+---
 {{ "" }}
 
 {{- /* This will be interpreted given a yamlChannels object. */ -}}

docs/eventing/channels/subscriptions.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # Subscriptions
 
 After you have created a Channel and a Sink, you can create a Subscription to enable event delivery.

docs/eventing/configuration/broker-configuration.md

@@ -1,3 +1,10 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 # Configure Broker defaults
 
 If you have cluster administrator permissions for your Knative installation, you can modify ConfigMaps to change the global default configuration options for Brokers on the cluster.

docs/eventing/configuration/channel-configuration.md

@@ -1,3 +1,10 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 # Configure Channel defaults
 
 Knative Eventing provides a `default-ch-webhook` ConfigMap that contains the configuration settings that govern default Channel creation.

docs/eventing/configuration/kafka-channel-configuration.md

@@ -1,3 +1,10 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 # Configure Channels for Apache Kafka
 
 !!! note

docs/eventing/configuration/keda-configuration.md

@@ -1,3 +1,10 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 # Configure KEDA Autoscaling of Knative Kafka Resources
 
 All of the Knative Kafka components which dispatch events (source, channel broker) support scaling the dispatcher data plane with KEDA.

docs/eventing/configuration/sources-configuration.md

@@ -1,3 +1,10 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 # Configure event source defaults
 
 This topic describes how to configure defaults for Knative event sources. You can configure event sources depending on how they generate events.

docs/eventing/configuration/sugar-configuration.md

@@ -1,3 +1,10 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 # Configure Sugar Controller
 
 This topic describes how to configure the Sugar Controller. You can configure the Sugar controller to create a Broker when a Namespace or Trigger is created with configured labels. See [Knative Eventing Sugar Controller](../sugar/README.md) for an example.

docs/eventing/custom-event-source/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: reference
+---
+
 # Custom event sources
 
 If you need to ingress events from an event producer that is not included in Knative, or from a producer that emits events which are not in the CloudEvent format that is used by Knative, you can do this by using one of the following methods:

docs/eventing/custom-event-source/containersource/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # Create a ContainerSource
 
 ![API version v1](https://img.shields.io/badge/API_Version-v1-green?style=flat-square)

docs/eventing/custom-event-source/containersource/reference.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: reference
+---
+
 # ContainerSource reference
 
 ![API version v1](https://img.shields.io/badge/API_Version-v1-green?style=flat-square)

docs/eventing/custom-event-source/custom-event-source/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # Create a custom event source
 
 If you want to create a custom event source for a specific event producer type, you must create the components that enable forwarding events from that producer type to a Knative sink.

docs/eventing/custom-event-source/custom-event-source/controller.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: tutorial
+---
+
 # Create a controller
 
 You can use the sample repository [`update-codegen.sh`](https://github.com/knative-extensions/sample-source/blob/main/hack/update-codegen.sh) script to generate and inject the required components (the `clientset`, `cache`, `informers`, and `listers`) into your custom controller.

docs/eventing/custom-event-source/custom-event-source/publish-event-source.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: tutorial
+---
+
 # Publish an event source to your cluster
 
 1. Start a minikube cluster:

docs/eventing/custom-event-source/custom-event-source/receive-adapter.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: tutorial
+---
+
 # Create a receive adapter
 
 As part of the source reconciliation process, you must create and deploy the underlying receive adapter.

docs/eventing/custom-event-source/custom-event-source/sample-repo.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: tutorial
+---
+
 # Using the Knative sample repository
 
 The Knative project provides a [sample repository](https://github.com/knative-extensions/sample-source) that contains a template for a basic event source controller and a receive adapter.

docs/eventing/custom-event-source/sinkbinding/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: explanation
+---
+
 # SinkBinding
 
 ![API version v1](https://img.shields.io/badge/API_Version-v1-green?style=flat-square)

docs/eventing/custom-event-source/sinkbinding/create-a-sinkbinding.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # Create a SinkBinding
 
 ![API version v1](https://img.shields.io/badge/API_Version-v1-green?style=flat-square)

docs/eventing/custom-event-source/sinkbinding/reference.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: reference
+---
+
 # SinkBinding reference
 
 ![API version v1](https://img.shields.io/badge/API_Version-v1-green?style=flat-square)

docs/eventing/event-delivery.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # Handling Delivery Failure
 
 You can configure event delivery parameters for Knative Eventing components that are applied in cases where an event fails to be delivered

docs/eventing/event-mesh.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: explanation
+---
+
 # Event Mesh
 
 An Event Mesh is dynamic, interconnected infrastructure which is designed to simplify distributing events from senders to recipients.  Similar to traditional message-channel architectures like Apache Kafka or RabbitMQ, an Event Mesh provides asynchronous (store-and-forward) delivery of messages which allows decoupling senders and recipients in time.  Unlike traditional message-channel based integration patterns, Event Meshes also simplify the routing concerns of senders and recipients by decoupling them from the underlying event transport infrastructure (which may be a federated set of solutions like Kafka, RabbitMQ, or cloud provider infrastructure).  The mesh transports events from producers to consumers via a network of interconnected _event brokers_ across any environment, and even between clouds in a seamless and loosely coupled way.

docs/eventing/event-registry/README.md

@@ -1,3 +1,11 @@
+---
+audience: developer
+components:
+  - eventing
+function: explanation
+# And function: how-to
+---
+
 # Event registry
 
 Knative Eventing defines an `EventType` object to make it easier for consumers to discover the types of events they can consume from Brokers or Channels.

docs/eventing/event-registry/eventmesh-backstage-plugin.md

@@ -1,3 +1,11 @@
+---
+audience: developer
+# And audience: administrator for install
+components:
+  - eventing
+function: how-to
+---
+
 # Knative Event Mesh Backstage Plugin
 
 !!! info

docs/eventing/faq/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: reference
+---
+
 # Eventing FAQs
 
 ## What is a Sugar Controller?

docs/eventing/features/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: reference
+---
+
 # Eventing Features
 
 To keep Knative innovative, the maintainers of this project have developed an

docs/eventing/features/authorization.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # Knative Eventing Authorization
 
 **Tracking issue**: [#7256](https://github.com/knative/eventing/issues/7256)

docs/eventing/features/cross-namespace-event-links.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # Cross Namespace Event Links
 
 **Flag name**: `cross-namespace-event-links`

docs/eventing/features/delivery-retryafter.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # DeliverySpec.RetryAfterMax field
 
 **Flag name**: `delivery-retryafter`

docs/eventing/features/delivery-timeout.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # DeliverySpec.Timeout field
 
 **Flag name**: `delivery-timeout`

docs/eventing/features/eventtype-auto-creation.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # EventType auto creation for improved discoverability
 
 **Flag name**: `eventtype-auto-create`

docs/eventing/features/istio-integration.md

@@ -1,3 +1,10 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 # Eventing integration with Istio service mesh
 
 **Flag name**: `istio`

docs/eventing/features/kreference-group.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: reference
+---
+
 # KReference.Group field
 
 **Flag name**: `kreference-group`

docs/eventing/features/kreference-mapping.md

@@ -1,3 +1,10 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 # Knative reference mapping
 
 **Flag name**: `kreference-mapping`

docs/eventing/features/new-apiserversource-filters.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: reference
+---
+
 # New trigger filters
 
 **Flag name**: `new-apiserversource-filters`

docs/eventing/features/sender-identity.md

@@ -1,3 +1,10 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 # Sender Identity for Knative Eventing
 
 **Flag name**: `authentication-oidc`

docs/eventing/features/transport-encryption.md

@@ -1,3 +1,10 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 # Transport Encryption for Knative Eventing
 
 **Flag name**: `transport-encryption`

docs/eventing/flows/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: reference
+---
+
 # Eventing Flows
 
 Knative Eventing provides a collection of [custom resource definitions (CRDs)](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) that you can use to define event flows:

docs/eventing/flows/parallel.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: explanation
+---
+
 # Parallel
 
 Parallel CRD provides a way to easily define a list of branches, each receiving

docs/eventing/flows/sequence/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: explanation
+---
+
 # Sequence
 
 Sequence CRD provides a way to define an in-order list of functions that will be

docs/eventing/flows/sequence/sequence-reply-to-event-display/README.md

@@ -1,3 +1,11 @@
+---
+audience: developer
+components:
+  - eventing
+  - serving
+function: how-to
+---
+
 # Sequence wired to event-display
 
 We are going to create the following logical configuration. We create a

docs/eventing/flows/sequence/sequence-reply-to-sequence/README.md

@@ -1,3 +1,11 @@
+---
+audience: developer
+components:
+  - eventing
+  - serving
+function: how-to
+---
+
 # Sequence wired to another Sequence
 
 We are going to create the following logical configuration. We create a

docs/eventing/flows/sequence/sequence-terminal/README.md

@@ -1,3 +1,11 @@
+---
+audience: developer
+components:
+  - eventing
+  - serving
+function: how-to
+---
+
 # Sequence terminal
 
 We are going to create the following logical configuration. We create a

docs/eventing/flows/sequence/sequence-with-broker-trigger/README.md

@@ -1,3 +1,11 @@
+---
+audience: developer
+components:
+  - eventing
+  - serving
+function: how-to
+---
+
 # Using Sequence with Broker and Trigger
 
 We are going to create the following logical configuration. We create a

docs/eventing/observability/accessing-traces.md

@@ -1,3 +1,11 @@
+---
+audience: administrator
+# And audience: developer for accessing traces
+components:
+  - eventing
+function: how-to
+---
+
 # Accessing CloudEvent traces
 
 Traces give us the big picture of how events traverse through the system and applications.

docs/eventing/observability/logging/collecting-logs.md

@@ -1 +1,8 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 --8<-- "collecting-logs.md"

docs/eventing/observability/logging/config-logging.md

@@ -1 +1,8 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 --8<-- "configuring-logs.md"

docs/eventing/observability/metrics/collecting-metrics.md

@@ -1,3 +1,10 @@
+---
+audience: administrator
+components:
+  - eventing
+function: how-to
+---
+
 --8<-- "collecting-metrics.md"
 
 ### Enabling Metric Collection

docs/eventing/reference/eventing-api.md

@@ -1 +1,8 @@
+---
+audience: developer
+components:
+  - eventing
+function: reference
+---
+
 This file is updated to the correct version from the eventing repo (docs/eventing-api.md) during the build.

docs/eventing/sinks/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # About sinks
 
 When you create an event source, you can specify a _sink_ where events are sent to from the source. A sink is an _Addressable_ or a _Callable_ resource that can receive incoming events from other resources. Knative Services, Channels, and Brokers are all examples of sinks.

docs/eventing/sinks/integration-sink/README.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: reference
+---
+
 # Knative Sink for Apache Camel Kamelet integrations
 
 ![stage](https://img.shields.io/badge/Stage-alpah-red?style=flat-square)

docs/eventing/sinks/integration-sink/aws_s3.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # AWS S3 Sink
 
 The `IntegrationSink` supports the Amazon Web Services (AWS) S3 service, through its `aws.s3` property.

docs/eventing/sinks/integration-sink/aws_sns.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # AWS Simple Notification Service Sink
 
 The `IntegrationSink` supports the Amazon Web Services (AWS) Simple Notification Service (SNS) service, through its `aws.sns` property.

docs/eventing/sinks/integration-sink/aws_sqs.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # AWS Simple Queue Service Sink
 
 The `IntegrationSink` supports the Amazon Web Services (AWS) Simple Queue Service (SQS) service, through its `aws.sqs` property.

docs/eventing/sinks/integration-sink/logger.md

@@ -1,3 +1,10 @@
+---
+audience: developer
+components:
+  - eventing
+function: how-to
+---
+
 # Log Sink
 
 The `IntegrationSink` supports the _Log Sink Kamelet_ that logs all data that it receives, through its `log` property. This sink useful for debugging purposes.