The need for page inheritance functionality

Use case or problem

I would like Obsidian to provide page inheritance to organize the page hierarchy instead of just having a tag hierarchy.

Many times I don’t need a lot of hierarchical tags, the particle size of the pages is large and the particle size of the tags is small, it would be awesome to implement a hierarchy between pages.

The lack of hierarchy between pages causes me to give more thought to the naming of pages to ensure that when I review the page in the future, I can quickly recognize its purpose from the page name.

Proposed solution

For example, I’m creating a [[apple]] page, but in the future I’ll have a hard time recognizing whether it’s apple for fruit or apple for technology companies.
If there was a page inheritance feature, then I could inherit the [[apple]] of the fruit to [[Fruits]] and the [[apple]] of the company to [[Companies]].

A piece of software provides this functionality, and it handles the above example as follows. (But I prefer Obsidian, so I came here to suggest this.)

  • [[Fruits/apple]]
  • [[Companies/apple]]

In this way, [[Fruits]] is the parent page of [[apple]], under which there can be other sub-pages of the same level such as [[grape]], [[peach]], etc.

Current workaround (optional)

The only way I can do it at the moment is to manually attribute the page to the folder it should be in, and to avoid renaming, the name of the page may need to be specially marked.
As in the fruit example above, I might not be able to create two [[apple]] pages, I would need to write [[apple in Fruits]], [[apple in Companies]] and manually attribute them to the folders they should go under. Also, I may need to manually write another stupid sentence under the [[apple in Fruits]] page - [[apple in Fruits]] is a sub-page of [[Fruits]], in order to get a link relationship between them.
This example is enough to illustrate my current dilemma.

And, actually, my recording scenario is more mathematical in content. Instead of using LaTeX, I use Obsidian because I hope that the double linking will help me to find more connections between mathematical contents. But the same term in mathematics can have a completely different meaning depending on its scope. I really hope that Obsidian will provide the inheritance function of the page, and I expect Obsidian will be better.

You might want to try out the breadcrumbs plugin.


Thanks, I’ll try it.

1 Like

I don’t know if you what you need is something simple like breadcrumbs plugins, or simply configure obsidian to use absolute path in vault, or if you are asking some more comprehensive

No, I’m just lazy and don’t want to use YAML for every article.

As you said, I really just need simple plugins like breadcrumbs, but currently that type of plugin doesn’t directly distinguish hierarchical relationships between pages, but requires manual linking.

Now I found the Super FR you gave very interesting and I’m looking forward to it.

However, I would like to ask the following question.

In mathematics, for example, the method of substitution appears in various places, such as factorisation, calculus in one variable, multivariable calculus, etc.
When I wrote the [[Method of Substitution]] page, I ran into the problem of whether I should give it a more exhaustive name. For example, calling it [[Method of substitution of calculus in one variable]], [[Method of substitution in multivariable calculus]].
This would be cumbersome, and it would be difficult to see the connection between the permutation method and it at the file link level.

But without naming it that way, my only option is to put everything related to the method of substitution on the [[Method of Substitution]] page.

Or do I only have the option of creating a [[Method of substitution of calculus in one variable]] and later adding a link to the [[Method of substitution]] page?

Either way is very unfriendly. As for some plugins like Breadcrumbs, they don’t solve this problem for me either.

So I would like to know what you would do if you had a similar problem?
The solution most likely characterises the difference in thinking between us and could possibly help me, so allow me to thank you in advance!

Another way to establish hierarchies between topics would be to use nested tags - maybe you should give that a try as well…

1 Like

After a day of experimenting with nested tags, I found that my need for a file hierarchy had been satisfied. I also discovered that files with the same name could exist in different folders, which made things much less complicated for me.

However, there is still the inconvenience that the YAML language has no automatic tag completion prompt when editing tags, which makes manual typing a lot of trouble, and the template does not solve such a problem.

Is there a plugin for tag completion, or another solution?

I think I have found the solution, thank you very much.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.