# Alpaco Developer Documentation

## Alpaco Developer Documentation

- [Introduction](https://documentation.alpaco.email/introduction.md): This documentation is for developers/designers of HTML templates. If you are a marketeer / email content creator, please refer to the Fundamentals.
- [What are the fundamentals](https://documentation.alpaco.email/fundamentals/what-are-the-fundamentals.md): In this section we'll go over what are the fundamentals to understand before you get going with setting up your organization in Alpaco.
- [Creating an email](https://documentation.alpaco.email/fundamentals/creating-an-email.md): In this section we'll go over how you actually get started with creating an email when all have been setup correctly with Base, Blocks, Merge Tags and Integrations
- [Base](https://documentation.alpaco.email/template/base.md): Alpaco is much more than a email builder, HTML or CSS, it's a way to systemize and manage your brand, design rules, data-integrations, languages, all those small details needed for an email template.
- [Blocks](https://documentation.alpaco.email/template/blocks.md): If Base is the foundation of a template, Blocks are the building-blocks to build up your template. It's individual modules you can have infinite of.
- [Input Groups](https://documentation.alpaco.email/template/input-groups.md): If Blocks are the building-blocks the template is build on, Inputs are the mortar. This is where your settings and rules are defined and the key part of what separates Alpaco from other email editors.
- [Input Types](https://documentation.alpaco.email/template/input-groups/input-types.md): In Alpaco you can have many different input types, separated or grouped together to form sets of settings.
- [Text String](https://documentation.alpaco.email/template/input-groups/input-types/text-string.md): A simple text string, single line that can be used for settings where users only can insert one line of text
- [Textarea](https://documentation.alpaco.email/template/input-groups/input-types/textarea.md): Textarea are more refined compared to Text String and can be used for when you want to allow for multiple lines of text, but also open up for rich-text options
- [Select](https://documentation.alpaco.email/template/input-groups/input-types/select.md): Select inputs are used for when you want to give the user options to choose from.
- [Boolean](https://documentation.alpaco.email/template/input-groups/input-types/boolean.md): A Boolean is used for when you want something to be either true or false, like a lighting switch that can be toggled on or off
- [Image](https://documentation.alpaco.email/template/input-groups/input-types/image.md): Images are a fundamental part of an email, that's why we've built this feature with deep setting possibilities to take care of all scenarios that you would need
- [Image settings](https://documentation.alpaco.email/template/input-groups/input-types/image/image-settings.md): Image settings are the powerful features that enables you to model, filter, rotate, resize and expand on what your template needs to ensure those images looks just right, each time - without Photoshop
- [Color Picker](https://documentation.alpaco.email/template/input-groups/input-types/color-picker.md): Unlike Select, where you can create things like themes that will alter your entire color palate, Color Picker is meant for when you want to give users a color wheel to pick any color manually
- [Code](https://documentation.alpaco.email/template/input-groups/input-types/code.md): An input field, unlike Text String, that can be used for specific scenarios where users needs to input elaborate pieces of code
- [Integrations](https://documentation.alpaco.email/account-settings/integrations.md): Integrations are what makes Alpaco connect with your existing Email Platform, and enables it to send over your creation to the platform, so you can send it ou
- [Merge Tags](https://documentation.alpaco.email/account-settings/merge-tags.md)
- [REST API](https://documentation.alpaco.email/account-settings/rest-api.md): The Alpaco REST API allows you to programmatically inspect workspaces, compile designs, and push finalized email assets directly to your external distribution channels.
- [Subject line & Preheader](https://documentation.alpaco.email/how-to/subject-line-and-preheader.md): Subject line & preheaders are a natural part of email marketing, it's the first thingbut the way it's handled and supported by the various ESP's are different
- [Escape code from the editor](https://documentation.alpaco.email/how-to/escape-code-from-the-editor.md): Sometimes you want to display something for the editor, but have some other code executed on export, or sometimes you just want the code editor to leave your delicate ESP specific variables alone
- [Use custom fonts](https://documentation.alpaco.email/how-to/use-custom-fonts.md): Here we'll describe how you can add custom fonts to your email campaigns and start making use of them
- [AMP](https://documentation.alpaco.email/how-to/amp.md): AMP for email stands for Accelerated Mobile Pages for email and is the ability to add immersive interactions to your email. It's usually paired up with a fallback versions for non-amp inboxes


---

# 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, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on a page URL with the `ask` query parameter:
```
GET https://documentation.alpaco.email/introduction.md?ask=<question>
```
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.
