vicode
DocsAPI
Sign in

Get started

OverviewPublishingProject pages

Workspace

Notes and commentsAPI and CLIFAQ

Notes, comments, and voice memos

How the active workspace trail works and how to use build logs, notes, comments, and voice memos together.

Create a project

Build log versus notes

Build-log entries are the high-signal trail. Notes are the lighter, faster layer.

  • Use build log for milestones, releases, setbacks, and visible progress.
  • Use notes for ideas, blockers, decisions, and rough in-progress context.
  • Use voice memos when speaking is faster than writing.
  • Use comments for signed-in discussion tied to the project itself.

Signed-in discussion

Comments are native to vicode and tied to signed-in users. That keeps discussion inside the workspace instead of splitting it across an external tool.

When to use each workspace layer

Use build log for the moments a visitor should notice immediately. Use notes when the work is still messy, raw, or incomplete. Use comments when other signed-in users should be able to respond in context.

  • Build log: releases, milestones, setbacks, pivots, launch notes.
  • Notes: ideas, blockers, decisions, rough thinking, voice memos.
  • Comments: questions, reactions, clarification, outside input.

Project pages

Previous Page

API and CLI

Next Page

On this page

Build log versus notes
Signed-in discussion
When to use each workspace layer