Summary
The artefacts section is where users view, manage, and access their generated artefacts. It serves as both a personal library and a launchpad for publishing/sharing.
Views
Gallery View (Primary)
- Grid layout showing the most recently created artefacts
- Each card shows: title, type, creation date, status (draft/published), thumbnail or preview
- Visual, browsable format for quick discovery
List View
- Full list of all artefacts with more detail per row
- Sortable/filterable (by date, type, status, etc.)
- Better for users with many artefacts
Artefact States
| State | Description |
|---|---|
| Generating | Agent is currently producing the artefact |
| Draft | Generated but not yet published |
| Published | Shared via one or more publishing methods |
Artefact Detail View
Clicking an artefact opens it for:
- Reading the full content
- Editing (if still in draft, or for revisions)
- Publishing actions (see 06-publishing-sharing.mdx)
- Viewing metadata (created from which exploration, which snippets, when)
Published Artefacts List
Within the artefacts section, there should be a view of published artefacts showing:
- Which artefacts are published
- The sharing method(s) active for each (global, link, team)
- Quick access to share links
- Ability to unpublish
Open Questions
- Should artefacts be versionable? (v1, v2 after edits)
- Can artefacts be duplicated/forked?
- Is there a search function within artefacts?
- Should artefacts show analytics? (views, shares, etc.)
- Can artefacts be grouped into collections or folders?
- What does the artefact editing experience look like? Rich text editor? Markdown? Block-based?
- Should there be artefact templates that users can create and reuse?