# HS Blueprint

> How HubSpot portals are designed.


## Pages

- [Glossary](https://hsblueprint.com/glossary/): The terms on the pattern pages. A portal is records, and the rules between them.
- [Anti-patterns](https://hsblueprint.com/anti-patterns/): They work while the portal is small. They fail when a second team, a second brand, or a second year arrives.
- [Governance](https://hsblueprint.com/governance/): Without those three, the portal collects fields. People stop filling them, and the reports keep using the empty ones.
- [Reporting](https://hsblueprint.com/reporting/): A chart cannot invent a link the records do not have. Fix the model, then draw the number.
- [Multi-brand](https://hsblueprint.com/multi/): The choice follows who must not see whom, and whether the brands share customers. It is not a preference for menus.
- [Teams and permissions](https://hsblueprint.com/permissions/): Who may see a record is a design. Super-admin is not a role you hand to a new hire so they can get unstuck.
- [Pipelines and lifecycle](https://hsblueprint.com/pipelines/): If two teams define the same stage differently, the automation will fight them and the report will argue with both.
- [Data model](https://hsblueprint.com/data-model/): The thing you are tracking either fits on a record people already open, or it deserves its own object with a labeled link.
- [Patterns](https://hsblueprint.com/patterns/): Each pattern is a decision you can hand to the next admin. A demo that only works on ten records is not a pattern.
- [Home](https://hsblueprint.com/): How HubSpot portals are actually built: data model, pipelines, permissions, and the patterns that keep a 200-user account readable.


[comment]: # (Generated by Hostinger Tools Plugin)