Skip to main content

Creating and editing bits

Bits are the smallest building blocks of content in Floxar. Each bit is a single, self-contained process step that combines rich text, media, and interactive elements that can capture input from the person working through it. This article covers what a bit contains, what the editor can do, and how bits relate to flows.

What a bit contains​

Every bit has a title, and you must provide one before the bit can be created. You can also add a description, an abstract, and category tags — categories such as "Onboarding" or "Troubleshooting" help you filter, group, and find related content. A bit can carry a target completion time (up to one hour) so you can see whether a step tends to take longer than intended. Reading statistics such as reading time and word count are computed automatically from the content; you never maintain them yourself.

The body of a bit is a structured document: the title always sits at the top and cannot be deleted, and the document always ends with a text line so there is always somewhere to keep typing.

Writing and formatting content​

The rich-text editor supports the content types you would expect from a modern document editor:

  • Text — paragraphs, several levels of headings, formatting such as bold and italics, quotes, and highlighted callouts for important notes.
  • Lists — numbered lists, bulleted lists, and definition lists for term-and-definition pairs.
  • Tables — with optional header, footer, and caption.
  • Code blocks — for technical steps and snippets.
  • Media — images (optionally with captions) and videos, either uploaded or referenced from an external address. A bit can hold up to 25 media files; images are compressed automatically on upload.
  • Other blocks — embedded frames that show external web content inside a step, link preview cards, and dividers that separate sections.

Your changes are saved automatically after a short pause in editing, so you do not need to save each edit by hand. Structured blocks such as tables, media, and interactive elements are configured through their own panels and menus rather than edited as free text.

Interactive elements​

Interactive elements are the parts of a bit that capture data or record an action while someone runs the bit inside a trail. Nine types are available:

  • Checklist — a list of items the person ticks off; each item records its own checked state.
  • Date picker — captures a date, a time, or a date and time, depending on how you configure it.
  • Dropdown — a single choice from a configured list of options.
  • Radio buttons — a single choice from a set of options shown all at once.
  • Text area — free-form text such as notes or case details. You can control its size and maximum length, and add a validation pattern that either warns about non-matching input or blocks it.
  • Searchable field — lets the person search a configured data source and select one or more matching items.
  • Inline link — a link inside a sentence that records whether it was opened.
  • Link card — a link presented as a preview card with details about the destination; it also records whether it was opened.
  • Video — a video that records whether it was played.

Each element carries a short name that identifies its captured answer in trail records; names are generated automatically and you can rename them. The answers people enter are saved step by step with their trail — see the article on running and tracking trails.

How bits relate to flows​

Bits are library content, not parts of any single flow. A bit exists on its own and can appear in zero, one, or many flows. You build a flow by connecting bits: connections appear as navigation buttons inside the bit, and each one leads to another step. Removing a bit from one flow does not remove it from the library or from other flows that use it.

Bits are never deleted. To retire one, you archive it: archiving removes the bit from every flow's paths and prevents it from being added to new flows, while past trail records that visited it remain fully readable. A bit that is the starting bit of an active flow cannot be archived — point the flow at a different start or deactivate the flow first.

Last reviewed: 2026-07-28