Heartbeat Help Center

How can we help?

Resources Overview

  • Updated

Resources is where your written and downloadable content lives: guides, workbooks, templates, reference libraries, recorded material, onboarding material. It replaces Docs.

A Resource can be published to the open web, gated behind an email address, or sold outright, without the reader needing an account. That makes it the first thing a stranger encounters, and the thing that turns them into a contact you can follow up with.

How Resources are structured

Resource → Folder → Document.

  • A Resource is the container, and it is the unit of access. Anyone who can open the Resource can open everything published inside it.
  • Folders are a single layer of grouping inside a Resource, for when you have enough documents to want them. You do not have to create one, and until you have two Documents the folder layer stays hidden. There are no sub-folders.
  • Documents are the pages. A document can hold text, images, files, video, and embeds.

Creating a Resource

  1. Go to Resources in your community sidebar.
  2. Click + New Resource.
  3. Give it a Name. This is required, and it is what readers see.
  4. Add a Description if you want one. Optional, but on a public Resource it is the first thing a stranger reads, so it is worth filling in.
  5. Choose a Resource type. This is required:
    • Text: markdown docs. The default. Use it for guides, written material, anything you are writing rather than uploading.
    • Video: a video library.
    • File: asset downloads. Use it for the things people download and keep, like templates, worksheets, and PDFs.
  6. Click Create.

The type you pick sets the initial document type, not a permanent constraint. You can mix and match document types inside the Resource afterwards, so a Text Resource can still hold a video and a File Resource can still hold a written introduction. Pick the one that describes most of what is going in it.

The type changes how a document presents itself:

  • A File document leads with a file card: the file type icon, the file name, its size, and a Download button, with any writing you add underneath. 
  • A Text document is the writing itself. That makes File the right choice for a downloadable, and Text the right choice for something people read on the page.

Building out a Resource

  1. Add your documents. Write in the editor, or start with Add image, Add video, or Add file at the top of a document. Type / to see the full list of content blocks.
  2. Each document stays a Draft, labelled as such, until you publish it. Drafts are only visible to you and other admins.
  3. When the Resource is ready, publish it.

Nothing about who can see it, what it costs, or whether it collects emails is decided when you create it. All of that happens at publish. See Publishing a Resource.

What you can do with a published Resource

You want to Publish it as
Let anyone read it, no email, no account Public only, open access
Collect email addresses from strangers Public only, email access
Sell to people who are not members Public only, paid access
Give every member something Community only, open access
Give one group something Community only, limited access
Include it in a paid membership Community only, limited access
Sell it to members as a one-off Community only, limited access
Free for members, paid for everyone else Everywhere

Access and Permissions

Access is all-or-nothing within a Resource. If someone can open it, they can open every published document inside it.

What varies per document is whether it is published at all. You choose that document by document when you publish the Resource.

There are no per-Document permissions. If you need two audiences to see two different things, make two Resources.

Frequently asked questions

What happened to Document sections?
Sections are now Folders, and they sit inside a Resource.

Can I still nest documents inside other documents?
No. The hierarchy is Resource → Folder → Document, and it stops there. Content that was nested deeper was flattened during the migration.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request