> 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/visual-navigation-framework/visual-navigation-framework-overview.md).

# Visual Navigation Framework Overview

With LogicNets, you connect individual steps together in a process flow to create applications and then you assign a layout template and style sheets, and many LogicNets-based applications look much different to the end-users in the published version than they do to the designers who created the flows.

As with other LogicNets frameworks, the *Visual Navigation* framework controls the way logicnets and associated content displays to users in published applications. However, with the Visual Navigation framework users see and interact with the actual graphical flowchart of each logicnet. As a user moves through the application, the system highlights selected options and affected pathways and the user is able to see the path they took to get to a particular step or outcome.

The Visual Navigation framework offers two display options for published applications: the Algorithm View and the Side-by-Side View.

## Algorithm View

The Algorithm View takes published applications that are based on the Visual Navigation framework and displays to the user the nodes and the pathways containing the questions and content. This allows the user to see the path he has taken, back up to a previous node, and then move forward in the same path or along another path.

## Side-by-Side View

The Visual Navigation also has the ability to display the full text of a node on the side of the screen in addition to displaying the algorithm view. This is called the Side-by-Side View. Here is an example of the project displaying a text panel in the side-by-side view:

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-086a32c2c1174736867bfb7ef3664ed48fc0f1d9%2F078c1f06-49e7-4959-ac5f-de944744c3c3.jpg?alt=media)

## Create and Configure a Visual Navigation Project

To create and configure a project based on the Visual Navigation framework, see [Create a Visual Navigation Framework Project](/release-9/design-considerations-and-frameworks/frameworks/visual-navigation-framework/create-a-visual-navigation-framework-project.md).

## Example Project

To help you get started with the Visual Navigation framework we have created a sample project and instructions on how to create it [here](/release-9/design-considerations-and-frameworks/frameworks/visual-navigation-framework/visual-navigation-example-project.md).


---

# 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/visual-navigation-framework/visual-navigation-framework-overview.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.