> 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/high-level-concepts.md). # High-Level Concepts Before diving into the LogicNets software, it might be helpful to read through high-level explanations of some of the concepts behind it. There is more detailed information on each of these in this support center. ## Designer The Visual Designer, or Designer, is where and how you create your applications. It's your central location and toolbox for building, testing, and publishing the logicnets, data, and other resources that make up your applications. ## Projects When you want to create an application, this is where you start. A Project is basically a folder, a place where you build all of the logicnets related to an application and the central location for the data, images, and layout details that go into your completed application. ## Logicnets These are strings of steps you put together. Some of these steps are user-facing and contain text, questions, and/or images, and some of them system-facing and tell the system to save information, get information, perform a calculation, or send an email, for example. Your completed application can be one logicnet or many of them linked together. Resources Your application is more than just strings of steps -- it's images, data, and layout and styling. We group these into a category we call Resources, and when you start a project the system sets up subfolders for each category. ## Frameworks With LogicNets you can build your own applications from the ground up, but there are some functions that we know work well together. We put these together in groupings we call frameworks. Frameworks are groups of logicnets, data tables, and resources that LogicNets created to run your content and provide specific functionality. A framework does all the work of presenting your content or using data in a certain way and allows you to focus on modeling your expertise. We offer the Assessment, Support Center, WebServices, and Visual Navigation frameworks. We also offer the StarterApp framework, which includes workflow functionality. --- # 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/high-level-concepts.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.