> For the complete documentation index, see [llms.txt](https://upskilling.stacs.scot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upskilling.stacs.scot/upskl-site-home.md).

# UPSKL site home

A collection of tutorial recordings and other materials for teachers of Computing in Scotland

<h2 align="center">Welcome to STACS Up-Skilling</h2>

{% columns %}
{% column %}
{% hint style="success" %}

#### Get started!

* Find advice on key messages from course reports.
* Get to grips with ideas for summative and formative assessment.
* Explore approaches for CS in EY, Primary and BGE.
* Revisit or catch up on STACS events.
  {% endhint %}
  {% endcolumn %}

{% column %}
{% hint style="info" %}

## Navigation

* Use the [<mark style="background-color:yellow;">top of page menu</mark>](#user-content-fn-1)[^1] for main section groups
* Use the [<mark style="background-color:yellow;">side-bar menu</mark>](#user-content-fn-2)[^2] for section pages
  {% endhint %}
  {% endcolumn %}

{% column %}
{% hint style="warning" %}

<h3 align="center">Don't forget to sign up!</h3>

<p align="center"><a href="https://connected.stacs.scot/" class="button primary" data-icon="people-group">Join the community at STACS connected</a></p>

<p align="center"><a href="https://www.stacs.scot/" class="button primary" data-icon="globe-pointer">Register for news and resources at STACS.scot</a></p>
{% endhint %}
{% endcolumn %}
{% endcolumns %}

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>How to use and navigate this site.</strong></td><td><a href="https://309569013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWPMGvhkk1FfevYyuMr49%2Fuploads%2FWyAUVJehXaxYhxW7vmkH%2FAbout%20Us%404x.png?alt=media&amp;token=efc3095f-5da5-4d80-95fa-d3d7450ee858">About Us@4x.png</a></td><td><a href="/site-appendices/about-the-site.md">About the site</a></td></tr><tr><td><strong>Browse the site Content Map</strong></td><td><a href="https://309569013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWPMGvhkk1FfevYyuMr49%2Fuploads%2Fb13wg0OCFbfPJzAZGIh1%2FMap%404x.png?alt=media&amp;token=90e3f50e-7712-4533-8239-466438911056">Map@4x.png</a></td><td><a href="/site-appendices/site-map.md">Site map</a></td></tr><tr><td><strong>YouTube and Spotify</strong></td><td><a href="https://309569013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWPMGvhkk1FfevYyuMr49%2Fuploads%2FOmXctUGii7Tnx2N3NuKa%2FVideo%404x.png?alt=media&amp;token=56fc63b4-22e6-4e38-ae19-93743cd696be">Video@4x.png</a></td><td></td></tr></tbody></table>

[^1]: Scroll L <-> R and drop down

[^2]: visible on section pages


---

# 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://upskilling.stacs.scot/upskl-site-home.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.
