Draft42 Docs

Settings

The Draft42 plugin settings are accessible through Obsidian's Settings → Community Plugins → Draft42. Settings are organized into several sections.

Authentication

  • Token — your Draft42 API token, stored securely in Obsidian's secret storage.

Manage API tokens at Draft42.

Sites

Lists all sites associated with your account. For each site, you can:

  • Set a folder path — the vault folder where the site's content lives.
  • Enable or disable — toggle whether the plugin manages a particular site in the current vault.

If your vault is dedicated to a single site, you can set / as the folder path to use the vault root directly instead of creating a subfolder.

Use Refresh sites to pull the latest site list from Draft42 if you've made changes on the web.

Automations

  • Manage site folders — automatically creates and organizes the file and folder structure for your sites.

We strongly recommend keeping this enabled, as manual management currently might have some rough edges. Managing site folders manually is possible, but not well tested, so it's error-prone.

Block IDs

Block IDs are short identifiers appended to content blocks (paragraphs, headings, list items, etc.) that make individual blocks linkable. When enabled, the plugin automatically generates and manages them — you don't need to add or edit them yourself.

Block IDs enable several features:

  • Deep linking — link not just to a page but to a specific paragraph, heading, or list item within it. You can cross-link from your content. Your site visitors can do this too!
  • Table of contents — headings with block IDs power automatic TOC generation for your content.
  • Content diffing — block IDs let the system track individual blocks across edits. In the future, we will allow tracking content changes, so users will be able to see exactly what changed in the recent update.

During publishing, the plugin checks that linked blocks exist, so you'll catch broken references before they go live.

We strongly recommend keeping it on. Without them, you lose all these goodies.

  • Enable — toggles block ID generation. Enabled by default. Disabling won't remove existing IDs, but new blocks won't get them.
  • Opacity — controls how visible block IDs are in the editor. Defaults to very subtle so they stay out of your way while writing.

Debugging

  • Extensive logging — enables detailed logging for troubleshooting.
  • Expose internal metadata — makes internal frontmatter fields visible in the editor.

These are off by default and only useful when diagnosing issues.