Ghost Outputs

There are several challenges to consider with my Ghost outputs: pages, posts, tags, navigation, and menus.

Pages

When creating content for my Ghost website from my linked notes, there are several challenges and issues to consider. In general, I want atomic notes to be pages within my website.

In my Obsidian vault, I link related notes together and organize them with maps, views, and metadata.

In my digital garden vault, the Properties are hidden when displaying a note, and I manage my file properties in the right sidebar pane.

This also means that any tags are also hidden when these notes are rendered by Obsidian Publish.

Posts

Although my pages are generally created from notes in my Atlas space with my ideas and knowledge, my blog posts are more like time-based notes in my Calendar space.

In many cases, many tend to be shorter and reference pages on my website. Also, they often reflect new discoveries, tips, techniques, how-to's, or insights based from my current experiences.

Since they are temporal, it's better to integrate related content into other pages and simply include a reference with some brief context and/or commentary.

My blog posts are distributed to my newsletter subscribers whenever new content is published. So they receive a stream of content over time.

It's the pages where persistent content belongs, and posts just provide an entry point for more.

Tags

I need to think about which tags and/or properties are relevant for published notes, and how should I present them.

Since fileClass and tags are hidden for published notes, I'm experimenting with showing tags that reflect the type of page and main tag status at the top of a page before the title.

Navigation

Also, I must determine ways to navigate my published notes, which means I should think about how I use maps and how should those be used for navigating published notes.

Currently, I'm trying to use my maps as pages on the website to see how they work in that context. Maps offer more context and structure that simple menu pages used in traditional applications and websites.

Menus

On my Ghost website, I have a main menu in the site navigation bar for major sections like Home, PKM, Technology, Interests, and About.

Each of these sections have a section page that serves as a menu for pages in that section.

I use properties for classification rather than hierarchical folders, but provide a similar drill-down navigation via nested menu pages (like maps in an Obsidian vault).