# Developers - [How to contribute](https://icij.gitbook.io/datashare/developers/how-to-contribute.md): 👷‍♀️ This page is currently being written by Datashare team. - [Backend](https://icij.gitbook.io/datashare/developers/backend.md) - [API](https://icij.gitbook.io/datashare/developers/backend/api.md): The Datashare API is fully defined using the OpenAPI 3.0 specification and automatically generated after every Datashare release. - [Database Schema](https://icij.gitbook.io/datashare/developers/backend/database.md) - [Write extensions](https://icij.gitbook.io/datashare/developers/backend/write-extensions.md) - [Frontend](https://icij.gitbook.io/datashare/developers/frontend.md) - [Design System](https://icij.gitbook.io/datashare/developers/frontend/design-system.md) - [Write plugins](https://icij.gitbook.io/datashare/developers/frontend/write-plugins.md): What if you want to integrate text translations to Datashare’s interface? Or make it display tweets scraped with Twint? Ask no more: there is plugins for that! - [CLI with Tarentula](https://icij.gitbook.io/datashare/developers/introduction-to-tarentula.md): Datashare Tarentula is a powerful command-line toolbelt designed to streamline bulk operations against any Datashare instance. - [Script with Playground](https://icij.gitbook.io/datashare/developers/introduction-to-playground.md): Datashare Playground delivers a collection of Bash scripts (free of external dependencies) that streamline interaction with a Datashare instance’s Elasticsearch index and Redis queue. --- # 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://icij.gitbook.io/datashare/developers.md?ask= ``` 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.