> For the complete documentation index, see [llms.txt](https://choubey.gitbook.io/internals-of-deno/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://choubey.gitbook.io/internals-of-deno/foundations/4.18-whats-next.md).

# 5.18 What's next

And that concludes our overview of how a program operates within the Deno environment. We've journeyed from the starting point to the finish line, covering the essential steps along the way.

This initial example marked our first foray into Deno, and while it may have been straightforward, its simplicity proved incredibly valuable in grasping the fundamental concepts. By sidestepping the intricacies of more complex user programs, we were able to focus on building a solid foundation of understanding.

Now that we've grasped the fundamentals, we're ready to move forward. Next, we'll explore a simple program that introduces an asynchronous event triggered by a timer.&#x20;

In the next chapter of this book, we'll examine a program that incorporates various imports and operations. This will further enhance our understanding of Deno's capabilities and demonstrate how to effectively leverage its features.


---

# 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://choubey.gitbook.io/internals-of-deno/foundations/4.18-whats-next.md?ask=<question>&goal=<endgoal>
```

`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.
