Merge pull request #10 from open-metadata/fix_build

Fix followers specification

Author: harshach

docs/data-assets/apis/api-endpoint.md

@@ -1365,29 +1365,7 @@ for details on defining and using custom properties.
 
 ## Followers
 
-**Stay informed about API endpoint changes**
-
-Followers allow users to "follow" API endpoints and receive notifications when they change. This is critical for:
-
-- **API Consumers**: Monitor endpoints your applications depend on
-- **Backend Engineers**: Track endpoints you own or maintain
-- **Integration Teams**: Stay informed about contract changes
-- **API Product Managers**: Monitor endpoint usage and evolution
-
-**Key Benefits**:
-- Receive notifications about breaking changes to request/response schemas
-- Track deprecation notices and versioning changes
-- Monitor authentication or rate limiting updates
-- Get alerts for SLA or performance threshold changes
-
-**Common Use Cases**:
-- Frontend developers follow endpoints their apps consume
-- Backend engineers follow production endpoints they maintain
-- DevOps teams follow critical API endpoints for monitoring
-- Product teams follow public API endpoints for customer impact
-
-!!! tip "Learn More"
-    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about configuring notifications, best practices, and integration with webhooks.
+Users can follow API endpoints to receive notifications about schema changes, deprecation notices, and authentication updates. See **[Followers](../../metadata-specifications/followers.md)** for details.
 
 ---
 

docs/data-assets/dashboards/chart.md

@@ -1014,29 +1014,7 @@ for details on defining and using custom properties.
 
 ## Followers
 
-**Stay informed about chart changes**
-
-Followers allow users to "follow" individual charts and receive notifications when they change. This is useful for:
-
-- **Chart Creators**: Monitor charts they've built
-- **Metric Owners**: Track visualizations of key business metrics
-- **Stakeholders**: Stay informed about specific KPI visualizations
-- **Collaboration**: Work with team members on chart refinements
-
-**Key Benefits**:
-- Receive notifications about chart configuration changes
-- Track changes to underlying queries or data sources
-- Monitor visualization type or display property updates
-- Get alerts for ownership or deprecation changes
-
-**Common Use Cases**:
-- Analysts follow charts they created or maintain
-- Business users follow charts showing their KPIs
-- Data teams follow charts using complex calculations
-- Executives follow critical metric visualizations
-
-!!! tip "Learn More"
-    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about configuring notifications, best practices, and integration with webhooks.
+Users can follow charts to receive notifications about visualization changes, query modifications, and data source updates. See **[Followers](../../metadata-specifications/followers.md)** for details.
 
 ---
 

docs/data-assets/dashboards/dashboard.md

@@ -1036,29 +1036,7 @@ for details on defining and using custom properties.
 
 ## Followers
 
-**Stay informed about dashboard changes**
-
-Followers allow users to "follow" a dashboard and receive notifications when it changes. This is particularly valuable for:
-
-- **Business Stakeholders**: Track dashboards with key business metrics and KPIs
-- **Report Consumers**: Get notified when dashboards are updated or metrics change
-- **Collaboration**: Stay in sync with team members working on shared dashboards
-- **Governance**: Monitor dashboards for compliance and data quality
-
-**Key Benefits**:
-- Receive notifications about dashboard updates and refreshes
-- Track changes to underlying data sources or calculations
-- Monitor chart additions, removals, or modifications
-- Get alerts for ownership, tier, or governance changes
-
-**Common Use Cases**:
-- Executives follow executive dashboards for KPI tracking
-- Product managers follow dashboards tracking product metrics
-- Analysts follow dashboards they've created or contributed to
-- Data engineers follow dashboards to monitor data pipeline health
-
-!!! tip "Learn More"
-    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about configuring notifications, best practices, and integration with webhooks.
+Users can follow dashboards to receive notifications about updates, chart changes, and data source modifications. See **[Followers](../../metadata-specifications/followers.md)** for details.
 
 ---
 

docs/data-assets/databases/database.md

@@ -751,34 +751,7 @@ for details on defining and using custom properties.
 
 ## Followers
 
-**Stay informed about database changes**
-
-Followers allow users to "follow" a database and receive notifications when it changes. This is useful for:
-
-- **Monitoring Dependencies**: Get notified when databases your applications depend on change
-- **Staying Informed**: Track databases you're interested in without being the owner
-- **Collaboration**: Stay in sync with team members working on the same databases
-- **Governance**: Monitor databases with compliance requirements
-
-**Key Benefits**:
-- Receive notifications about schema changes, new schemas, or deletions
-- Track governance changes (tags, ownership, domain assignments)
-- Monitor data quality issues at the database level
-- Get alerts for deprecation notices
-
-**Following vs Ownership**:
-- **Ownership** = Responsibility and accountability for the database
-- **Following** = Interest and awareness about the database
-
-Any user can follow any database they have access to. A database can have multiple followers.
-
-!!! tip "Learn More"
-    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about:
-
-    - How to follow databases via UI and API
-    - Notification preferences and configuration
-    - Best practices for using followers effectively
-    - Integration with webhooks and activity feeds
+Users can follow databases to receive notifications about changes such as schema updates, governance changes, or deprecation notices. See **[Followers](../../metadata-specifications/followers.md)** for details.
 
 ---
 

docs/data-assets/databases/table.md

@@ -1324,42 +1324,7 @@ for details on defining and using custom properties.
 
 ## Followers
 
-**Stay informed about table changes**
-
-Followers allow users to "follow" a table and receive notifications when it changes. This is one of the most useful features for data practitioners:
-
-- **Monitor Dependencies**: Get notified when tables your applications or dashboards depend on change
-- **Schema Changes**: Receive alerts when columns are added, removed, or modified
-- **Data Quality**: Be notified of test failures, anomalies, or freshness issues
-- **Collaboration**: Track tables you're working on with others
-
-**Key Benefits**:
-- Receive notifications about schema changes (new columns, type changes)
-- Track data quality test results and failures
-- Monitor data profiling anomalies (unusual null rates, distribution changes)
-- Get alerts for deprecation, tier changes, or ownership updates
-- Stay informed about query usage patterns and popularity
-
-**Following vs Ownership**:
-- **Ownership** = Responsibility and accountability for the table's quality and accuracy
-- **Following** = Interest in being notified about changes to the table
-
-Any user can follow any table they have access to. Tables typically have multiple followers (analysts, engineers, data scientists who use the data).
-
-**Common Use Cases**:
-- Data scientists follow source tables for their ML models
-- Analysts follow tables used in their reports and dashboards
-- Data engineers follow tables in production pipelines
-- Compliance officers follow tables containing PII or sensitive data
-
-!!! tip "Learn More"
-    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about:
-
-    - How to follow tables via UI and API
-    - Configuring notification preferences (immediate vs digest)
-    - Best practices for avoiding notification overload
-    - Bulk following patterns (e.g., follow all tables in a domain)
-    - Integration with webhooks and Slack/Teams
+Users can follow tables to receive notifications about schema changes, data quality issues, profiling anomalies, and ownership updates. See **[Followers](../../metadata-specifications/followers.md)** for details.
 
 ---
 

docs/data-assets/messaging/topic.md

@@ -1235,29 +1235,7 @@ for details on defining and using custom properties.
 
 ## Followers
 
-**Stay informed about topic changes**
-
-Followers allow users to "follow" a topic and receive notifications when it changes. This is critical for:
-
-- **Event Producers**: Monitor topics they publish to
-- **Event Consumers**: Track schema changes in topics they consume
-- **Platform Teams**: Get notified of topic configuration changes
-- **Compliance**: Monitor topics with sensitive data
-
-**Key Benefits**:
-- Receive notifications about schema changes (critical for compatibility)
-- Track partition count or replication factor changes
-- Monitor retention policy or configuration updates
-- Get alerts for deprecation, ownership, or governance changes
-
-**Common Use Cases**:
-- Developers follow topics their services consume
-- Platform engineers follow all production topics
-- Data scientists follow topics with ML training events
-- Compliance officers follow topics with PII or sensitive data
-
-!!! tip "Learn More"
-    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about configuring notifications, best practices, and integration with webhooks.
+Users can follow topics to receive notifications about schema changes, partition updates, and configuration modifications. See **[Followers](../../metadata-specifications/followers.md)** for details.
 
 ---
 

docs/data-assets/ml/mlmodel.md

@@ -1421,29 +1421,7 @@ for details on defining and using custom properties.
 
 ## Followers
 
-**Stay informed about ML model changes**
-
-Followers allow users to "follow" an ML model and receive notifications when it changes. This is valuable for:
-
-- **Data Scientists**: Monitor models they've developed or deployed
-- **ML Engineers**: Track model version changes and deployments
-- **Stakeholders**: Stay informed about production model updates
-- **Compliance**: Monitor models for governance and regulatory requirements
-
-**Key Benefits**:
-- Receive notifications about model version updates
-- Track feature or algorithm changes
-- Monitor performance metrics and drift
-- Get alerts for ownership, deprecation, or governance updates
-
-**Common Use Cases**:
-- Data scientists follow models in production
-- ML engineers follow models they deploy and maintain
-- Product managers follow models powering product features
-- Compliance teams follow models with regulatory implications
-
-!!! tip "Learn More"
-    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about configuring notifications, best practices, and integration with webhooks.
+Users can follow ML models to receive notifications about version updates, performance metrics, and deployment changes. See **[Followers](../../metadata-specifications/followers.md)** for details.
 
 ---
 

docs/data-assets/pipelines/pipeline.md

@@ -1209,29 +1209,7 @@ for details on defining and using custom properties.
 
 ## Followers
 
-**Stay informed about pipeline changes**
-
-Followers allow users to "follow" a pipeline and receive notifications when it changes. This is essential for:
-
-- **Data Engineers**: Monitor pipelines they own or maintain
-- **Pipeline Dependencies**: Track upstream/downstream pipeline changes
-- **Operations**: Get notified of pipeline failures or configuration changes
-- **Stakeholders**: Stay informed about ETL processes affecting their data
-
-**Key Benefits**:
-- Receive notifications about pipeline configuration changes
-- Track task additions, removals, or modifications
-- Monitor pipeline schedule or trigger changes
-- Get alerts for ownership, deprecation, or governance updates
-
-**Common Use Cases**:
-- Data engineers follow production pipelines they maintain
-- Analysts follow pipelines that refresh their reports
-- Data scientists follow pipelines feeding their ML models
-- Operations teams follow critical data pipelines
-
-!!! tip "Learn More"
-    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about configuring notifications, best practices, and integration with webhooks.
+Users can follow pipelines to receive notifications about configuration changes, task modifications, and schedule updates. See **[Followers](../../metadata-specifications/followers.md)** for details.
 
 ---
 

docs/data-assets/storage/container.md

@@ -1509,29 +1509,7 @@ for details on defining and using custom properties.
 
 ## Followers
 
-**Stay informed about container changes**
-
-Followers allow users to "follow" storage containers and receive notifications when they change. This is important for:
-
-- **Data Engineers**: Monitor data lake containers with production data
-- **Analytics Teams**: Track containers with analytical datasets
-- **Data Scientists**: Stay informed about ML training data locations
-- **Operations**: Monitor storage usage and data lifecycle
-
-**Key Benefits**:
-- Receive notifications about new files or partitions added
-- Track schema changes in structured files (Parquet, Avro)
-- Monitor retention policy or lifecycle rule changes
-- Get alerts for access control or governance updates
-
-**Common Use Cases**:
-- Data engineers follow production data lake containers
-- Analysts follow containers with datasets they use
-- ML engineers follow containers with training/test data
-- Compliance teams follow containers with sensitive data
-
-!!! tip "Learn More"
-    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about configuring notifications, best practices, and integration with webhooks.
+Users can follow containers to receive notifications about new files, schema changes, and retention policy updates. See **[Followers](../../metadata-specifications/followers.md)** for details.
 
 ---
 

docs/data-assets/storage/directory.md

@@ -307,29 +307,7 @@ for details on defining and using custom properties.
 
 ## Followers
 
-**Stay informed about directory changes**
-
-Followers allow users to "follow" directories and receive notifications when they change. This is helpful for:
-
-- **Team Collaboration**: Monitor shared team directories
-- **Project Management**: Track project-specific directories
-- **Data Organization**: Stay informed about organizational changes
-- **Access Control**: Monitor permission changes to directories
-
-**Key Benefits**:
-- Receive notifications about new files or subdirectories added
-- Track permission or sharing updates
-- Monitor organizational structure changes
-- Get alerts for moves, renames, or deletions
-
-**Common Use Cases**:
-- Teams follow shared project directories
-- Managers follow departmental directories
-- Collaborators follow document repositories
-- Admins follow critical system directories
-
-!!! tip "Learn More"
-    See the complete **[Followers Guide](../../core-concepts/followers.md)** for detailed information about configuring notifications, best practices, and integration with webhooks.
+Users can follow directories to receive notifications about new files, permission changes, and organizational structure updates. See **[Followers](../../metadata-specifications/followers.md)** for details.
 
 ---