> For the complete documentation index, see [llms.txt](https://helpful-places.gitbook.io/a-guide-to-dtpr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpful-places.gitbook.io/a-guide-to-dtpr/using-dtpr/design-principles.md).

# Design Principles

As a result of the research conducted in 2019 (more information on this can be found in the [Appendix](/a-guide-to-dtpr/appendix/how-dtpr-was-developed.md)), a set of design principles were established to support the ongoing development of  DPTR. These design principles also set a rationale for the shapes, colours, and approaches to accessibility used as part of the standard.&#x20;

This section will offer specific guidance for how deploy DPTR, for more information on the design rationale for the shapes and colours that make up DTPR  please consult the Appendix: Details on How DTPR was Developed.&#x20;

## DTPR Design Principles&#x20;

1. Ensure the concepts being conveyed are done simply and clearly through the icons and the information placed on signs.
2. Ensure there is a prominent way for the public to provide feedback on DTPR when it is deployed in public places in order to address variations in the acceptance of and comfort with new technologies on the part of the public.
3. As the iconography is still relatively new, ensure that it is augmented with written explanations or explanatory text accompanying the icons where appropriate.
4. Provide multiple pathways to learn more and provide feedback through physical signage, QR codes and URLS.
5. The purpose of the technology/sensor is considered more important than the type of the technology and should be prioritised in signage or other communications.
6. Information on the entities responsible for vetting and governing of the technology should always be included.
7. Information indicating if individuals can be identified through the data gathered by a technology should always be included and prioritised

DTPR is typically deployed through a digital channel and physical signage that align with the design principles outlined above. The physical signage will have pointers to the digital channel and we are providing some guidance here on how to create your own digital channel and for producing physical signage.

## Finding Resources: The Open-Source Repository

All open-source assets associated with DTPR can be found in an [open-source repository](https://github.com/Helpful-Places/dtpr/tree/main). In this repository you will find all the requisite components required to deploy DTPR including downloadable icons, guides, worksheets and this guide to the standard.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpful-places.gitbook.io/a-guide-to-dtpr/using-dtpr/design-principles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
