# Overview

So you've got a handle on how to integrate PLAY's SDKs into your game's code - but what about the in-game side of integration? All of PLAY's modules have been deployed live and undergone analytics-driven tuning to determine the most effective ways to implement the features in-game.&#x20;

This section of PLAY's documentation is devoted to sharing these learnings and best practices for Web3 integration with you. A companion Game Design Guide is available for each of our modules that will provide you with examples of in-game UI/UX + illustrate various ways you can modify each module's in-game behaviour to suit your needs!&#x20;

We hope that these Game Design Guides (to be referred to as GDG in the rest of the documentation) will help you save some time in planning your next Web3 feature integration, or spark some inspiration for the latest GDD you are working on!&#x20;


---

# 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://playnetwork.gitbook.io/play-sdk-documentation/game-design-guides/overview.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.
