For example, here when you click on 7flash/gitmaps repo, it opens default layout, showing all of the files in grid on the same layer. Then, you can select "All API Routes" and move them to separate "api" layer, organize other files on the board as convenient for you personally.
Here's where advantage of transclusion mechanic shines clearly: other members of your team can clone the same repo but organize its files in their own layout, however its convenient to each individual, yet when new commits arrive, it will not break their layout, - but will highlight file changes from their individual perspective. This is truly game changer for knowledge exploration, collaborative work, and agentic assistance.
Watch full demo or try it with your own repo:
If you want to put the same document in several folders on your physical table, it's impossible unless you make a copy and then do so.
There's no such limitation in digital space, yet both local file system and the internet have inhereted it's logical flaw from legacy way of thinking.
Transclusion allows to transcend this limitation and organize files in rather creative ways across layers of abstractions and synchronize different perspectives within your team.