Last Updated: 4/30/2026

Jolli Spaces

A Space is where documentation lives in Jolli. You bring your existing docs in (or generate them from code); the AI Assistant and Gap Analysis keep them in sync as the code changes; every edit passes through review before going live; when you’re ready to share, you publish a Jolli Sites from the Space.

What lives in a Space

• Articles. The core unit of content. Markdown by default; JSON content type for OpenAPI specs.
• Folders. Group Articles. Nestable, drag-and-drop.
• Sources. External inputs (GitHub repos) the AI reads to import, generate, and detect drift.
• Changesets. Edits the AI Assistant or Gap Analysis proposes, plus chat edits from the Agent Hub.
• The AI Assistant. Lives in the Agent Hub tab. See Editing.

Sorting and filtering

The controls above the Article tree let everyone browsing the Space narrow what they see:

• Sort - Default (the Space’s manual order), Alphabetical, Last Updated, or Created. Each has ascending/descending variants.
• Filters - restrict to Articles updated in a window (Today / Last 7 days / Last 30 days / Last 3 months / a custom date) and/or by creator name.

Who Spaces is for

Teams and individuals. On signup, Jolli creates a Personal Space for you so you have a place to work right away. Create additional shared Spaces when you want to collaborate.

Onboarding

On first sign-in, Jolli opens the AI Assistant with guided walkthroughs. The most common is to create a new space with your existing documentation. You can import your documentation in these ways:

• A GitHub repo with Markdown files.
• A public GitHub repo URL (no authentication needed).

Once submitted, Jolli will create a new Space and provide options such as creating a site from your space.

What the import does

For a typical docs folder (dozens of files), expect a few minutes. The Agent:

• Preserves your folder structure where it makes sense.
• Self-hosts images so your Site doesn’t depend on the source repo.
• Rewrites broken internal links using the import’s source mapping.
• Flags unsupported formats (RST, AsciiDoc, Textile) with their paths and skips them.

Imports land directly in the Space - no Changeset review on the import itself. Edits you make later from the Agent Hub chat (and AI-proposed updates from Gap Analysis) do flow through Changesets.

Sources

A Source is where a Space pulls external content from.

Sources drive three things: the initial import, ongoing Gap Analysis drift detection, and optional Generate from code. See Editing for more details.

The two-layer model

Sources live at the workspace level, not per-Space. One connected Source can feed any number of Spaces.

1. Workspace Sources - managed at Settings → Sources. A GitHub App installation is one row at this level.
2. Space Sources - each Space picks which workspace Sources it consumes from Space Settings → Sources.

Connect once; link from any Space.

Connecting

GitHub App. Settings → Sources → Connect Source → GitHub App routes you to GitHub’s install page. Pick the org and repos (All repositories or Selected). If your org admin needs to approve third-party apps, they review the read-only permissions before allowing.

Public GitHub repo. Settings → Sources → Connect Source → Public GitHub Repo. Paste the URL.

Once connected, link a Source to a Space under Space Settings → Sources → Add sources.

Sync

Connected Sources stay live. Two modes per Source:

• Webhook events - near-real-time, default for GitHub App Sources.
• Scheduled polling - for cases where you’d prefer suggested changes be aggregated.

Tracked branch (and which repos a GitHub App can see) is configurable per Source under Settings → Sources → Configure. The choice between webhook-driven and scheduled sync lives per Space under Space Settings → Automation, because the same Source can feed multiple Spaces with different cadences.

Source statuses

• Connected - working normally.
• Needs Attention - usually a lapsed permission or auth issue. Click in to see the cause.

Each Source’s menu has Manage (which Spaces use it, recent activity), Configure (tracked branch, sync mode), and Disconnect (removes from the workspace; previously imported Articles stay in their Spaces).

Generate from code

If your repo has no existing docs, the AI Assistant can write Articles directly from the codebase. You can also trigger it later from the Agent Hub by asking the AI Assistant to generate docs for a specific part of a connected Source.

Generate is slower and more variable than Import - output quality scales with how well-commented the code is and how clear module boundaries are. If you have any existing docs, even rough Markdown READMEs, Import is faster and more reliable.

Next steps

• Editing - the writing surface, the AI Assistant, Changesets, Gap Analysis.
• Jolli Sites - publish the Space at a URL.