docs: Fixed documentation

Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>

Author: ntkathole

.gitbook.yaml

@@ -6,3 +6,6 @@ structure:
 redirects:
   reference/telemetry: ./reference/usage.md
   quickstart: ./getting-started/quickstart.md
+  reference/feature-store-yaml: ./reference/feature-repository/feature-store-yaml.md
+  reference/feast-ignore: ./reference/feature-repository/feast-ignore.md
+  reference/feature-repository: ./reference/feature-repository/README.md

docs/SUMMARY.md

@@ -23,7 +23,12 @@
   * [Project](getting-started/concepts/project.md)
   * [Data ingestion](getting-started/concepts/data-ingestion.md)
   * [Entity](getting-started/concepts/entity.md)
+  * [Data types](getting-started/concepts/feast-types.md)
+  * [Feature repository](getting-started/concepts/feature-repo.md)
   * [Feature view](getting-started/concepts/feature-view.md)
+  * [Batch feature view](getting-started/concepts/batch-feature-view.md)
+  * [Stream feature view](getting-started/concepts/stream-feature-view.md)
+  * [Tiling with Intermediate Representations](getting-started/concepts/tiling.md)
   * [Label view](getting-started/concepts/label-view.md)
   * [Feature retrieval](getting-started/concepts/feature-retrieval.md)
   * [Point-in-time joins](getting-started/concepts/point-in-time-joins.md)
@@ -38,6 +43,7 @@
   * [Online store](getting-started/components/online-store.md)
   * [Feature server](getting-started/components/feature-server.md)
   * [Compute Engine](getting-started/components/compute-engine.md)
+  * [Stream Processor](getting-started/components/stream-processor.md)
   * [Provider](getting-started/components/provider.md)
   * [Authorization Manager](getting-started/components/authz_manager.md)
   * [OpenTelemetry Integration](getting-started/components/open-telemetry.md)
@@ -85,13 +91,14 @@
 * [Feast Production Deployment Topologies](how-to-guides/production-deployment-topologies.md)
 * [Online Server Performance Tuning](how-to-guides/online-server-performance-tuning.md)
 * [Customizing Feast](how-to-guides/customizing-feast/README.md)
-  * [Adding a custom batch materialization engine](how-to-guides/customizing-feast/creating-a-custom-materialization-engine.md)
+  * [Adding a custom compute engine](how-to-guides/customizing-feast/creating-a-custom-compute-engine.md)
   * [Adding a new offline store](how-to-guides/customizing-feast/adding-a-new-offline-store.md)
   * [Adding a new online store](how-to-guides/customizing-feast/adding-support-for-a-new-online-store.md)
   * [Adding a custom provider](how-to-guides/customizing-feast/creating-a-custom-provider.md)
 * [Adding or reusing tests](how-to-guides/adding-or-reusing-tests.md)
 * [Starting Feast servers in TLS(SSL) Mode](how-to-guides/starting-feast-servers-tls-mode.md)
 * [Importing Features from dbt](how-to-guides/dbt-integration.md)
+* [Entity Key Serialization (v2 to v3)](how-to-guides/entity-reserialization-of-from-v2-to-v3.md)
 * [Feature Quality Monitoring](how-to-guides/feature-monitoring.md)
 
 ## Reference
@@ -162,12 +169,15 @@
   * [Faiss](reference/online-stores/faiss.md)
   * [Hybrid](reference/online-stores/hybrid.md)
 * [Registries](reference/registries/README.md)
+  * [Metadata](reference/registries/metadata.md)
   * [Local](reference/registries/local.md)
   * [S3](reference/registries/s3.md)
   * [GCS](reference/registries/gcs.md)
   * [SQL](reference/registries/sql.md)
   * [Snowflake](reference/registries/snowflake.md)
+  * [HDFS](reference/registries/hdfs.md)
   * [Remote](reference/registries/remote.md)
+  * [Registry permissions](reference/registry/registry-permissions.md)
 * [Providers](reference/providers/README.md)
   * [Local](reference/providers/local.md)
   * [Google Cloud Platform](reference/providers/google-cloud-platform.md)
@@ -182,6 +192,9 @@
 * [Feature repository](reference/feature-repository/README.md)
   * [feature\_store.yaml](reference/feature-repository/feature-store-yaml.md)
   * [.feastignore](reference/feature-repository/feast-ignore.md)
+  * [Registration inferencing](reference/feature-repository/registration-inferencing.md)
+* [Kubernetes auth setup](reference/auth/kubernetes_auth_setup.md)
+* [User token provisioning](reference/auth/user_token_provisioning.md)
 * [Feature servers](reference/feature-servers/README.md)
   * [Python feature server](reference/feature-servers/python-feature-server.md)
   * [\[Alpha\] Go feature server](reference/feature-servers/go-feature-server.md)
@@ -222,3 +235,4 @@
   * [ADR-0009: Contribution and Extensibility](adr/ADR-0009-contribution-extensibility.md)
   * [ADR-0010: Vector Database Integration](adr/ADR-0010-vector-database-integration.md)
   * [ADR-0011: Data Quality Monitoring](adr/ADR-0011-data-quality-monitoring.md)
+  * [ADR-0012: LabelView](adr/ADR-0012-label-view.md)

docs/getting-started/components/README.md

@@ -20,6 +20,10 @@
 [compute-engine.md](compute-engine.md)
 {% endcontent-ref %}
 
+{% content-ref url="stream-processor.md" %}
+[stream-processor.md](stream-processor.md)
+{% endcontent-ref %}
+
 {% content-ref url="provider.md" %}
 [provider.md](provider.md)
 {% endcontent-ref %}

docs/getting-started/concepts/README.md

@@ -16,6 +16,14 @@
 [entity.md](entity.md)
 {% endcontent-ref %}
 
+{% content-ref url="feast-types.md" %}
+[feast-types.md](feast-types.md)
+{% endcontent-ref %}
+
+{% content-ref url="feature-repo.md" %}
+[feature-repo.md](feature-repo.md)
+{% endcontent-ref %}
+
 {% content-ref url="feature-view.md" %}
 [feature-view.md](feature-view.md)
 {% endcontent-ref %}
@@ -44,6 +52,10 @@
 [dataset.md](dataset.md)
 {% endcontent-ref %}
 
+{% content-ref url="label-view.md" %}
+[label-view.md](label-view.md)
+{% endcontent-ref %}
+
 {% content-ref url="permission.md" %}
 [permission.md](permission.md)
 {% endcontent-ref %}

docs/getting-started/concepts/label-view.md

@@ -30,7 +30,7 @@ Before using label views, you need:
 
 **Generate training datasets.** Compose label views with feature views in a `FeatureService` and retrieve features + labels together with point-in-time correctness.
 
-**Annotate in the UI.** Configure annotation profiles so data scientists can label data directly in the Feast UI — entity forms, document spans, bulk review, or active learning.
+**Data label in the UI.** Configure data labeling profiles (annotation profiles) so data scientists can label data directly in the Feast UI — entity forms, document spans, bulk review, or active learning.
 
 ## Feedback vs Expectations
 
@@ -85,10 +85,10 @@ store.push("agent_feedback_labels_push_source", labels_df)
 
 | Use a **FeatureView** when… | Use a **LabelView** when… |
 |---|---|
-| Data is observational and append-only | Data is a judgment or annotation |
+| Data is observational and append-only | Data is a judgment or data label (annotation) |
 | One source writes the data | Multiple labelers may disagree |
 | No conflict resolution needed | You need governed conflict resolution |
-| No labeling UI needed | You want structured annotation workflows |
+| No labeling UI needed | You want structured data labeling workflows (annotation) |
 
 ## How Label Views Work
 
@@ -164,14 +164,14 @@ store.push("agent_feedback_labels_push_source", labels_df)
 
 Each push appends to the offline store (full history retained) and updates the online store (latest value per key).
 
-### Step 3: Annotate in the Feast UI
+### Step 3: Data label in the Feast UI
 
-Open the label view in the Feast UI **Annotate** tab. The UI reads annotation tags and shows the right workflow:
+Open the label view in the Feast UI **Data Labeling** tab (Annotate tab). The UI reads data labeling tags (annotation tags) and shows the right workflow:
 
 1. Open **Label Views** in the sidebar
-2. Select a label view (check the **Annotation** badge on the list page)
-3. Go to the **Annotate** tab
-4. Choose a method (Entity Form, Document Span, Review & Edit, or Active Learning)
+2. Select a label view (check the **Data Labeling** badge on the list page)
+3. Go to the **Data Labeling** tab (Annotate tab)
+4. Choose a data labeling method (annotation method): Entity Form, Document Span, Review & Edit, or Active Learning
 5. Submit labels — they are pushed to the label view's `PushSource`
 
 ### Step 4: Join labels with features for training
@@ -193,16 +193,16 @@ training_df = store.get_historical_features(
 
 Training pipelines get features and resolved labels in one retrieval call.
 
-## Annotation Profiles
+## Data Labeling Profiles (Annotation Profiles)
 
-Annotation profiles configure **how** labels are created in the UI. Set them via `tags` — no schema changes required.
+Data labeling profiles (annotation profiles) configure **how** labels are created in the UI. Set them via `tags` — no schema changes required.
 
 ### Supported profiles
 
 | Profile | Best for | UI experience |
 |---|---|---|
 | `entity-form` | RLHF, safety review, per-entity feedback | Form — one entity at a time |
-| `document-span` | RAG chunk labeling, span annotation | Load document, label chunks |
+| `document-span` | RAG chunk labeling, span labeling (annotation) | Load document, label chunks |
 | `table` | Bulk review, correcting existing labels | Editable table with dropdowns |
 | `active-learning` | Label high-value unlabeled entities | Queue from a reference feature view |
 
@@ -215,7 +215,7 @@ Answer one question:
 3. **"I need to correct labels in bulk"** → `table`
 4. **"I want to label only the most valuable unlabeled items"** → `active-learning` (requires `reference_feature_view`)
 
-The **Annotate** tab shows only relevant methods per profile:
+The **Data Labeling** tab (Annotate tab) shows only relevant data labeling methods (annotation methods) per profile:
 
 | Profile | Methods shown |
 |---|---|
@@ -228,7 +228,7 @@ The **Annotate** tab shows only relevant methods per profile:
 
 | Tag | Purpose | Example values |
 |---|---|---|
-| `feast.io/labeling-method` | Primary UI workflow | `entity-form`, `document-span`, `table` |
+| `feast.io/labeling-method` | Primary data labeling method (annotation method) | `entity-form`, `document-span`, `table` |
 | `feast.io/field-role:<field>` | Semantic role of a field | `feedback`, `expectation`, `label`, `metadata`, `content`, `span_start`, `span_end` |
 | `feast.io/label-values:<field>` | Allowed label values | `relevant,irrelevant` |
 | `feast.io/label-widget:<field>` | Input widget type | `enum`, `binary`, `text`, `number` |
@@ -325,7 +325,7 @@ When multiple labelers write different values for the same entity, `ConflictPoli
 |---|---|
 | `LAST_WRITE_WINS` | Default. Most recent write wins. |
 | `LABELER_PRIORITY` | Trusted labelers override others (e.g. human over LLM judge). |
-| `MAJORITY_VOTE` | Consensus labeling (e.g. multiple annotators on RAG chunks). |
+| `MAJORITY_VOTE` | Consensus labeling (e.g. multiple labelers on RAG chunks). |
 
 {% hint style="info" %}
 Conflict policies apply to the **offline store** (training). The **online store** always uses last-write-wins. Full label history is always retained in the offline store.
@@ -337,20 +337,20 @@ Conflict policies apply to the **offline store** (training). The **online store*
 
 **Tag field roles.** Set `feast.io/field-role:<field>` to `feedback` or `expectation` so your team and UI know what each field means.
 
-**Match conflict policy to label type.** Use `LABELER_PRIORITY` when humans correct automated judges. Use `MAJORITY_VOTE` for multi-annotator consensus. Use `LAST_WRITE_WINS` for simple feedback streams.
+**Match conflict policy to label type.** Use `LABELER_PRIORITY` when humans correct automated judges. Use `MAJORITY_VOTE` for multi-labeler consensus. Use `LAST_WRITE_WINS` for simple feedback streams.
 
-**Link to features.** Set `reference_feature_view` so the UI and documentation show which feature view the labels annotate.
+**Link to features.** Set `reference_feature_view` so the UI and documentation show which feature view the labels apply to.
 
 **Separate noisy feedback from stable ground truth.** When possible, put expectations in dedicated fields or views with stricter writer conventions (human-only).
 
 ## Limitations
 
 * Conflict policies are enforced on offline reads only; online store is always last-write-wins.
 * `LABELER_PRIORITY` requires explicit labeler ordering configuration.
-* Annotation profiles are UI configuration via tags — not enforced at the SDK write path.
+* Data labeling profiles (annotation profiles) are UI configuration via tags — not enforced at the SDK write path.
 
 ## Next steps
 
-* [Feature view](feature-view.md) — immutable features that label views annotate
+* [Feature view](feature-view.md) — immutable features that label views apply labels to
 * [Feature retrieval](feature-retrieval.md) — point-in-time joins for training
 * [ADR-0012: LabelView](../../adr/ADR-0012-label-view.md) — full design rationale

docs/how-to-guides/customizing-feast/README.md

@@ -15,8 +15,8 @@ Below are some guides on how to add new custom components:
 [adding-support-for-a-new-online-store.md](adding-support-for-a-new-online-store.md)
 {% endcontent-ref %}
 
-{% content-ref url="creating-a-custom-materialization-engine.md" %}
-[creating-a-custom-materialization-engine.md](creating-a-custom-materialization-engine.md)
+{% content-ref url="creating-a-custom-compute-engine.md" %}
+[creating-a-custom-compute-engine.md](creating-a-custom-compute-engine.md)
 {% endcontent-ref %}
 
 {% content-ref url="creating-a-custom-provider.md" %}

docs/reference/feature-repository/README.md

@@ -127,4 +127,4 @@ To declare new feature definitions, just add code to the feature repository, eit
 ### Next steps
 
 * See [Create a feature repository](../../how-to-guides/feast-snowflake-gcp-aws/create-a-feature-repository.md) to get started with an example feature repository.
-* See [feature_store.yaml](feature-store-yaml.md), [.feastignore](feast-ignore.md), or [Feature Views](../../getting-started/concepts/feature-view.md) for more information on the configuration files that live in a feature registry.
+* See [feature_store.yaml](feature-store-yaml.md), [.feastignore](feast-ignore.md), [Registration inferencing](registration-inferencing.md), or [Feature Views](../../getting-started/concepts/feature-view.md) for more information on the configuration files that live in a feature registry.