Eliminate the concept of pages


first of all, this is good question

the structure: block - tag - page, can offer layers of information, some small word can stay in a block, some big words can grow into a page, thus can build up something bigger, something normal, like a single building vs a community.

and a community offers the convenience of biggness … the similar blocks can stay together easily.

and also in concern of connectivity of blocks, if we say all blocks in journal pages to be tagged, those blocks in a page will not have to all tagged, as they are under the same roof ( tag, page), they enjoy a sense of connectivity by default, and some of them are free of tags, this is also mind of efficiency of tags.

if every thing flattened into blocks, at the same level, then all of them have to be tagged, and sometimes, a cluster of blocks have to share the same tags, if conjure them together into a bigger block, then the block is another form of page (in the shape of block), and might it be messy as well.

1 Like


This is a warning for everyone to stay on-topic.

  • Revisiting past arguments is fine. Spamming them is not.
  • Any off-topic comments should be posted in new threads.
    • This is a forum, so all posts should target future visitors.
    • If you prefer a chat-like experience, try discord.
  • Private messages are welcome. Public show-off is not.
    • We discuss topics, not persons.
    • Any questions on behaviors or policies should go to private messages.
  • All posts are subject to moderation, especially those failing the above.
    • Moderation is rare, so think twice if it happens to your post.

That’s a good reasoning, @baiwj . But, as @BBob will say again and again, the same thing could be done with blocks-only. Is as easy as create yourself that special blocks (the communities) using uppercase letters, for example. Or an emoji at the start of the block.

The initial proposal of this topic is asking for simplicity and freedom.

The actual structure (pages-blocks) is fine. But the all-blocks in a DB version is even better because is more flexible. And it’s proved again and again by succesful outliners like Workflowy or Tana.

Thanks @mentaloid for editing the post to clarify who said what.

None of them use references to tag blocks and their children, right? To my knowledge only Roam Research and Logseq do and they both have the concept of pages.

Anyway, wouldn’t it be better if we had the following option to treat specific blocks as pages?

It seems the team is considering narrowing the gap between pages and blocks. Adding here because this might be relevant to others interested in this thread.


Hope to remove page concept ! I think there is no need to maintain page concept anymore, especially when you query something, you should choose filter page or block or both, which introduce unnecessary operation. after eliminate page concept , refernce syntax and query elements is clear, simple, just like Tana…