A Tree-object for hierarchical navigation

[HelenaGwyn]

As referenced in Layout as a Type with templates I would like a Tree-object.

Although the graph is amazing, a hierarchy or tree might come in handy as well. An object could be linked to or used in multiple tree-objects. You would also have to state which object is the parent (the tree or some other object within the tree).

You could use a tree-object as a table of contents on a page. This could be created automatically based upon the headings. You could use a tree-object in navigation. I don’t know how the upcoming sidebar is going to be implemented, but it could be/contain a set of tree-objects you can manually create and adjust.

If we can start publishing objects to the internet, linked to a certain domain, a tree-object could be linked to custom anytype-url (as it is done in notion) or you could attach your own domainname to the tree. The root would be f.e. www.domain.ext. Every object referenced in the tree would become www.domain.ext/object-slug/… .

[forgettable]

See if these request do not already concern what you are talking about.

Side panel with relations in opened object

Describe the solution you’d like There is a suggestion. And what if the relationship is displayed in the sidebar of an open object, for example, as in the screenshot? [Side Panel] Ideally, this panel should also have a filter, like the main search, but by the displayed elements. Describe alternatives you’ve considered Not located. Additional context It’s for additional usability. If the object is in a relationship with other objects, then these objects are displayed in the specified pan…

[HelenaGwyn]

That’s nice but something different. I suggest a type in which you can place other objects into a tree-structure. This object could be included on the canvas or in the sidebar. This object could have a domainname or url as a relation. The objects in the tree would become pages underneath the url resulting in a published website.

[forgettable]

Ok I see better. The problem is that there are still unknowns:

1. How will the publication of Objects work? Either only the published Objects will be published, or we will be able to include our nested Objects inside, like on Notion.

2. Under which URL will be displayed these shared Objects ? The IPFS protocol may not allow a redirection to a classic domain name. I don’t know.

[HelenaGwyn]

When publishing a tree-object, every object underneath it would be automatically published. Although I do see an issue if an object in the tree links to other objects not referenced in the tree. These links could need to be turned into unclickable text to prevent someone from following a link to an unpublished object.

You link a domain to the tree-object.

I’m new to IPFS. I’m going to do some reading.

[HelenaGwyn]

I did some reading on IPFS and found DNSLink (https://dnslink.io) and Pinata (https://www.pinata.cloud) both linking IPFS-data to a domainname. Maybe this might be a service AnyType could offer in the (near) future for a certain price?