Assets
What are Assets?
Assets are reusable HTML blocks stored in the Visual Experience Engine. Each asset has a name, slug, and HTML body (code). They are used in scheduled content, linked from pages, and can be targeted by device, location, or category.
Core Properties
| Property | Description |
|---|---|
| id | Unique identifier |
| name | Display name |
| slug | URL-friendly identifier (lowercase, hyphens; e.g. faq-content) |
| code | HTML body |
| status | draft or published |
| devices | Target devices: iphone, ipad, android, web |
| location | Optional location targeting |
| category | Optional category targeting |
| categoryLocation | Optional array of URLs for category/location rules |
| external | Whether the asset is external (URL-based) |
| url | External URL (when external is true) |
| schedule | Optional scheduling: startDate, endDate, persistent |
| createdAt / updatedAt | Timestamps |
How Assets Are Edited
The Assets form provides two editors for the HTML body:
- Text Editor – Rich (WYSIWYG) editor
- HTML Editor – Raw HTML code editor (mode:
html)
The Asset Name field auto-generates a slug (lowercase, spaces → hyphens).
Where Assets Are Used
| Context | Usage |
|---|---|
| Pages | A page can link to an asset via contentId; the app fetches and renders the HTML when the page is opened |
| Remote API | Published assets are available via remote-content and remote-pages APIs |
Targeting and Scheduling
- Devices – Assets can be restricted to specific devices (
iphone,ipad,android,web). - Location – Optional location string for geo or context targeting.
- Category – Optional category for catalog/merchandising targeting.
- Schedule –
startDate,endDate, andpersistent: truemeaning no end date.
External Assets
When external is true, the asset points to an external URL instead of storing HTML. The url field must be a valid URI. This is used when the actual asset lives elsewhere (e.g. third-party page).
API: Fetching Assets
Assets are fetched by:
- Page API –
remote-pagesreturns pages; a page can include linkedasset(id, name, slug, code, status). - Content API –
remote-contentcan return assets by slug or ID (when available).
Assets are returned only when published and (if scheduled) within their schedule window.
Pages vs. Assets
| Concept | Purpose |
|---|---|
| Assets | Reusable HTML blocks |
| Pages | Routes with slugs that optionally link to an asset |
A page provides the route (e.g. about-us); the asset provides the HTML to display when that page is opened.
Key Takeaway
Assets in the BILDIT Visual Experience Engine are reusable HTML blocks managed in the Assets section. Each has a name, slug, HTML body, targeting (devices, location, category), and scheduling. They are used by pages, scheduled content, and the remote APIs.