Skip to content

Store and Community

Jump to bottom
Bobby Comet edited this page Aug 6, 2026 · 3 revisions

Store & Community

In-app Store tab

The Store tab discovers and installs Conky themes from two sources:

Sub-tab Source How it works
Community Static index.json feed You set an Index URL (default points at the project’s placeholder). Browse loads the manifest; pick a theme and Install.
OpenDesktop / Pling Live OCS API Search Pling or openDesktop, preview metadata/downloads, then Install theme.

Installed themes land under ~/.config/conky/ (or the configured install root). Use the Manager tab to launch them.

If a sub-tab looks empty:

  • Community — no public community index is required by default; point Index URL at your own index.json (see the Community Store section in the README / packaging template).
  • OpenDesktop / Pling — needs network access. Prefer Pling; openDesktop uses api.opendesktop.org (the old www.opendesktop.org/ocs/v1/ host returns HTTP 410 and is not used).

Community store (static index)

The Community panel talks to whatever static index.json a host publishes (GitHub raw, CDN, etc.). Entries include name, author, version, description, tags, download URL, and optional sha256 for integrity before install.

Typical content kinds:

Kind Who it’s for
Built themes End users who only need to run a HUD
Project JSON + assets Authors who want to remix graphs in Studio
Plugin packs Extra logic/visual nodes (JSON + Lua)
Art / image packs Assets referenced by Image nodes or wizard themes

Preferred public packaging:

  1. Primary: built theme folder (or .zip / .tar.*) with start.sh / conky.conf — runs without Studio
  2. Optional: project JSON for remixing, plus plugin list and asset paths documented

See Sharing Projects.

OpenDesktop / Pling (OCS)

Live search uses the OCS content API:

  • Pling: https://api.pling.com/ocs/v1/
  • openDesktop: https://api.opendesktop.org/ocs/v1/

Search defaults to conky if the query is empty. Results that look Conky-related are marked with ★. Selecting an item loads full details and download links; Install theme downloads, unpacks, detects a theme root (conky.conf, .conkyrc, start.sh, theme.json, render.lua, …), and copies it into the install root.

View on site / Open website open the system browser for catalog pages. That hand-off is intentional for browsing and account flows; Studio still owns local install.

ocs:// links

If Conky Studio is registered as the handler for ocs:// / ocss://, browser “Install” links can open the app and install directly. Secondary instances can forward URLs to a running Studio via the local OCS server. Packaging notes for MIME/scheme registration are in the OCS handler helpers. It will also install a minimal start.sh to run the theme.

Limitattions

  • If it is a collection, it may still install a start.sh, safely delete it if not needed.
  • If a theme is broken, this will not fix it
  • Does not install dependencies if a theme has some

Discord & videos

Also available from Help → Support in the app.

Trust and safety

  • Treat downloaded themes and plugin packs like any script you run: Lua and shell execute under your user in Conky’s process
  • Prefer known authors and reviewed packs
  • Prefer built themes from strangers if you only need to run a HUD and are not auditing a graph
  • Community index entries may include sha256; a mismatch aborts install

Contributing content

  • Themes: export a clean build; include README and theme.json when useful
  • Community index: follow the index schema and community-repo template (layout + optional CI validation)
  • Plugins: follow the Plugins authoring rules; PR or publish a manifest JSON
  • Pling / openDesktop: publish on those sites so OCS search can find the item
  • Report import/preview issues with Studio version, distro, X11/Wayland, and Conky version (Tools → Hardware & Session helps)

Clone this wiki locally