Welcome!

Uploading Content Items

TL;DR; A content item is a single file inside a library folder — a PDF, a Markdown document, a text file, or a video. You upload content items from inside a folder; they show up in the library's browse view and become part of the AI agent's knowledge base.

Content items are the atoms of the Knowledge Base. Everything the AI agent can answer questions about is, ultimately, a content item someone uploaded.

Supported file types

Libraries support the same document types as document activities:

  • Markdown (.md) — rendered as formatted HTML.
  • PDF (.pdf) — rendered in an embedded viewer.
  • Plain text (.txt) — rendered as-is.
  • Video — referenced or uploaded, depending on your plan.

Other file types (Word, Excel, PowerPoint) aren't supported as content items today. Convert to PDF or export to Markdown before uploading.

Uploading from inside a folder

Open the library, navigate to the folder where you want the content to live, and click Upload Content Item (or similar). You'll get a file picker and a form with:

  • Title — what learners will see. Defaults to the filename minus the extension, but rename it to something human-readable.
  • Description — optional, shown under the title in the browse view. Use it to explain what the content covers and who it's for.
  • File — the actual file to upload.
  • Tags — optional keywords for search.

Upload Content Item form with a PDF selected

Bulk uploading

If you have a lot of content items to add at once, you can usually upload multiple files in a single operation — select them together in the file picker. Each file becomes a separate content item with its filename as the default title.

For very large migrations (hundreds of files), consider doing it in batches of 20–50 to keep the upload manageable and easier to review.

Writing good titles and descriptions

The title and description are what a learner sees in the library's browse view and what the AI agent uses to decide whether to surface the content in an answer. Good metadata makes the difference between "I can never find anything in here" and "this library is actually useful."

A few rules:

  • Title: start with what the content is about. "Incident Response Runbook" beats "Runbook-v2.pdf." Avoid acronyms unless they're universally known.
  • Description: one or two sentences explaining what the content covers and when someone should use it. "The official runbook for a Sev 1 production incident. Start here when paging the on-call team."
  • Tags: use a handful of specific keywords, not a wall of synonyms. Three or four tags is plenty.

How content items are used

Content items have two audiences:

  • Learners browsing directly. They open the library, navigate to the folder, click a content item, and read it inline. Same rendering experience as document activities.
  • The AI agent, if the library has one. The AI indexes the content items and uses them as the source material for answering questions.

Both audiences benefit from good metadata and well-structured content. The AI is more forgiving of bad titles than a human browsing visually — it can look inside the file — but good titles still help both.

Updating a content item

If the underlying file changes, edit the content item and upload a new version. Lupo replaces the file while keeping the item's ID, title, and place in the folder.

For changes that materially alter what the content says (new sections, removed sections, changed recommendations), consider adding a "last updated" note to the description so learners know to re-read.

Removing a content item

Delete a content item from its row in the folder view. Deletion is permanent — if you want to take something offline temporarily without losing it, move it to a "retired" folder instead.

Where to go next