> For the complete documentation index, see [llms.txt](https://developers.newbluefx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.newbluefx.com/api-examples/sample-controllers-tour/08-vue-example-weather-report.md).

# Vue Example - Weather Report

Up to this point, all examples are written in plain JavaScript without the use of any frameworks.

This example uses [Vue](https://vuejs.org/), a popular framework for building user interfaces. It builds on top of standard HTML, CSS and JavaScript and helps you efficiently develop user interfaces. It is well suited for the style of simple interfaces required for controllers. Keeping things simple, Vue apps will run from Captivate’s file server, so there is no need to set up a more sophisticated server of your own.

This example offers a simple weather report tool.

<figure><img src="https://2284285836-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXkMvk0MrY3BcyplZ0pf7%2Fuploads%2FQn36qa6Dr6yheOqU4JnA%2Fdownload-7.png?alt=media&amp;token=3ef713ef-7172-4179-93bb-0f78e1b65f8d" alt=""><figcaption></figcaption></figure>

This provides a great working example for both building with Vue and using the National Weather Service APIs to capture weather data.


---

# 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://developers.newbluefx.com/api-examples/sample-controllers-tour/08-vue-example-weather-report.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.