publish

To publish markdown notes as a standalone encrypted HTML file, use the publish skill to generate self-contained HTML output with client-side AES-256-GCM encryption and password protection. It strips private metadata during the process.

Client-side AES-256-GCM encryption for HTML pages is a security mechanism that uses PBKDF2 key derivation to password-protect content directly in the browser. This ensures encrypted data remains inaccessible without the correct password.

Yes, publishing encrypted brain pages automatically strips private metadata, internal citations, and references before generating the final standalone HTML. This ensures sensitive internal knowledge structures are not exposed to external readers.

Yes, you can share deal memos or research notes as password-protected HTML. The publish skill creates self-contained HTML files with no external dependencies, using client-side AES-256-GCM encryption for controlled access.

The best way to securely share knowledge pages across teams is generating standalone HTML files with client-side password protection. This approach uses PBKDF2 key derivation and AES-256-GCM encryption to ensure data privacy.

No, you do not need a server to decrypt password-protected HTML pages. The publish skill uses client-side AES-256-GCM encryption and PBKDF2 key derivation, meaning all decryption happens directly in the viewer's browser.