Logo
NeoArc Studio

Offline Workflows

NeoArc works without an internet connection. Learn how to create and edit documentation offline, then sync your changes when connectivity returns.

NeoArc Studio works entirely with local files. No cloud dependency for editing. No server required for creating content. This architecture means you can work offline: on aeroplanes, in remote locations, during network outages. When connectivity returns, sync through Git.

Why Offline Matters

Traditional documentation tools require constant connectivity.

Traditional ToolsNeoArc
Every keystroke sends data to a serverAll content lives in files on your machine
Opening a page requires a network requestThe application reads and writes locally
Network lag affects editing responsivenessNo network latency
Outages mean no access to documentationFull access regardless of connectivity

Working Offline

Before Going Offline

Prepare your workspace while you have connectivity.

Creating Content Offline

All NeoArc features work offline.

Create Pages
Create new pages and diagrams
Edit Content
Edit existing content
Add Blocks
Add content blocks
Preview
Preview pages in the viewer
Save Changes
Save changes to local files
Auto-Save
Auto-save continues to work

Git Operations Offline

Git itself is designed for offline work. While offline, you can perform these operations.

Syncing When Online

Push Your Changes

When connectivity returns, push your local commits to the remote repository.

git push origin my-branch

Pull Remote Changes

Others may have pushed changes while you were offline.

git fetch origin
git merge origin/main

# Or pull directly to fetch and merge:
git pull origin main

Handling Divergent Changes

If both you and others made changes while you were offline, you may need to merge.

Offline Scenarios

What Requires Connectivity

Some operations do need network access.

OperationRequires Network
Publishing to cloudYes - Uploading to Azure or other cloud storage
Git remote operationsYes - Push, pull, fetch, clone
CDN purgeYes - Clearing Cloudflare cache after publishing
Core editingNo - Fully offline

Local-First Benefits

Beyond offline capability, file-based storage provides additional benefits.

Speed
No network latency when editing
Privacy
Content stays on your machine until you push
Control
You decide when to sync
Resilience
No single point of failure

Best Practices

This documentation was written using NeoArc Studio's offline-capable architecture. The same workflow applies to your own documentation projects.

Next Steps

Docs as Code
The philosophy behind treating documentation like code
Learn more →
Branching Strategies for Documentation
Git branching patterns suited to documentation workflows.
Learn more →
Handling Merge Conflicts
Resolving conflicts after syncing
Learn more →