> For the complete documentation index, see [llms.txt](https://docs.bird.com/taxi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/taxi/email-design-systems/brands/what-are-brands.md). # What are Brands {% embed url="" %} \* Sub-templates are now Brands *Music:* [*https://www.bensound.com/royalty-free-music*](https://www.bensound.com/royalty-free-music) Brands previously known as Sub-templates are children of your Email Design System which allow you to create multiple branded Email Design Systems all from the same code base. This means you can create Email Design Systems for multiple brands and products without any HTML knowledge and any updates or fixes to the HTML will apply to all Brands.\ \ For each Email Design System, you can set design defaults such as logos, colours, CTA styles etc. or content defaults such as footer text or the navigation. This means when you're creating your emails all of this will be set automatically, saving you from doing it manually each time. Below is a diagram of two Brands created from one Email Design System. ![](https://downloads.intercomcdn.com/i/o/159536248/ded56a87aa8bac97f8ff1dfe/Subtemplate+%281%29.png) Read Next:\ [Creating a Brand](https://docs.messagebird.com/taxi/Email%20Design%20Systems/Brands/creating-a-brand)



--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.bird.com/taxi/email-design-systems/brands/what-are-brands.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.