Conventions
The Conventions screen is where you set up and manage the naming rules for your project. Conventions help you enforce consistent naming across tables, columns, schemas, and other elements of your data solution.
What you can do here
Section titled “What you can do here”Create and manage conventions
Section titled “Create and manage conventions”- Add new conventions that define naming patterns for your project.
- Edit existing conventions to adjust rules as your standards evolve.
- Delete conventions you no longer need.
- Browse all conventions in your project.
Define naming patterns
Section titled “Define naming patterns”Each convention captures a naming rule — for example:
- Staging tables should be prefixed with
stg_ - Hub tables should be prefixed with
hub_ - All column names should follow a specific casing pattern
- Audit columns should use a standard naming format
Why conventions matter
Section titled “Why conventions matter”When you’re managing dozens or hundreds of data objects, consistent naming makes everything easier to understand, navigate, and maintain. Conventions also work with templates — your Handlebars templates can reference conventions to generate correctly named output automatically.
For more on the concepts behind conventions, see Naming Conventions.
- Agree on standards early — It’s much easier to set up conventions at the start of a project than to rename things later.
- Keep them simple — A few clear, well-communicated rules are better than a long list of complex patterns.
- Use them in templates — Conventions are most powerful when your templates reference them to generate consistently named output.
Related
Section titled “Related”- Naming Conventions (Concepts) — Understand why conventions matter
- Classifications — Another way to organize your metadata
- Templates — Templates that can reference your conventions