> For the complete documentation index, see [llms.txt](https://inclusivity.toolkit.citiobs.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inclusivity.toolkit.citiobs.eu/dialogue/how-can-we-engage-with-the-lnob-pledge/lnob-workshop-slide-deck.md).
# LNOB Workshop Slide Deck
The CitiObs LNOB Workshop materials introducing the pledge to "Leave No One Behind' and the concepts of Justice, Equity, Diversity and Inclusion (JEDI) take the form of a slide presentation, along with interactivity materials, and guidance for the use of both with key stakeholders at different stages of the CO lifecycle.
As we develop this slide deck, we have been creating made-to-measure versions for workshops with our Frontrunner Cases, to test their contents in our own reflections sessions.
These interim versions can be found in the CitiObs Zenodo repository:
* [The LNOB workshop with the Dublin-based front runner cases](https://zenodo.org/records/13919897) - October 2024
* [The LNOB workshop at the SciVil citizen science network day](https://zenodo.org/records/13896021) - October 2024
* [The LNOB mentoring workshop with front-runner cases](https://zenodo.org/records/17680335) - June 2025
The final version of these slides will be uploaded to Zenodo and contained in the LNOB Toolkit and CitiObs Cookbook.
Slidedeck of the LNOB workshop
---
# 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://inclusivity.toolkit.citiobs.eu/dialogue/how-can-we-engage-with-the-lnob-pledge/lnob-workshop-slide-deck.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.
