To make your templates as dynamic as possible, Voulez supports a variety of different field types to use.
The text field is the most common field, it’s used for when you need text that is not too long.
Some examples would be names, titles, tags, etc. When using Figma templates, Text fields support different text styles.
The Textarea field is needed when text can get a bit longer, e.g. for paragraphs, snippets of code, or quotes.
When using with Figma templates, it also supports different text styles.
There are different date and time fields:
The type of field you are choosing decides what the users of your template can select in the date/time picker.
When defining a date/time field in a template, you have to specify a format which should be used. Please see the following table of which formats are supported:
Unit | Pattern | Result examples |
Era | G..GGG | AD, BC |
GGGG | Anno Domini, Before Christ | |
GGGGG | A, B | |
Calender year | y | 44, 1, 1900, 2017 |
yo | 44th, 1st, 0th, 17th | |
yy | 44, 01, 00, 17 | |
yyy | 044, 001, 1900, 2017 | |
yyyy | 0044, 0001, 1900, 2017 | |
Quarter | Q | 1, 2, 3, 4 |
Qo | 1st, 2nd, 3rd, 4th | |
01, 02, 03, 04 | ||
QQQ | Q1, Q2, Q3, Q4 | |
QQQQ | 1st quarter, 2nd quarter | |
Month | M | 1, 2, …, 12 |
Mo | 1st, 2nd, …, 12th | |
MM | 01, 02, …, 12 | |
MMM | Jan, Feb, …, Dec | |
MMMM | January, February, …, December | |
J, F, …, D | ||
Week of year | w | 1, 2, …, 53 |
wo | 1st, 2nd, …, 53th | |
ww | 01, 02, …, 53 | |
Day of month | d | 1, 2, …, 31 |
do | 1st, 2nd, …, 31st | |
dd | 01, 02, …, 31 | |
AM, PM | a..aa | AM, PM |
aaa | am, pm | |
aaaa | a.m., p.m. | |
a, p | ||
Hour [1-12] | h | 1, 2, …, 11, 12 |
ho | 1st, 2nd, …, 11th, 12th | |
hh | 01, 02, …, 11, 12 | |
Hour [0-23] | H | 0, 1, 2, …, 23 |
Ho | 0th, 1st, 2nd, …, 23rd | |
HH | 00, 01, 02, …, 23 | |
Minute | m | 0, 1, …, 59 |
mo | 0th, 1st, …, 59th | |
mm | 00, 01, …, 59 | |
Second | s | 0, 1, …, 59 |
so | 0th, 1st, …, 59th | |
00, 01, …, 59 |
Boolean fields are currently only available for web templates.
They can have one of two states: true or false, on or off. They might be useful if you have certain conditions, e.g. “show this additional information”.
A number field. Supports all numbers, currently no constraints can be defined.
List fields are currently only available for web templates.
Use a dynamic-sized list of text elements, e.g. for tags or authors.
When defining an image parameter, you have to option to also specify a fixed aspect-ratio. This way, the user has to deliberately crop their uploaded image.
If you have multiple presets for different platforms in your template it makes sense to define the image parameter for every preset itself, just so you can make sure it has the correct crop.