Craft Docs: A Practical Guide to Craft

Overview

Craft Docs is a document workspace for writing, organizing notes, connecting related information, and presenting it in a polished form. The Craft app is the software used to create and access that workspace across supported devices, while “Craft notes” generally refers to notes and documents created inside it rather than a separate product. It can serve as a personal knowledge system, a place for professional writing, or a shared documentation environment.

This guide focuses on how those roles fit together in practice. It examines the path from capturing an idea to maintaining and sharing useful information, including where Craft AI can assist. It also explains the choices involved in collaboration, permissions, importing existing material, and preserving a portable knowledge base.

How Craft fits a document and note workflow

A typical workflow starts with a quick note, daily entry, or new document. Because content is assembled from blocks, an initial thought can grow into a structured page without requiring a rigid format at the outset. Writers can combine paragraphs with supporting media or embedded material, then use headings and nested documents to turn rough capture into something easier to navigate.

Organization happens at several levels. Spaces establish broader working contexts, folders and nested documents create hierarchy, and tags provide another way to group related material. Links between documents help connect ideas that do not fit neatly into a single folder. This makes Craft notes suitable for evolving subjects, although the workspace still benefits from consistent naming and a deliberate structure. Full-text search can retrieve material later, but search does not remove the need to archive obsolete pages or clarify which document is authoritative.

Daily notes, tasks, and calendar views can bring time-sensitive material into the same writing flow. Craft is still primarily a document and knowledge workspace rather than a dedicated task manager. Readers who need assignment-heavy execution may want to compare that model with a focused system such as Todoist task management.

Craft AI can enter the workflow when a draft needs summarizing, translation, rewriting, or assistance from a custom prompt. Its usefulness depends on the selected processing mode and available plan credits. On-device processing offers an offline route that does not consume AI credits, while cloud-based assistance introduces different processing considerations. AI output should remain a draft or aid: the document owner still needs to verify accuracy, preserve context, and decide whether generated wording belongs in the maintained record.

Sharing, collaboration, and workspace responsibilities

Private drafting and collaborative documentation are related but distinct modes. A writer can prepare material before exposing it to others, then share a document through a link, invite participation, or publish it for a broader audience. External people can view or edit shared documents without creating a Craft account when the selected sharing configuration permits it. Comments provide a feedback path without requiring every participant to rewrite the source material.

Shared Spaces support a more persistent team context, but they are plan-dependent rather than part of the Free offering. They are most useful when several people need to maintain connected documentation over time, not merely read a finished page. A team deciding between Craft and a more administration-oriented knowledge system may also find the distinction clearer by reviewing Confluence for shared team knowledge.

Craft supplies the workspace, sharing mechanisms, and collaborative editing environment. It does not decide the organization’s information architecture or governance rules. Workspace administrators and contributors must determine who should edit, which pages may be public, how drafts are marked, and who owns ongoing maintenance. They also need a process for removing outdated links, reconciling duplicate documents, and reviewing access after someone’s role changes.

Public presentation adds another responsibility. A visually finished page can still contain confidential details, stale instructions, or embedded material with separate access requirements. Before distributing a link, its owner should review both the document and the resources it references. Where public discovery matters, teams should establish their own publishing checks rather than assuming every shared link has the same visibility or indexing behavior.

Importing, exporting, and maintaining a portable knowledge base

Moving existing material into Craft is not simply a file-transfer exercise. Import support covers several document formats and established note services, but the quality of a migration depends on the source structure. Nested pages, internal links, attachments, tables, and unusual formatting may not map perfectly between systems. A small representative import is therefore more useful than moving an entire archive before checking the result.

After import, review hierarchy, media, links, and document titles. It may be better to restructure active knowledge than preserve every historical folder exactly. Duplicate notes and abandoned drafts should be handled before they become part of the new workspace’s search results and navigation.

Exports provide a route for backups, publishing workflows, or future migration. Choosing formats that retain meaningful structure makes the exported material easier to reuse outside Craft. Teams that prioritize device-held Markdown files above managed workspaces may also consider how Craft’s model differs from Obsidian’s local-first notes.

Portability remains an ongoing practice rather than a one-time setting. Schedule exports appropriate to the value and rate of change of the material, inspect them periodically, and document how critical pages relate to external files. That approach reduces lock-in while making recovery or migration more predictable.