1.1.0

[OwainWilliams]

This pull request performs a comprehensive rebranding and functional update of the Obsidian plugin, changing its name from "Umbracidian" to "umbPublisher" and updating associated identifiers, assets, and documentation. It also introduces significant improvements to the plugin's settings UI, particularly in how users select the parent node for publishing content in Umbraco, now supporting dynamic fetching and hierarchical selection of nodes.

Rebranding and Naming Updates:

• Renamed all references, files, code identifiers, and assets from Umbracidian to umbPublisher throughout the codebase, including in package.json, manifest.json, README.md, and TypeScript classes and interfaces. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]

• Updated plugin assets and icons to use new branding (e.g., umbPublisher-Logo.png, umbpublisher-logo.svg). [1] [2]

Settings and Configuration Improvements:

• Overhauled the settings UI to allow users to fetch and select the parent content node from Umbraco dynamically, including recursive retrieval and display of the content tree for easier selection. This replaces the previous manual UUID entry. [1] [2]

• Added helper functions to fetch bearer tokens and recursively retrieve all content nodes from Umbraco for use in the settings panel.

Functional and UX Enhancements:

• Improved the command registration to use editorCheckCallback for better command availability detection and user feedback.

• Refined the logic for extracting frontmatter and content from notes, removing the dependency on the gray-matter library and instead using Obsidian’s metadata cache and file reading for more accurate content extraction. [1] [2]

Documentation and Licensing:

• Updated documentation and repository links to reflect the new plugin name and repository location. [1] [2]

• Updated the LICENSE file to reflect the correct copyright holder and year.

CI/CD Automation:

• Added a new GitHub Actions workflow (.github/workflows/release.yml) to automate plugin releases on tag pushes, building the plugin and creating draft releases with the necessary assets.