> ## Documentation Index
> Fetch the complete documentation index at: https://docs.shipyard.lol/llms.txt
> Use this file to discover all available pages before exploring further.

# ShipSpace basics

> Understand the core ShipSpace objects before you start planning work.

ShipSpace organizes product work around workspaces, issues, and shared context. Start with the smallest structure that reflects how your team already works, then add more detail as your workflow becomes clearer.

<Columns cols={2}>
  <Column>
    <Card title="Workspaces" icon="boxes">
      A workspace groups related projects, issues, teammates, and knowledge. Use separate workspaces when teams need different visibility or priorities.
    </Card>
  </Column>

  <Column>
    <Card title="Issues" icon="list-checks">
      Issues track the work itself: status, priority, ownership, discussion, and handoff into ShipCode.
    </Card>
  </Column>

  <Column>
    <Card title="Company Knowledge" icon="book-open">
      Company Knowledge gives Leo and connected tools durable context about your product, team, decisions, and workflows.
    </Card>
  </Column>

  <Column>
    <Card title="Messages" icon="message-circle">
      Messages keep collaboration close to the work so teammates can discuss decisions without leaving ShipSpace.
    </Card>
  </Column>
</Columns>

## How the pieces connect

<CardGroup cols={2}>
  <Card title="From issue to implementation" icon="arrow-right">
    Issues collect the planning context that ShipCode needs when work is ready to build.
  </Card>

  <Card title="From discussion to memory" icon="brain">
    Important decisions should be captured in issue details or Company Knowledge so Leo and teammates can reuse them later.
  </Card>
</CardGroup>

## Keep the first setup simple

<Steps>
  <Step title="Create one workspace">
    Start with one workspace for the product or team you want to manage first.
  </Step>

  <Step title="Import or create issues">
    Bring in existing work from Linear or create a few representative issues manually.
  </Step>

  <Step title="Review priorities">
    Confirm imported priorities, owners, due dates, and categories before using the board for planning.
  </Step>

  <Step title="Invite collaborators">
    Add teammates once the workspace structure is clear enough for shared work.
  </Step>
</Steps>

<Note>
  You can revise the workspace structure later. ShipSpace is designed to grow from a lightweight issue tracker into a shared planning layer for your team.
</Note>