Templates
Most App Builder projects start from a template: a production-ready application that already works. A template is not an empty page. It ships with a map, wired-up controls and clean code, so you begin from something running and shape it from there.
The two other doors, turning a web map into an app and duplicating one of your projects, are on What is the App Builder.
The templates
Section titled “The templates”| Template | What it gives you |
|---|---|
| Blank | The full ALIGN map runtime with no pre-placed widgets and no preset layout. Start from your own design. |
| Fullscreen Foldable | A map-centric layout with a header, map controls, a foldable context panel and a widget catalogue already wired. |
A template that is not ready to use yet is shown in the gallery marked Coming soon, and cannot be selected.
Choosing the map library
Section titled “Choosing the map library”ALIGN templates are not tied to one mapping stack. A template declares the map libraries it supports, and you pick the one your project runs on from the Stack & SDK panel of the template’s page, before you create the project.
Fullscreen Foldable runs on MapLibre GL, Mapbox, MapTiler or Leaflet. Blank runs on MapLibre GL. In both cases MapLibre GL, the open map runtime, is the default, and a library your organization cannot use is shown but not selectable.
This keeps your app portable: your data, your widgets and your code do not depend on a single vendor’s map engine. If you pick a library that needs a provider key, see Integrations.
What a template gives you
Section titled “What a template gives you”When you create a project from a template, you get:
- a working map, centered and styled sensibly,
- widgets you can configure without code,
- map controls already placed,
- and a real project structure you and the AI Builder can extend.
From here, open the Interface overview to see where everything lives, or head straight to Working with the AI Builder.