Feature Request: Public Vault Publishing with Optional Login Access

[pilasguru]

I propose adding support for publishing one or more vaults in read-only mode to the public. When at least one public vault is configured, the first page of the site would display the public content, along with a "Login" link for authenticated access. If no vaults are marked as public, the site should continue to default to showing the login form, as it currently does.

Benefits:

• Public-facing content: Easily turn a vault (or group of vaults) into a public knowledge base, blog, or documentation site without requiring complex user role or permission systems.
• Draft-to-public workflow: Users can create and edit notes in private vaults, then move them to a public vault once ready for publication.
• Simplicity: Enables content sharing without additional infrastructure or access control setup.

This would greatly enhance the software's use cases, making it suitable not only for personal or team use, but also for sharing curated content with a wider audience.

[brufdev]

Thank you for the suggestion.

This is not planned, at least for the near future. I need to think about it, but I have other higher-priority features to focus on right now. I will move this to discussions to leave it open for ideas in the meantime.