> 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/getting-started/logicnets-an-introduction/how-it-works-logicnets-basics.md). # How it Works: LogicNets Basics LogicNets is a visual design environment and the Designer is where you build. In the Designer you link steps together in strings called logicnets to create a logical path for your application users. Add a step, link it to other steps, and connect your steps together in a group called a logicnet. **Logicnets** A logicnet is similar to a process flow—it is a series of simple steps that you link together to provide a logical process for accomplishing a specific task or objective. You can link, combine, and reuse logicnets. **Steps** A logicnet is a group of user-facing or system-specific steps that perform all kinds of actions. * **User-facing Steps:** These steps are visible to your application users and we call them form nodes or form-part nodes. They can display images and information as well as ask questions and collect data. * **System-facing Steps:** These steps manage the data your application collects, perform calculations, and send emails, for example. They also route users through your application based on user selections or rules you create. **Frameworks** LogicNets frameworks are a collection of logicnets we created to support specific application use cases, and they simplify the work of setting up the basics of any application, including user management and data storage. They allow you to focus on modeling your specific expertise and supporting content, but you can also create an application that doesn’t use frameworks at all. Click [here](/release-9/design-considerations-and-frameworks/frameworks/general-framework-information/what-is-a-framework.md) for more information about the available frameworks. **Projects** You start all of your applications by creating a project. A project folder is where you store all of the parts that go together to make your application, including logicnets, images, documents, data, and layout/styling details. When you are ready to publish your application the system looks in the project folder and publishes all of the application parts from there. --- # 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/getting-started/logicnets-an-introduction/how-it-works-logicnets-basics.md?ask=&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.