Skip to content

Commit 49523e8

Browse files
committed
docs: [UPDATE] What is a Fragment Type
Fragment ID: a5409f44-97f1-43e1-87ba-ec62ae670fdf Path: src/content/docs/knowledge/what-is-a-fragment-type.md Auto-generated by N8N
1 parent 10fba52 commit 49523e8

File tree

1 file changed

+13
-2
lines changed

1 file changed

+13
-2
lines changed

src/content/docs/knowledge/what-is-a-fragment-type.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,14 @@ description: "Comprehensive documentation explaining fragment types: purpose, st
44
fragmentId: "a5409f44-97f1-43e1-87ba-ec62ae670fdf"
55
fragmentType: "Knowledge"
66
createdBy: "unknown"
7-
createdAt: "2025-10-30T12:27:22.510Z"
8-
updatedAt: "2025-10-22T13:48:56.266Z"
7+
createdAt: "2025-10-30T12:27:46.607Z"
8+
updatedAt: "2025-10-23T15:26:23.666Z"
99
badges: []
1010
---
1111

12+
> Update: Sourced from Usable Live (2025-10-23) — Fragment Types session. See summary and full transcript linked at the end.
13+
# What is a Fragment Type
14+
1215
A **Fragment Type** is a classification system that helps organize and categorize knowledge fragments within Usable workspaces. Fragment types provide semantic meaning to your content, making it easier to find, filter, and understand the purpose of each piece of information.
1316

1417
---
@@ -217,3 +220,11 @@ This demonstrates how **fragment types scale** from personal knowledge managemen
217220
---
218221

219222
**Sources**: Compiled from Usable Live sessions (Oct 2025), particularly the "Docs From Context" session and Week 41 Clarity case study.
223+
224+
---
225+
### Updated from Usable Live (2025-10-23)
226+
This page was updated based on the Usable Live session focused on the five default fragment types and how we use them in practice, including auto-generating docs for the Astro JS site.
227+
228+
- Summary: “Usable Live - 2025-10-23: Granola Summary - Fragment Types”
229+
- Full transcript: “Usable Live - 2025-10-23: Transcript (Fragment Types)”
230+
- Key additions: clarified purpose of defaults, human vs LLM focus (Recipe vs Instruction Set), examples of custom types (e.g., Gmail in CRM).

0 commit comments

Comments
 (0)