The Landing Page Builder includes asset functions for working with images as well as supporting icon and font selection workflows.
Assets should be managed deliberately because a visual page can depend on the same uploaded file in more than one location.
The GrapesJS Builder includes an Asset Manager used to work with available page images.
The confirmed user Builder is configured for a single uploaded file per upload operation rather than multi-file upload.
The Landing Page image-upload controller accepts the following formats:
The confirmed upload validation uses a maximum value of 20,000 KB.
A file must also pass the application's supported image-type validation.
If the uploaded Builder file does not satisfy the accepted image format validation, the current endpoint can report:
The file must be an jpg,jpeg,png,svg
Uploaded Landing Page Builder images are stored in a public storage location associated with the authenticated user's ID.
This separates the normal user Builder's image-storage location by user account.
After an upload succeeds, the application returns the resulting public image URL to the Builder so the image can be used as a page asset.
The current user upload controller preserves the uploaded file's original filename when placing it into the user's storage location.
As a practical best practice, give important campaign images clear and unique filenames before uploading them. This reduces the risk of confusing similarly named assets and makes later asset review easier.
When adding images, consider both visual presentation and the function of the page.
Before launch, verify that:
The Builder listens for supported asset-removal actions.
When an image is removed through that workflow, the Builder sends the image source to the Landing Page image-deletion endpoint.
The controller extracts the image filename and, when a matching file exists in the authenticated user's storage location, deletes that file.
Asset caution: Do not remove an uploaded image from the Asset Manager if another part of the Landing Page still depends on that physical file.
Removing an image component from one location in the page design and deleting the underlying uploaded asset are not necessarily the same action.
If an uploaded file is reused elsewhere, deleting the physical asset can affect every place that still references its URL.
Before removing an asset, inspect both the Main Page and Thank You Page when the same file may have been reused.
AIUNIFY Funnels provides an icon-search function for the Builder.
When a keyword is supplied, the application searches its configured icon list for values matching that keyword and returns the matching icon elements for use by the interface.
When no keyword is supplied, the endpoint can return the configured icon list for browsing.
Use icons as visual support rather than as a substitute for essential information that a visitor must understand.
After selecting an icon, review its visibility against the selected background and confirm that it remains understandable on the page sizes important to your audience.
The Landing Page system also includes a font-search workflow backed by its bundled Google Font data.
The font-search function looks for font families matching the supplied search value so the user can locate available font choices more efficiently.
Landing Pages maintain a current font setting as part of their Landing Page configuration. A newly created Landing Page is initialized with Open Sans in the confirmed creation workflow.
Detailed Landing Page font configuration is covered in Chapter 28.
The visual page's saved HTML, Components, and CSS can contain references to the assets used during editing.
That means asset management and page-content management should be treated as connected tasks. Removing an asset without reviewing the page can leave a visual area pointing to content that is no longer available.
When replacing an important campaign image:
Because the Main Page and Thank You Page maintain separate page content, review both when cleaning up campaign assets.
An image that appears unused on the Main Page may still be required by the Thank You Page.
Operating principle: Treat uploaded assets as dependencies of the page. Replace references first, verify the public result, and delete the old physical asset only when it is no longer needed.