- New app, including with a coding assistant: start in sempods-apps-template. Its workflow reads the SDK's AI app-builder guide. A short description of the app is enough to start a useful first draft.
- SDK in an existing React app: follow the complete quickstart.
- Understand the data model: Build your app explains Pods, Contexts and field mapping. Read it when those concepts become relevant.
The hackathon checklist helps after setup. The guides below are references for the task at hand, not prerequisites to read in order.
-
client-sdk: portable Pod requests, OAuth and editing.
-
app-sdk: browser sessions, headless authoring and optional React.
-
app-ui: shadcn/ui components on React Aria, SDK-aware adapters, a router over the app's address model and the theme contract for Tailwind CSS 4.
-
Pod overviews with Contexts on-demand and the copyable overview, one-click and task-with-note recipes.
-
RDF values: readable text, exact terms, dates and web addresses for values a SPARQL read returns.
-
Creation and modification times: instants the standard writes maintain, and lists ordered by them.
-
Resource cards: cards with pictures and dates from every connected Pod, with the source of each value and bounded reads.
-
Neighborhood: the statements around a resource, page by page, with a few examples of other predicates.
-
Public RDF: one explicit, credential-free lookup of an IRI's own RDF document, kept apart from Pod data.
-
TODO example and Node example.
-
0.9.0 release notes (in preparation), the 0.8.0 release notes, the 0.7.0 release notes and the earlier 0.6.0 release notes and template adoption.
- Vision, architecture decisions, contributing and development checks.
- Accepted, partly implemented (remembered Pods, resilient renewal): access and sessions across devices.
- client-sdk and its provenance.
- app-sdk and its provenance.
- app-ui and its provenance.
- Agent instruction map, documentation strategy, issue work, doc review, test review, release and live validation.
The root agent map and documentation scope explain which instructions govern a change. Public plans live in GitHub issues.