Open Collections Desktop getting started

Install from GitHub Releases

1. Open the latest desktop release on GitHub Releases.
2. Download the current Windows installer asset for the release you want to test.
3. Run the installer on Windows and allow it to complete.
4. Launch Open Collections Desktop from the installed app shortcut.
5. On first launch, choose whether to open Manager or Browser first. You can switch between them inside the app.

This preview is intended for evaluation and early workflow testing rather than broad production rollout.

Maintainers should complete the Open Collections Desktop v0.1.0 release checklist and publish the Windows installer on GitHub Releases before public announcement.

What Manager and Browser do

• Open Collections Manager helps you connect a host, prepare collection metadata, and publish updates.
• Open Collections Browser lets you inspect example and hosted collections in a read-focused browsing experience.

The desktop app brings both tools together so you can move between editing and browsing without switching to separate web pages.

Start with example, local, GitHub, or S3-compatible hosts

• Example browsing: start with the built-in example content to learn the layout and the Browser experience.
• Local folder host: use this to test with folders on your own machine and understand the collection structure locally.
• GitHub host: connect a repository-backed host when you want a simple remote publishing target for preview work.
• S3-compatible host: connect object storage when your team already uses S3-style buckets for hosted files.

The preview includes remembered hosts so you can reconnect without re-entering each setup step every time.

Understand the draft, host, and published model

Open Collections Desktop separates work into three practical states:

• Draft: the local working state where you prepare metadata, review files, and make changes before publishing.
• Host: the connected destination such as a local folder, GitHub repository, or S3-compatible bucket.
• Published: the version that has been written to the host and can be opened again in the Browser or shared with others.

This model is helpful in the preview because it makes it clear what is still local work, what is connected, and what has actually been published.

Reconnect basics

If you reopen the app later, remembered hosts and reconnect flows help you return to your previous work more quickly.

• Use the host list to reopen a previously connected local, GitHub, or S3-compatible destination.
• If a connection needs attention, confirm the host details and credentials, then retry the reconnect flow.
• The desktop credential storage path is part of this preview so credentials can be reused more consistently between sessions.

Known limitations

• registry browsing is not included yet
• custom domain hosting is not included yet
• full sync/conflict-resolution workflows are not included yet
• some host repair and reconnect flows still need broader real-world validation

Feedback

For this preview, please send questions, bug reports, and workflow feedback through GitHub Issues.