# Product Vision & Plan Quick overview of what I want: - 1 Obsidian vault that I write in… - with Obsidian Publish set to publish to [vault.goinglovefirst.com](vault.goinglovefirst.com) (✅ ) - `AND` which is ALSO tracked in a github repository - `AND` that repository publishes the goinglovefirst.com website - `AND` the notes that are committed to the repository don't need to be the same that get published to the `vault` subdomain (✅ ) - `AND` the notes published to the main site support MDX component imports & use, as well as Obsidian-style `![[Wikilinks]]` embedding of notes - The notes support YAML frontmatter compatible with [the starter template used for the main goinglovefirst.com site](https://github.com/timlrx/tailwind-nextjs-starter-blog) - The notes *can* be kept in a flat folder structure, but - Ideally, they support a folder structure so that there can be a matching structure between the `vault` subdomain and the main site - `AND / OR` the main site supports a nested folder display via the use of `tags:` in the YAML frontmatter This list is incomplete but covers the core file & folder structure. ## Obsidian link experiment Here are two links, one to [[Universal Love]] and one to [[Give Your Stories A Title]]. The former is in the root directory, the latter inside a subdirectory called `/newsletter` in the folder structure. Initially, the two links look like this in the source file: ```md [[Universal Love]] … [[Give Your Stories A Title]] ``` When I make a second file also called [[Give Your Stories A Title]], but in the root folder, the source file somehow does not distinguish the difference. I did get prompted if I wanted to change existing links (to the `/newsletter` file) and update them to point to the new file I was creating with the same title. But, I declined, and now this is the source file output: ```md Here are two links, one to [[Universal Love]] and one to [[Give Your Stories A Title]]. The former is in the root directory, the latter inside a subdirectory called `/newsletter` in the folder structure. When I make a second file also called [[Give Your Stories A Title]], … ``` Here is a newly-made internal link, explicitly to the `/newsletter` one: [[newsletter/Give Your Stories A Title|subfolder link (with custom display text)]]. It now contains the subfolder in its source link (and if not overridden with a `|`, also in how it is displayed). The original link, which I didn't update, now points to the newly created second file. ### Random testing I've now set the New Link Format setting to *Absolute path in Vault*, and here are some tests: Root folder links: - [[there-is-no-final-destination-you-are-eternal|There Is No Final Destination; You Are Eternal]] - [[Welcome To Love First]] Subfolder links: - [[_sources/On Creating Conscious Culture]] - [[how-to/Go Love First|Go Love First]] The source code of those: ```md Root folder links: - [[there-is-no-final-destination-you-are-eternal|There Is No Final Destination; You Are Eternal]] - [[Welcome To Love First]] Subfolder links: - [[_sources/On Creating Conscious Culture]] - [[how-to/Go Love First|Go Love First]] ``` > [!INFO] Note > Two links point to notes not published to the vault, and so they show up as plain text. ### Incomplete aspects I didn't test what happens when you make a new duplicate file _deeper_ in the file tree, and what happens after you decline (in the prompt) to update existing links. Additionally, I haven't tested with multiple nested folders to determine the order of how Obsidian does its file tree prioritization, i.e. root-first and alphabetically through folders second? Recursively through folders first or root-upwards one level deep at a time? Or maybe creation date-based? Don't know! ### Conclusion It seems Obsidian does smart file linking for internal links that are in subfolders, going down the file tree until it finds one. When creating duplicate title files, it prompts you to update existing links accordingly, but if you don't do so the existing links will point to the new file.