Store Notes as Markdown into folders with hierarchy

Concept: Saving Notes and Metadata in a File-Based Structure

I really appreciate the idea of saving notes in a file-based hierarchy, specifically using Markdown files for the content. And saving all meta information related to each note in a hidden .floaters.

Format for Meta Information

To enhance interoperability and transparency, a standardized exchange format like JSON could help. This would allow both users and third-party applications to:

• easily view and understand the meta information (such as background color, transparency, monitor placement, group assignment, etc.),
• alter or update these settings manually if necessary.

Indexing for Performance

To avoid the need for Floaters to constantly scan all folders and files to often or in a way to short interval, a centralized indexing and catalog mechanism could be introduced into an lightweight SQL-based database file (placed in project root or offical "Documents" folder of MacOS).

This index would:

• keep track of all available Markdown notes and their associated meta files,
• categorize and locate floaters efficiently,
• minimize filesystem reads and improve the app's overall performance.

The choice of database format and structure should be flexible, depending on the developer's preferences.

This would be the primary use for Floaters for me. To have Floaters automatically save .md files to a predefined directory within a vault of notes, so its automatically integrated with my existing system.

Floaters becomes a handy way to capture notes in the moment without switching context or focus. And seamlessly hands off to my chosen writing app when I later want to reference that information or incorporate it into other notes etc.

This is nearly completed for version 1.0 and will be available soon. Lots of settings, and features involved to make it work solo and to make it play nice with other apps that also have their notes in markdown format.

This has been completed and released with version 0.9