# v1.1.2_navigation #shipped #### Last Version: [[v1.1.1_content]] #### Release Date: 2025-04-28 #### Description: Continued apologies for broken links. In this release I've changed the naming convention for what were previously called *index* pages. This is about the biggest breaking change I could do as far as URLs, so I figure best to do it early, before the site is getting much traffic. The naming convention is now as follows: - Each directory contains an index page - The top level directory index page is called `root` - Each top level directory gets its own index page: - `career` directory gets `career` index page - `creative` directory gets ``creative`` index page - `development` directory gets `development` index page - `personal` directory gets `personal` index page - If additional sub-indexes are needed, they can be added using the same naming convention: - eg: `creative/mesk-xyz` directory gets `mesk-xyz` index page This makes the graph view easier to read and navigate at a glance, and simplifies file names. The change does have the side effect of producing URLs of the form: `words.mesk.dev/personal/personal`, which I don't love. The previous format was: `words.mesk.dev/personal/personal-index`, which I also dislike. My preferred solution would be to have the index page exist at: `words.mesk.dev/personal` but this isn't supported using Obsidian Publish (at least out of the box). I could name all these types of pages `index`, which would produce (eg): `words.mesk.dev/personal/index` `words.mesk.dev/development/index` but this would make the graph view hard to navigate. So this is the best middle ground I could quickly find for now. It's not perfect, but it's consistent and easy to read, which is a start #### Features: - Changed naming convention for `index` type pages: - Previous examples: - `main-index` (root level index) - `personal-index` (sub-index for the `personal` directory) - New examples: - `index` (root level index) - `personal` (sub-index for the `personal` directory) - Updated [[career]] section - Single page for each employer instead of one page for each role title - Pages added for each project/experience, so single employer page doesn't need to be too bulky, and experiences can be linked from any other page