hub

A multi-app workspace for your Solid pod. Profile, Files, Calendar, Contacts, Notes, Tasks, Photos — all stored as JSON-LD on a pod you own.

The UI is the Linked Objects Hub demo, wired to real data via xlogin + JSON-LD CRUD. Tasks discover trackers through your solid:publicTypeIndex (same convention as pilot and SolidOS' tracker-pane); other apps default to /hub/ on your pod and can be moved by editing your TypeIndex.

Live: https://solid-apps.github.io/hub/

Status: early — read paths solid, write paths exercised but not exhaustively tested.

Stack

• Vanilla JS, ESM modules, no build step
• xlogin for Solid OIDC auth (DPoP-authenticated fetch via window.xlogin.authFetch)
• Pod requirement: serves application/ld+json via content negotiation. Turtle-only pods aren't supported yet.

Running locally

python3 -m http.server 8080
# or any static file server, e.g.
npx serve .

Open http://localhost:8080/. Click the floating Login button (xlogin) to sign in to your pod.

Apps

App	Status	Pod path	Vocab
Home	dashboard	(synthesized)	—
Profile	read+edit	WebID document	foaf, vcard
Files	browse	/hub/files/	LDP
Calendar	read+edit	/hub/calendar/	ical
Contacts	read	discovered from WebID	foaf
Notes	read+edit	/hub/notes/	schema.org TextDocument
Tasks	read+edit	/hub/tasks/list.jsonld	wf:Tracker (SolidOS #1)
Photos	browse	/hub/photos/	LDP, schema.org
Activity	feed	(synthesized)	—
Settings	UI	/hub/prefs.jsonld	hub: namespace

Pane convention

Apps own chrome and discovery; per-subject rendering is delegated to panes. A pane is a small module:

export const meta = { id, name, forClass };          // optional, for debugging

export function canHandle(input) { /* boolean */ }   // input: { url, doc, forClass }
export async function render(input, container, ctx); // emit DOM into container

Built-in panes live under src/panes/. To plug in a new one:

import { register } from './panes.js';
import * as MyPane from './panes/my-pane.js';
register(MyPane);

Apps look up a pane per discovered subject via findFor(input). The first registered pane whose canHandle returns true wins, so registering an external pane before the built-in one swaps the renderer without touching the app shell.

Three options for the Tracker pane

To make pane evolution concrete, hub ships three ways to render wf:Tracker:

1. Default — src/panes/tracker.js: hub's own copy, vendored byte-for-byte from pilot's tracker-pane.js. Will evolve here independently of pilot. LOSOS-shape exports are wrapped via adapt() at register time so the registry sees a hub-shaped pane.
2. Toggle in Settings → Panes: registers src/panes/pilot-tracker.js first, which lazy-loads https://solid-apps.github.io/pilot/tracker-pane.js at runtime. Useful for comparing hub's diverging copy against the upstream.
3. Per-registration urn:solid:view (described below): pin a specific tracker to a specific renderer URL on your pod. Highest priority — wins over both 1 and 2.

External Preact panes (the toggle, and the urn:solid:view loader) work because index.html ships a tiny importmap for preact / preact/hooks / htm. Hub's own modules are pure ESM and don't depend on it.

Per-registration override via urn:solid:view

A TypeRegistration can pin its preferred renderer with the urn:solid:view predicate (term in urn-solid registry, owl:sameAs http://w3id.org/solidos#view):

{
  "@context": {
    "solid": "http://www.w3.org/ns/solid/terms#",
    "view":  "urn:solid:view"
  },
  "@id": "#reg-tracker",
  "@type": "solid:TypeRegistration",
  "solid:forClass": { "@id": "http://www.w3.org/2005/01/wf/flow#Tracker" },
  "solid:instance": { "@id": "...todo-data.jsonld#this" },
  "view":           { "@id": "https://solid-apps.github.io/pilot/tracker-pane.js" }
}

When present, hub-pod loads that ES module and uses it instead of the built-in pane. Both hub-style (canHandle(input) + render(input, container, ctx)) and LOSOS-style (canHandle(subject, store) + render(subject, store, container, rawData)) exports are supported — the resolver auto-adapts. The choice lives on your pod, so it travels with you across browsers and is interoperable with any other Solid client that honours the same predicate.

License

AGPL-3.0-or-later.