Custom and Live components allow developers to create a component with HTML, CSS, and JavaScript code.
Use Custom components when the code is edited directly in Fluid Topics. Use Live components when developing locally from a local HTTP server.
Live components are for local development only. Developers cannot publish them publicly. To make a Live component available publicly, convert it to a Custom component. See Live component procedure.
There are different variants of Custom and Live components:
| Component | Edited in | Public use | Additional context |
|---|---|---|---|
| Custom | Fluid Topics | Yes | |
| Custom (page) | Fluid Topics | Yes | Has access to the current page's metadata when using pagination. |
| Custom (search) | Fluid Topics | Yes | Has access to information about the current search in a Search block component. |
| Live | Local files | No | |
| Live (page) | Local files | No | Has access to the current page's metadata when using pagination. |
| Live (search) | Local files | No | Has access to information about the current search in a Search block component. |
- As for all components, only one person at a time should edit a Custom component to avoid conflicts.
- The code for Custom components is public. Do not add credentials in a Custom component.
PORTAL_ADMIN users can only edit Custom components if an ADMIN user has disabled the Custom code toggle.
- By default, Live components do not appear in published designed pages. Developers can display Live components in published designed pages locally by adding
?version=draftat the end of a URL. - The Custom component screencast also contains information about configuring a Custom component.