Output Folders
Currently, I'm not using explicit output folders within my Efforts space. I'm just using an Output note for each output, which are reflected in my Outputs View.
When I'm working on create an output, it seems worthwhile to have an Output Map with an Output template to help me plan, outline, and manage my work for that output. Although this could simply use a Map fileClass, it might be better to have an OutputMap fileClass specifically for an output map.
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 file 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, the 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, Music, 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).
Categories
Since I have many interests in my PKM system: Music, Photos, Travel, Genealogy, Health, Writing, Reading, and Blog, I classify them with a category property. And I have a category page for each of them with a category menu (like a category map).
Topics
Within a category, I have multiple topics and each has a topic page with a corresponding menu for navigation (like a topic map).
Groups
Within a topic, I sometimes have groups that I create for collections of related pages. And for these, I have a group page as a menu for navigation (like a group map).
Views
Since the Dataview plugin is not supported by Obsidian Publish, I'm generating Markdown lists or tables from my Obsidian Dataview queries and then publishing them on my web pages and posts. At least, they're still dynamic and current when published changes are pushed to the website.