# Introduction

Throughout the years at Embrace - The Human Cloud, the Product team has made important design decisions. The goal of this documentation is to refer to these decisions. The documentation is focused on user experience - not on the specifics for the UI, which may alter more quickly over time.

{% hint style="info" %}
This documentation is meant to document **design decisions.** Looking for developer handoff documentation? See Documentation in Figma. 
{% endhint %}

### Quick links

{% content-ref url="/pages/2uFrVVsQRh3dINKZU4U7" %}
[Principles](/foundation/principles.md)
{% endcontent-ref %}

### What's documented here

This documentation covers design patterns, workflows and decisions for the Embrace Suite software, specifically:

* Digital collaboration
* Digital services

### Who is this for

The primary audience exists of:

* Product Designers joining or continuining work on the Embrace Suite
* Product Managers planning new features
* Developers implementing user-facing features

Also suited for:

* Stakeholders wanting to understand design rationale
* Anyone curious about how we approach UX at Embrace

### Scope and boundaries

What's included:

* Patterns and workflows specific for the Suite
* Design decisions made forwards from 2020
* Context on user needs per product

What's not included:

* Embrace Brand Guidelines: see the [Brand Guide](https://branding.embracecloud.nl/)
* Development implementation specifications: see Figma Documentation


---

# Agent Instructions: 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:

```
GET https://design.embracecloud.nl/getting-started/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.