Features
Triage

"Extract to -> Page" option for block selection

Scenario

When writing a page, a page sometimes goes very large. So, we want to move some selected blocks into a separate page and link it into the original page as an object.

Current situation

  1. Select the block we want to extract
  2. Cut it
  3. Create new Page
  4. Paste the contents there
  5. Give the page a name
  6. Come back to original page
  7. Create a new block to link that new page on the same position as the previous page

Solution

An option in the block selection context menu and in block context menu that does all that work in a single click.

Workflow

  1. I select a block or group of block which I want to extract
  2. Right click on it to get context menu
  3. Choose Extract to > Page.
  4. Fill the name of the page, press enter.

Expected

  1. A new page is created with the selected blocks as contents.
  2. A new object block is created in place of the selected object.
  3. The name of the new page is as provided by the user in step 4.

Who is this for?

Everyone who write pages that gets very large and needs extraction into different pages.

3 Comments

Sign in to comment

K
Kaye
Kaye·about 1 hour ago(edited)

This is similar to turn block into object, except you want it to be for multiple blocks?

I would add that it'd faster to:
1. Cut the content.
2. Add a /page in the editor.
3. Add title.
4. Paste.
I'm not sure that this 'extract' feature would save many more steps in reality—just one if I count correctly.

That being said, there's a similar option in other block editors of 'move to'. I suppose its a question of how granular you want all the menu options to be. At the rate of feature requests, there will be A LOT in the menu.

AO
Alaz Oz·8 minutes ago

Yes, "move to" is the option I was referring to. Just couldn't remember those words.
And the reason why I created separate FR, for it was because in AnyType selecting objects and turn into page would create separate objects for each block. And it completely makes sense for "turn into" scenario.

What I missed was, there was a "move to" button in Anytype too that implements the feature that I requested and even better (supports moving to a pre existing page) Somehow I missed that completely while I was on Anytype.

That same "move to" feature should be in AnyTwo too. And that is my FR. (Please change it on my behalf, sorry for the trouble)

AL
Alex Lins (Bao)·about 2 hours ago

Thanks for the detailed breakdown — the workflow is clear. A few quick questions to lock down the scope:

  1. When you extract multiple blocks at once, should they all land in the new page in their original order, or do you need any grouping/nesting preserved from how they were stacked in the original?
  2. For the "object block" that replaces them — should it default to showing the new page's title, or would you want to customize its label separately (e.g., "See: Architecture Details" instead of just the page name)?
  3. If the selected blocks include nested content (e.g., a block with child blocks), does "extract" mean the whole tree moves, or just the top-level block?