Templates & Relations v Type & Relations

[Filip]

Relations are per-object, you can add any relation to any object that you want regardless or template or type.
When you “add” a relation to a type trough the library, you’re only adding a suggestion that will show up in the relation menu of every object of that type. You’re not technically adding those relations to those objects.
On the other hand, when you add a relation to a template, you are adding the relation itself to to template and any object that is created trough that template.
These are all separate things. This way, you can add relations that should be used in all of your objects of that type to that type, and then only add relations that you want to be used in specific templates to that template.

@Pointswell

I would expect that a Type when you add relations to it not update the Template automatically (which is how Anytype behaves).

@Pointswell

. Anytype however works like an MS Word Template, once you make a Word document from a template that is the Word document, if you change the MS Word Template then new Word documents get that new template.

Yes, templates are a manual process right now. Hopefully in the future we get the ability to automatize them. Something like this:

Embedded Templates

Is your feature request related to a problem? Please describe. I have certain projects that reoccur on a regular basis and would like to create a template for it. To manage progress in the project, I would like to create some pre-defined tasks alongside the project every time I create a new copy from the template for a project. Right now creating objects in a template makes them their own objects outside of the template. Describe the solution you’d like I would like to create a template for a…