> 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/assessment-framework/assessment-framework-template-adjustable-widths.md).

# Assessment Framework Template - Adjustable Widths

In the LogicNets Assessment Framework Standard Template, we have added a feature that allows each user to customize the width of the two main panels containing the Q\&A (observation panel) and Reports (report panel) during runtime.

The user can click on the divider and slide left or right to the desired width for that session. On resuming the session later, the original widths are reinstated. Below are instructions to do the following:

* remove the sliding bar feature completely (if not required)
* adjust the default/starting section widths

### Remove the Sliding Bar Feature

In order to remove this feature, two files should be removed from the project:

1. in the */resources/layout/js* folder delete the resizer.js file
2. in the */resources/layout/css* folder delete the resizer.css file.

Don't forget to republish/reinstall for these changes to take effect for end users.

### Adjust the Default/Starting Section Widths

The widths for section3 (observation panel) and section 4 (report panel) are set on the Cascading Style Sheet (CSS) for the framework but can be overridden at the project level by the Designer User as follows.

1. (if not already present) add a custom CSS stylesheet by navigating to the /resources/layout/css folder and click NEW
2. add the following CSS

   ```
   div#section3 {width: X%;}

   div#section4 {width: Y%;}
   ```

   X and Y should sum to 100% generally (unless additional layout changes are being made). **Recommendations:** For applications where the questions and/or answer responses are very descriptive, we recommend setting X = 70% and Y = 30%. For applications with shorter Q\&A or where Help references are extensive and/or include images, we recommend setting X = 55% and Y = 45%. Try out different values and experiment to find the best balance for the content in your application.


---

# 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/assessment-framework/assessment-framework-template-adjustable-widths.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.