Input Types
In Alpaco you can have many different input types, separated or grouped together to form sets of settings.
These are the current allowed Input Types:
- A single line of text with no formatting options.
- Multi-line text input with simple formatting options.
- Link validator w. tracking
- Select/Dropdown of predefined values.
- On/off toggle/switch.
- Image upload or URL input.
- Color picking wheel w/ eyedrop tool.
- Ability to insert raw code.
How to get started?
Simply open up your Base or Block, depending on where you want your input, navigate to the Right panel, click the button called "Add input" and select your input type from the dropdown. Just like with Input Groups, the Name and Key needs to be inserted and given a proper name.

Validate Inputs
Validating inputs and give warnings is an essential part of handing over your template to others users. By using validation rules you can add clarity to what the intended use for an input should be. All Input types have a dropdown option in the Template Editor where multiple validation rules can be added and they all come with an option to make a Custom Error Message per validation rule, for each input field.

If an input is not validated in the Email Editor, the user will be informed of the error, taken to where the error is, have the error highlighted and prevented from saving the email before adhering to the specific input requirement.

Required field
This field must be blank
Must Not Be Default
This field must not be indentical to the default content
Regex
Define any form of regular expression you want. Be that URL, numbers, wordings ect.
Show or hide
When building your Email Design system, over time it can become very crowded with fields and options for the users to fill in. However many times fields are dependent on each other, and is useless without the other - in these cases you want to hide those uncessary fields. That's where the if/unless field come in handy on Inputs. You'll be able to hide or show any input types by typing in a liquid condition in accompanying if/unless field. The liquid condition could be coming either internally from the Block or even from Cross reference inputs.

The syntax is a bit deconstructed in so far as you're not suppose to write the entire liquid statement with the proper opening and closing tag, eg. {%if *YOUR STATEMENT*%}{%endif %} as the platform will be doing that for you. Simply type in the liquid condition however complex you may need. You're able to use if or unless as your initial condition.
Last updated