Architecture Documentation for Data Architects
Use ERD diagrams with navigation and linting, data lineage tracking, schema definitions, and data lifecycle blocks for complete data architecture documentation.
Data architects focus on data models, governance, and compliance. Content Foundry provides specialised blocks that support these needs with structured, auditable documentation.
Key Blocks for Data Architects
Schema Definition Block
Embed live schema documentation:
Data Lifecycle Block
Document the journey of data entities:
Data Lifecycle Examples
ERD Diagrams
The diagram editor provides powerful ERD capabilities:
Schema Lineage
Map schema fields to their database sources:
ERD Lineage Examples
The following schemas demonstrate ERD lineage, where each field traces back to database tables and columns:
Represents a book in the library catalogue with full lineage to the Book table in the database.
Lineage Override Examples
When schemas inherit from a base schema, they can override lineage for inherited fields. These path parameter schemas extend a generic IdPathParam and override the Id field lineage:
Base schema for ID path parameters. Derived schemas override lineage for specific entities.
Graph Database Navigation
For graph database models, the editor provides:
Graph Lineage Examples
The following healthcare schemas demonstrate lineage to graph database nodes. Each field traces back to a node and property in the healthcare domain model:
Represents a patient in the healthcare system. Lineage maps to the Patient node in the healthcare graph domain model.
Notice how the EncounterId field in Diagnosis and Prescription references the Encounter node, showing relationships across the graph.
Data NFRs
Document measurable data requirements:
Data Constraints
Document data-related constraints: