Custom

Client-side pages run in the user's browser. They are best suited to building interactive application frontends with HTML, CSS, and JavaScript.

What client-side pages can use

• Browser APIs such as DOM manipulation, events, and network requests.
• MODLR custom page tags that inject values into the page.
• Reusable HTML includes for shared layouts and styling.
• script blocks with runat="server" for server-generated template context.
• Runtime-specific helpers such as ServerClient.

What client-side pages cannot use

Client-side pages do not run process functions directly. If logic must run on the server, use a server-side page or a process.

Custom pages can also include script blocks with runat="server" when server-side logic is needed during template rendering.

Custom page tags

Variable

Retrieve the value from a model variable such as brand.Logo.

<a target="_top" href="/home/"><img src="<!--variable:brand.Logo-->" alt="Logo"></a>

Include

Include another custom HTML page. This is commonly used for shared navigation or styles.

<!--include:inc.Style-->

Tag

Control page content with access tags.

<!--tag:admin-->
<!--include:inc.adminNavigation-->
<!--tag:else-->
<!--include:inc.publicNavigation-->
<!--tagend-->

User

Fetch information about the current user.

<!--user:name-->
<!--user:id-->
<!--user:email-->
<!--user:phone-->

Model

Retrieve information about the current model.

<!--model:id-->
<!--model:name-->

Application

Retrieve information about the current application.

<!--application:id-->
<!--application:name-->
<!--application:route-->

Related pages

• See Client-side Available Functions for client-side runtime helpers.
• See Server Template Blocks for runat="server" block usage.
• See ServerClient for the ServerClient API.
• See serverside (Deprecated) for the deprecated serverside helper.