Components and Model Marketplace
Component sources, Model Marketplace, downloads, and safe placement.
Understand component sources, browse and filter the Model Marketplace, download models, and place them safely on a page.
A component is a reusable piece of a page. The editor may also call it a block, model, or section. Examples include a hero, feature grid, pricing comparison, FAQ, testimonial group, or call to action.
Component sources
| Source | What it contains |
|---|---|
| Built-in Blocks | Components already shipped with the editor |
| Official | Models published by the PageDesigner library |
| AI-made | Models identified as AI-created |
| Community | Models shared through the broader library |
| Installed | Hosted models already downloaded into the local cache |
| Saved Components | Snapshots saved from your own canvas |
| Custom Components | Forked or hand-prepared HTML stored locally |
| Shared Components | Components imported from a share link or UID |
Placing a component creates a page copy. Changing the page copy does not rewrite the library source.
Open the Model Marketplace
- Open Blocks in the left panel.
- Select the plus action in the panel heading.
- The Model Marketplace opens.
The marketplace search matches model names, categories, and tags.
Filters
- All models — every available result.
- Official — the PageDesigner collection.
- AI-made — models tagged as AI-generated.
- Community — community-shared models.
- Installed — models already available in the local cache.
Use Refresh to request the current manifest. When Hosted cannot be reached, PageDesigner can show downloaded cached components and reports that the hosted connection is unavailable.
Download, add, and cache states
The action on a card depends on local state:
- Download fetches and verifies the model payload, then saves it in the local cache.
- Add makes an available model usable in the current Blocks panel or places it as the UI indicates.
- In library means the model is already available.
- Cache identifies a local cached source when Hosted is not the current source.
Downloaded content is verified before it is cached. If verification fails, do not attempt to bypass it with copied unknown HTML.
Place a model on the canvas
- Download or add the model.
- Close the marketplace.
- Find it in Blocks.
- Drag it to the intended position.
- Select it.
- Replace all example content.
- Check desktop, tablet, and mobile.
- Test interactions in Preview.
Choose models deliberately
Before adding a model, ask:
- Does it help the page's main goal?
- Does its information structure fit the content?
- Does it match nearby sections?
- Can it be reduced to the amount of content you actually have?
- Does it require an interactive library that the active theme has not enabled?
The most visually elaborate model is not automatically the best model.
Understand hosted updates
The hosted manifest can report a newer version for a reusable cached component.
- An update to the reusable cache does not rewrite a component already placed on a page.
- Existing pages therefore remain stable.
- To use the new version, add the refreshed reusable model and deliberately migrate your content.
- Auto-update downloaded library cache affects the reusable template only.
Empty or incomplete results
If the list looks empty:
- Clear the search.
- Switch to All models.
- Select Refresh.
- Check whether the status says Hosted is connected or only the local cache is available.
- Confirm your role has hosted-library view/download permissions.
- Confirm the license is active.
- Review diagnostics and application logs if the request failed.
Interactive models
Some accordions, tabs, carousels, and other enhanced components can use optional FlyonUI/Iconify theme integration.
Always:
- test interactive mode on the canvas;
- test full Preview;
- test the public page after publishing;
- verify keyboard and touch behavior;
- confirm the active theme contains any optional frontend integration the model expects.
Marketplace safety
- Replace all sample copy, images, links, prices, and IDs.
- Do not paste credentials or private customer content into a model.
- Verify the rights for media and copy.
- Check external requests and embeds.
- Prefer official or reviewed sources.
- Treat uploaded custom HTML as code.
- Never add scripts or inline event handlers through canvas HTML.
When to save, fork, or share
| Goal | Action |
|---|---|
| Reuse the exact selected page section locally | Save as Block |
| Create a permanently customized reusable model | Fork, edit the downloaded HTML, then Upload |
| Send one component to another installation | Share Component |
| Receive a shared component | Import Component |
Continue with Reuse, fork, and share components.