Style guide

Style guides go stale the moment they're published. The editorial guide was accurate when someone wrote it. Then the brand voice shifted, a new product launched, the terminology changed, and nobody updated the guide because updating it means opening a Google Doc or a PDF and hoping you find the right section. Meanwhile, the team is writing in three slightly different voices because the "official" guide reflects decisions that were revised in a Slack thread two months ago. The guide that's supposed to create consistency is itself inconsistent with what the team actually does.

Fabric keeps your style guide alive: editable in real time, commentable by the team, searchable by AI, and shareable via a single link that always reflects the current version. Update once, everyone sees the latest. No more "which version is current" emails.

Editable by the team, not locked in a PDF

Write your style guide in notes and docs with full Markdown support. The guide is a living document, not a published artefact. When the tone of voice evolves, edit the section. When a new product term is added, update the terminology list. When a convention changes, change it in one place.

Real-time collaboration means multiple people can edit, comment, and refine the guide simultaneously. The writing team proposes a change, the brand lead approves it, and the guide is current. No separate review process, no version proliferation.

Structure the guide across multiple notes if it's large: one for tone of voice, one for grammar and punctuation, one for terminology, one for formatting conventions. All searchable together as one body of knowledge.

AI that answers style questions instantly

Nobody reads the full style guide. They have a specific question: "Do we use the Oxford comma?" "Is it e-commerce or ecommerce?" "What's our tone for error messages?" "How do we refer to the product in third person?"

The AI assistant answers from the guide in seconds. Ask a style question and get the answer with a citation to the relevant section. No scrolling, no ctrl+F, no asking a colleague who might remember it differently.

AI search finds anything in the guide by meaning. Search "how to write CTAs" and find the section, even if the guide calls it "calls to action" or "button copy." The search works by concept, not exact phrasing.

One link, always current

Publish the style guide with a password-protected link. Freelancers, agencies, new hires, and cross-functional teams all get the same link. Update the guide and the link serves the latest version. No re-publishing, no re-distributing, no version confusion.

Link analytics show who's accessed the guide, when, and how long they spent. Create named tracking links per recipient: one for the agency, one for the freelance pool, one for the product team. When someone's writing doesn't match the style, you can see whether they've read the guide before having the conversation.

Commentable and discussable

Style decisions are debated. "Should we capitalise feature names?" "Is this sentence too formal for our blog voice?" The discussion should happen on the guide, not in a separate Slack thread that gets buried.

Annotations let team members comment on specific sections of the guide: propose changes, flag inconsistencies, ask questions about edge cases. The comments are pinned to the exact section they refer to and are searchable. The debate happens in context, and the resolution updates the guide directly.

Stays current from your team's discussions

Self-writing docs can keep the style guide connected to how your team's language actually evolves. When a meeting or Slack discussion produces a style decision, the decision log captures what was decided and why. The guide and the reasoning behind it stay linked.

Agents can flag when content across your workspace diverges from the style guide, or produce a digest of recent style decisions for the team.

Works for every kind of style guide

Editorial and content style. Tone of voice, grammar conventions, punctuation rules, terminology, formatting for different channels.

Design system documentation. Component naming, usage rules, spacing conventions, colour application rules, dos and don'ts with visual examples. Arrange examples on the canvas alongside the written rules.

Code style and engineering standards. Naming conventions, documentation standards, commit message formats, PR templates. Searchable alongside the team's technical documentation.

Client-specific style. Agencies managing multiple brands keep a style guide per client space. Each client's voice, terminology, and conventions in one searchable, shareable place. See Fabric for agencies.

Who uses Fabric for style guides

Writers and content creators reference the guide while drafting. Marketers check tone and terminology for content planning. Designers maintain design system documentation. Creative teams and agencies share style guides with clients and freelancers. Marketing teams keep editorial standards current as the brand evolves. Engineering teams maintain code style and documentation standards.

For the visual brand system (logos, colours, fonts, assets), see brand guidelines. For the broader team knowledge base, see team wiki.

Get started

Keep your style guide alive and stop publishing documents that go stale the moment they're shared. Try Fabric free.

Comparing tools? See the best creative ops platform comparison.

FAQs

Can the AI answer style questions from the guide?

Yes. The AI assistant answers questions like "do we use the Oxford comma" or "how do we write error messages" from your guide, with a citation to the relevant section.

Can we edit the style guide collaboratively?

Yes. Notes and docs supports real-time collaboration. Multiple people can edit, comment, and refine simultaneously.

Can we share the guide with one always-current link?

Yes. Publish with password protection. Update the guide and the link reflects the change. No re-publishing.

Can we track who's read the guide?

Yes. Link analytics show who accessed the link, when, and how long they spent. Named tracking links per recipient.

Can team members comment on specific sections?

Yes. Annotations let anyone comment on specific parts of the guide. Propose changes, flag edge cases, and discuss in context.

Does the guide stay current automatically?

Self-writing docs capture style decisions from your meetings and Slack. The decision log records what changed and why. The guide itself still needs a human to update the text, but the decisions that should inform updates are captured automatically.

Can we have separate style guides per client?

Yes. Agencies can maintain a style guide per client space, each with its own tone, terminology, and conventions, each shareable via its own tracked link.

Can we include visual examples in the style guide?

Yes. Embed images, screenshots, and examples alongside the written rules. Use the canvas for spatial arrangements of do's and don'ts with visual examples.

Does it support Markdown?

Yes. Notes and docs supports Markdown natively. Write with the formatting syntax you know.

How is this different from a Google Doc or Notion page?

A Google Doc or Notion page is static until someone edits it, has limited search, and requires re-sharing when the URL changes. Fabric adds AI search by meaning, an AI assistant that answers style questions with citations, tracked sharing with per-recipient analytics, annotations for in-context discussion, and self-writing decision logs that capture style decisions from your team's conversations. The guide is alive rather than slowly going stale.

Is our style guide secure?

Yes. Fabric uses AES-256 encryption and is CASA Tier 2 compliant. Published links can be password-protected.