> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/application-starter-framework/custom-screen-layout-and-structure.md).

# Custom Screen Layout and Structure

## Description

LogicNets provides standard layout templates in each framework. However, if the standard layout with the predefined frameset does not fit your needs, you can define your own layout for your Starter Application.

Note that creating a custom layout requires advanced knowledge of general website development and how it ties in with the LogicNets frameworks. For minor changes, e.g. displaying an alternative browser tab text, it is easy to edit the default template. For more detailed changes, we recommend you request professional services from LogicNets to support you.

## Add Your Custom Layout

Please follow the following steps to add your custom layout to your Portal Application

**Step 1.** Create an HTML layout file and add it to your project in the *resources/layout* folder. When you created your Starter Application from a template, the system created a custom\_layout template in your layout folder that you can customize.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-c70e70121013af1003322cb9d68efd54c01e80ec%2F5ed1b9b9-7587-458d-8f4f-949bf5a6a8d0.png?alt=media)

Pay special attention to the token containers, these must formatted as follows:

```
<div id="section1" class="section">
          <script type="text/javascript">
                 ajax.initialize_div('[[$sself]]', 'section1', { _token: 1, verb: 'force_step_nofp' });
          </script>
</div>
```

**Step 2.** In your project settings refer to the custom template layout template. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-c497187975edde6ab8ace57f9e9df40403a2b06d%2F8a19d8f2-1aa0-4012-99c5-d7774953cd97.png?alt=media)

**Step 3.** In your framework settings, specify the tokens and associate each with the logicnets that you want to load in the tokens. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-a9be1528902d43ff7892aaf19c579c2371f0e689%2F4104ee78-dd5c-4e73-a0ad-f309bd319f86.jpg?alt=media)

## Example

Download and import the following [example](/release-9/example-gallery/example-projects-for-parts/starter-app-custom-layout-example-project.md) of a project with custom layout.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/application-starter-framework/custom-screen-layout-and-structure.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.