> For the complete documentation index, see [llms.txt](https://olab4.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://olab4.gitbook.io/help/getting-started.md). # Getting started ## Basic learning design steps We have some of the basic pointers [included in our 'VP on VPs' case](https://player.olab4.net/1586/0). ### Focus on a few key points Don't try to convey too much in a single map. We find that early authors are too ambitious. Start small. You can always come back and expand it later. ### Draw your map backbone Using the Designer, you can map out a basic path in a join-the-dots fashion. Create a few nodes that contain your main points and then build from there. ### Add some content The Node editor functions like pretty much any text editor for a web page. You don't need to know HTML or fancy coding stuff. Just write what you want to say and add a few pictures. ### Play your map Once you have a few nodes (or pages) linked together, fire up the Player and see how it will look to your learners. ## Requirements Not much. A web browser, an Internet connection, and a free trial account on an OLab4 server. See the [FAQs](/help/faqs.md) for more on this. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://olab4.gitbook.io/help/getting-started.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.