> For the complete documentation index, see [llms.txt](https://annarbor.worldiaday.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://annarbor.worldiaday.org/people/candice-yono.md).

# Candice Yono

<img src="https://content.gitbook.com/content/w7KdqMH0cA13S7iLAgFF/blobs/3DEAWXmTrHgQTCiMhhju/Candice_Yono.jpg" alt="Candice_Yono" height="180" width="180">

A graduate from the School of Information and School of Education, Candice is a user experience professional interested in how technology can improve student learning and educational outcomes. When not exploring educational technology topics, Candice is busy sampling lots of cheeses from across the globe; she's a cheese aficionado in the making. Other interests include all things French, travel, food blogging, and Lord of the Rings. As a student intern, Candice worked at Seelio during summer and fall 2014. Besides enjoying the awesome design and research projects on which she worked, she loved the office culture. Everyone on the team was welcoming, friendly, and hilarious. From Waffle Wednesdays to Walkies, the Seelio team definitely had a unique vibe. Going to work wasn't a dull chore, it was more like working on an exciting project with friends. Understanding how to build a unique dynamic everywhere is a pretty important skill.


---

# 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://annarbor.worldiaday.org/people/candice-yono.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.
