# Cloning a block

The last block feature that we want to cover is cloning a block. Sometimes, we would like to have a block that is a variation of an existing block, so the question is – how can we “reuse” the existing one? It is done by cloning. As shown above, as part of every block there is an icon to clone the block: ![img\_54.jpg](/files/-LD6N2MaEBN7hm-g866J)

So let’s clone the Theme Block. After clicking on the “Clone” icon, we’ll get the block configuration screen. Let’s only change the name of the block and make it visible:

![img\_54.jpg](/files/-LD6N2MckTr_MaLE1mKu)

And let’s see the user side:

![img\_54.jpg](/files/-LD6N2MekOIhhA5zceMp)

As you can see on the left, both blocks are working just fine. Of course, you can make more significant changes/modifications to the cloned block.


---

# 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://xoops.gitbook.io/xoops-operations-guide/the-admin-interface/blocks/cloning-a-block.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.