```yaml
id: getting_started
namespace: company.team
tasks:
- id: hello_world
type: io.kestra.plugin.core.log.Log
message: Hello World!
```
The supported languages for code blocks are fully listed in the `useShiki.ts` file in the repository, and if you need something new added, you can make an addition there.
### How to use images
Images are a key part of the documentation. We couple images used on a page within the page directory. The Apps documentation markdown page and its associated images are contained in the same folder to keep assets together and to make them easy to find and add. Taking this guide as an example, an image we used earlier in the guide appears in the markdown as follows:
```markdown
```
The image has a clear title and is located in the Apps folder. For this guide, all images are placed in this folder path so the organization is clear and easily worked with by another contributor. This same practice is used for our blog and other parts of the website that are kept in the repository.
## Contribute to Kestra Plugin Documentation
Kestra Plugins each have their own documentation page on the website in [Plugins](/plugins). Each plugin also has in-app contextual documentation so that task and property definitions are easily usable while building flows. Plugin docs are maintained in separate repositories rather than the product documentation.
For example, if you want to contribute to the [OpenAI Plugin](/plugins/plugin-openai), you can find the documentation in the [OpenAI Plugin Repository](https://github.com/kestra-io/plugin-openai).
:::alert{type="info"}
All plugin repos are searchable from the central [Kestra GitHub](https://github.com/kestra-io). The name of the repository is in the URL of the plugin documentation page. For example, the OpenAI repo is called `plugin-openai`, which is in the URL path `https://kestra.io/plugins/plugin-openai/io.kestra.plugin.openai.chatcompletion`. Searching the tool's name should suffice, but this always works as a fallback.
:::
To contribute to a plugin's documentation, fork the repository. Once cloned, contributions are welcome to four key components of plugin task documentation: title, description, examples, and properties.
Continuing with [OpenAI](/plugins/plugin-openai), the tasks include [ChatCompletion](/plugins/plugin-openai/io.kestra.plugin.openai.chatcompletion) and [CreateImage](/plugins/plugin-openai/io.kestra.plugin.openai.createimage).
Each task is in the path `src/main/java/io/kestra/plugin/openai`. This will be similar to all other plugins (i.e., `src/main/java/io/kestra/plugin/Send a message to Kestra
Send a message to Kestra
Execution ID: {responseData.id}
} ``` In this case, `id` is the Execution ID of the Execution that was started because of the webhook request. Now we've added the response, our full `App.js` should look like this now: ```js import React, { useState } from 'react'; import axios from 'axios'; import './App.css'; function App() { const [formData, setFormData] = useState({}); const [responseData, setResponseData] = useState({}); const handleSubmit = async (e) => { e.preventDefault(); try { await axios.post('http://localhost:8080/api/v1/main/executions/webhook/company.team/webhook_example/abcdefg', formData).then(response => { setResponseData(response.data) }); } catch (error) { console.error('Error:', error); } }; const handleChange = (e) => { setFormData({ ...formData, [e.target.name]: e.target.value }); }; return (Send a message to Kestra
{responseData.id &&Execution ID: {responseData.id}
}