Skip to content

Commit

Permalink
docs: sort feature section alphabetically (#10400)
Browse files Browse the repository at this point in the history
  • Loading branch information
yoonhyejin authored May 13, 2024
1 parent b8b7928 commit 3dc5326
Show file tree
Hide file tree
Showing 16 changed files with 134 additions and 71 deletions.
171 changes: 117 additions & 54 deletions docs-website/sidebars.js
Original file line number Diff line number Diff line change
Expand Up @@ -43,75 +43,138 @@ module.exports = {
description: "Learn about the features of DataHub.",
},
items: [
"docs/ui-ingestion",
"docs/how/search",
"docs/schema-history",
// "docs/how/ui-tabs-guide",
"docs/domains",
"docs/dataproducts",
"docs/glossary/business-glossary",
"docs/tags",
"docs/ownership/ownership-types",
"docs/authorization/access-policies-guide",
"docs/features/dataset-usage-and-query-history",
"docs/posts",
"docs/sync-status",
"docs/incidents/incidents",
"docs/generated/lineage/lineage-feature-guide",
"docs/businessattributes",
{
label: "Assertions",
type: "category",
link: { type: "doc", id: "docs/managed-datahub/observe/assertions" },
items: [
{
label: "Column Assertions",
type: "doc",
id: "docs/managed-datahub/observe/column-assertions",
className: "saasOnly",
},
{
label: "Custom SQL Assertions",
type: "doc",
id: "docs/managed-datahub/observe/custom-sql-assertions",
className: "saasOnly",
},
{
label: "Freshness Assertions",
type: "doc",
id: "docs/managed-datahub/observe/freshness-assertions",
className: "saasOnly",
},
{
label: "Volume Assertions",
type: "doc",
id: "docs/managed-datahub/observe/volume-assertions",
className: "saasOnly",
},
],
},
{
label: "Business Attributes",
type: "doc",
id: "docs/tests/metadata-tests",
className: "saasOnly",
id: "docs/businessattributes",
},
{
label: "Business Glossary",
type: "doc",
id: "docs/glossary/business-glossary",
},
{
label: "Data Contract",
type: "doc",
id: "docs/managed-datahub/observe/data-contract",
},
{
label: "Data Products",
type: "doc",
id: "docs/dataproducts",
},
{
label: "Dataset Usage and Query History",
type: "doc",
id: "docs/features/dataset-usage-and-query-history",
},
{
label: "Domains",
type: "doc",
id: "docs/domains",
},
{
label: "Incidents",
type: "doc",
id: "docs/incidents/incidents",
},
{
label: "Ingestion",
type: "doc",
id: "docs/ui-ingestion",
},
"docs/act-on-metadata/impact-analysis",
{
label: "Observability",
label: "Lineage",
type: "category",
link: {
type: "doc",
id: "docs/generated/lineage/lineage-feature-guide",
},
items: [
{
label: "Assertions",
type: "category",
link: {
type: "doc",
id: "docs/managed-datahub/observe/assertions",
},
items: [
{
type: "doc",
id: "docs/managed-datahub/observe/freshness-assertions",
className: "saasOnly",
},
{
type: "doc",
id: "docs/managed-datahub/observe/volume-assertions",
className: "saasOnly",
},
{
type: "doc",
id: "docs/managed-datahub/observe/custom-sql-assertions",
className: "saasOnly",
},
{
type: "doc",
id: "docs/managed-datahub/observe/column-assertions",
className: "saasOnly",
},
{
type: "doc",
id: "docs/managed-datahub/observe/schema-assertions",
className: "saasOnly",
},
],
label: "Lineage Impact analysis",
type: "doc",
id: "docs/act-on-metadata/impact-analysis",
},
{
label: "Managing Lineage via UI",
type: "doc",
id: "docs/managed-datahub/observe/data-contract",
id: "docs/features/feature-guides/ui-lineage",
},
],
},
{
Guides: ["docs/features/feature-guides/ui-lineage"],
label: "Metadata Tests",
type: "doc",
id: "docs/tests/metadata-tests",
className: "saasOnly",
},
{
label: "Ownership",
type: "doc",
id: "docs/ownership/ownership-types",
},
{
label: "Policies",
type: "doc",
id: "docs/authorization/access-policies-guide",
},
{
label: "Posts",
type: "doc",
id: "docs/posts",
},
{
label: "Schema history",
type: "doc",
id: "docs/schema-history",
},
{
label: "Search",
type: "doc",
id: "docs/how/search",
},
{
label: "Sync Status",
type: "doc",
id: "docs/sync-status",
},
{
label: "Tags",
type: "doc",
id: "docs/tags",
},
],
},
Expand Down
2 changes: 1 addition & 1 deletion docs/_feature-guide-template.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import FeatureAvailability from '@site/src/components/FeatureAvailability';

# About DataHub [Feature Name]
# [Feature Name]

<!-- All Feature Guides should begin with `About DataHub ` to improve SEO -->

Expand Down
2 changes: 1 addition & 1 deletion docs/act-on-metadata/impact-analysis.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import FeatureAvailability from '@site/src/components/FeatureAvailability';

# About DataHub Lineage Impact Analysis
# Lineage Impact Analysis

<FeatureAvailability/>

Expand Down
2 changes: 1 addition & 1 deletion docs/authentication/personal-access-tokens.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import FeatureAvailability from '@site/src/components/FeatureAvailability';

# About DataHub Personal Access Tokens
# Personal Access Tokens

<FeatureAvailability/>

Expand Down
2 changes: 1 addition & 1 deletion docs/authorization/access-policies-guide.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# About DataHub Access Policies
# Access Policies

<FeatureAvailability/>

Expand Down
2 changes: 1 addition & 1 deletion docs/authorization/roles.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import FeatureAvailability from '@site/src/components/FeatureAvailability';

# About DataHub Roles
# Roles

<FeatureAvailability/>

Expand Down
2 changes: 1 addition & 1 deletion docs/domains.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import FeatureAvailability from '@site/src/components/FeatureAvailability';

# About DataHub Domains
# Domains

<FeatureAvailability/>

Expand Down
2 changes: 1 addition & 1 deletion docs/features/dataset-usage-and-query-history.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import FeatureAvailability from '@site/src/components/FeatureAvailability';

# About DataHub Dataset Usage & Query History
# Dataset Usage & Query History

<FeatureAvailability/>

Expand Down
2 changes: 1 addition & 1 deletion docs/glossary/business-glossary.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ title: Business Glossary

import FeatureAvailability from '@site/src/components/FeatureAvailability';

# About DataHub Business Glossary
# Business Glossary

<FeatureAvailability/>

Expand Down
2 changes: 1 addition & 1 deletion docs/how/search.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import FeatureAvailability from '@site/src/components/FeatureAvailability';

# About DataHub Search
# Search

<FeatureAvailability/>

Expand Down
6 changes: 3 additions & 3 deletions docs/incidents/incidents.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ description: This page provides an overview of working with the DataHub Incident
import FeatureAvailability from '@site/src/components/FeatureAvailability';


# About Incidents
# Incidents

<FeatureAvailability/>

Expand All @@ -14,8 +14,8 @@ import FeatureAvailability from '@site/src/components/FeatureAvailability';

A couple scenarios in which incidents can be useful are

1**Communicating Assets with Ongoing Issues**: You can mark a known-bad data asset as under an ongoing incident so consumers and stakeholders can be informed about the health status of a data asset via the DataHub UI. Moreover, they can follow the incident as it progresses toward resolution.
2**Pipeline Circuit Breaking (advanced):** You can use Incidents as a basis for orchestrating and blocking data pipelines that have inputs with active issues to avoid propagating bad data downstream.
1. **Communicating Assets with Ongoing Issues**: You can mark a known-bad data asset as under an ongoing incident so consumers and stakeholders can be informed about the health status of a data asset via the DataHub UI. Moreover, they can follow the incident as it progresses toward resolution.
2. **Pipeline Circuit Breaking (advanced):** You can use Incidents as a basis for orchestrating and blocking data pipelines that have inputs with active issues to avoid propagating bad data downstream.

In the next section, we'll walk through how to

Expand Down
2 changes: 1 addition & 1 deletion docs/managed-datahub/approval-workflows.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import FeatureAvailability from '@site/src/components/FeatureAvailability';

# About DataHub Approval Workflows
# Approval Workflows

<FeatureAvailability saasOnly />

Expand Down
2 changes: 1 addition & 1 deletion docs/posts.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import FeatureAvailability from '@site/src/components/FeatureAvailability';

# About DataHub Posts
# Posts

<FeatureAvailability/>
DataHub allows users to make Posts that can be displayed on the app. Currently, Posts are only supported on the Home Page, but may be extended to other surfaces of the app in the future. Posts can be used to accomplish the following:
Expand Down
2 changes: 1 addition & 1 deletion docs/schema-history.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import FeatureAvailability from '@site/src/components/FeatureAvailability';

# About DataHub Schema History
# Schema History

<FeatureAvailability/>

Expand Down
2 changes: 1 addition & 1 deletion docs/sync-status.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import FeatureAvailability from '@site/src/components/FeatureAvailability';

# About DataHub Sync Status
# Sync Status

<FeatureAvailability/>

Expand Down
2 changes: 1 addition & 1 deletion docs/tags.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import FeatureAvailability from '@site/src/components/FeatureAvailability';

# About DataHub Tags
# Tags

<FeatureAvailability/>

Expand Down

0 comments on commit 3dc5326

Please sign in to comment.