With multiple large blocks on a single page, things become a little unwieldy. Just bracketing the block heading doesn’t solve this. Begin able to create a page from a block would really help in the ability to re-organize things without breaking backlinks and a lot of extra work.
1 Like
Hey, I do this on regular intervals. Right now, I create a new page by adding brackets as @mat_rhein said, shift+click to open it in sidebar and cut-paste children.
It’s a bit of a chore but infrequent enough for me that I didn’t create request.
1 Like
I’m still conflicted when to use blocks or pages. Logseq allows for block references, but arguably they are not as flexible as page references, so as a rule of thumb, I start with a block (e.g. an article I’ve read). If I find myself referring to the article from other places, I promote it to a page (and move block properties to page-properties). Is this a common workflow?
Personally, I would find it very useful to have an option to do this automatically:
- Right click on the block would allow to “promote it to a page”. The title of the page would be the first bullet in the block.
- All the block properties should be converted to page properties
- Any block reference to the block should be converted into references to the new page.
Any thoughts?
3 Likes
I also start most of my notes as blocks in a writing-inbox. After some review, I will decide if that note is worth keeping. When it is, I turn them into a page. I have done this manually in Logseq, so it would be nice to have this feature.
3 Likes
This is really an essential feature. It often happens that a block, over time, becomes important enough to merit a page status.
3 Likes
Let me add an example use case. Say you want to write a book. Make a page with blocks detailing the line of argument for each section/chapter. When this settles down, progressively change the blocks to pages (preferable with the option of keeping the original block as a reference to the newly spawed page). Voilà: a book.
Then of course we need spiffy (pandoc-aided) export to LaTeX, with references becoming clickable links in the output PDF, and so on, but that’s another topic.
4 Likes
Logseq with big pages is so slow that this will help to decompose such pages in a way that can improve the performance. My vote.
1 Like
The way I’ve seen it done in Roam, which works in Logseq too is:
If you haven’t already, create the page title and nest all the content under it.
Surround the page title with [[ ]] thus making it a page.
Go to the page: the “content” of the page will be in the references. If you want to bring the content into the page rather than leaving it in the original source then drag and drop it from the references. The page you’ve created will, by definition, be linked from the original source.
2 Likes
For me I prefer it take all sub bullet and automaticaly add it to the page. If I just whant to create a page link only i’ll use [[
Thanks for explaining, but that’s quite a long procedure, and I assume a simple command ‘Promote block to page’ should be possible.
1 Like
Agreed - it is, and promote block to a page has my vote.
It would need to handle duplicate page titles - perhaps by appending to the existing page?
Not sure how block properties would work in that instance.
What is different for page and block ?
Actually, the page and block make new user confused.
because in Workflowy or Remnote, there’s no difference between page and block.
1 Like
A Logseq page is a special kind of block. Just like blocks, it can contain other blocks. A page is special because it is directly represented by a file on local disk, either an ORG file or an MD file. So I understand.
Merging pages is one cruical feature in Roam that’s missing in Obsidian. It would be fantastic to have this functionality to fix the issue of duplicating page titles when promoting page to block as well.
1 Like
I spoke too soon. This does work well. A simple command would still be preferred, but for now, this will do! Thanks.
N.B. The page is not linked from the original page though. It’s gone.
Ah you’re right. If you drag the page title from the references it moves that too.
It really only works well if you have
- [[PAGE TITLE]]
- A heading block
- Content here
- Content here
- Content here
- A heading block
You can then drag the heading block and it’l leave the page title behind. Any other structure e.g.
- [[PAGE TITLE]]
- Content here
- Content here
you would need to drag each individual block up. Not great.
So yes - a menu item to do it would be much preferable!
3 Likes
Also, I found that selecting a number of blocks in the desktop application and dragging them from the references to the main body of the new page, only moves the first block and its children while the others are simply lost. Dangerous! Thanks to DropBox versioning, I didn’t lose any text. Inside Logseq, undo didn’t bring back the lost blocks.
7 Likes
Yes. I had that happen as well. Git to the rescue.
There is a plugin which converts a block to page which may be worth checking out https://github.com/hyrijk/logseq-plugin-block-to-page
4 Likes