> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/developers/integrations/guides/save-editable-block-content.md).

# Save editable block content

This guide builds a block with editable text and a button. The button saves the current text to the block properties.

### Before you start

You need a local integration project. Follow the [integration quickstart](/docs/developers/integrations/quickstart.md) before continuing.

### Add the component

In your integration entry file, create and register the component:

```typescript
import { createComponent, createIntegration } from '@gitbook/runtime';

const editableContent = createComponent({
  componentId: 'editable-content',
  render: async (element) => (
    <block>
      <textinput
        state="content"
        initialValue={element.props.content}
        label="Content"
      />
      <button
        label="Save content"
        onPress={{
          action: '@editor.node.updateProps',
          props: {
            content: element.dynamicState('content')
          }
        }}
      />
    </block>
  )
});

export default createIntegration({
  components: [editableContent]
});
```

The input keeps its working value in component state. `@editor.node.updateProps` stores that value in the editor node properties.

### Add the block to your manifest

In `gitbook-manifest.yaml`, add the block to the `blocks` list:

```yaml
title: My integration
blocks:
  - id: editable-content
    title: Editable content
```

The manifest block ID must match `componentId`.

### Test the block

1. Start your integration with the development command.
2. Insert **Editable content** from the inline palette.
3. Enter text and select **Save content**.

The block saves the input value as its `content` property.

### Next steps

Use the [text input](/docs/developers/integrations/development/contentkit/reference.md#text-input) and [button](/docs/developers/integrations/development/contentkit/reference.md#button) references to build richer editor interactions.


---

# 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://gitbook.com/docs/developers/integrations/guides/save-editable-block-content.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.