Skip to content
Titan Docs Titan Docs

Organize a large workspace

Uses

Section titled “Uses”

Prerequisites

Section titled “Prerequisites”
  • Open a project that has enough files/folders to reorganize.
  • Ensure your role allows create/rename/move operations.

Steps

Section titled “Steps”
  1. Audit the current structure in File workspace.
  2. Create top-level folders for stable domains (for example docs, notebooks, data, assets).
  3. Use file-tree context actions to rename, move, duplicate, or delete files/folders.
  4. Apply consistent naming and folder rules across the project.
  5. Reopen core files and confirm they still load correctly.
  6. Use search/outline/navigation panels to verify discoverability after reorganization.
  7. Keep project state/backing behavior in mind when reorganizing private folder-backed vs private browser-backed projects.

Verification

Section titled “Verification”
  • The file tree shows the new structure and naming.
  • Moved/renamed files open without missing-path errors.
  • Navigation and search are more predictable for recurring tasks.

If Something Goes Wrong

Section titled “If Something Goes Wrong”
  • Files seem missing after moves
  • Search by filename and verify destination paths in File workspace.
  • Links/references break after renames
  • Update path-based references and revalidate compile/preview flows where applicable.
  • Organization differs across collaborators
  • Ensure sync completed before teammates continue edits on moved files.
  • Bulk changes are risky
  • Reorganize in smaller batches so you can quickly isolate path regressions.