portaljs-connect-ckan
Wire a scaffolded PortalJS portal to a CKAN backend over its API. Generates a tiny server-side fetch client (no runtime dependency) and feeds the /search catalog and /@namespace/slug showcases from CKAN instead of datasets.json. Use when connecting an existing portal to a live CKAN instance instead of a static manifest.
npx skills add datopian/portaljs --skill portaljs-connect-ckan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PortalJS — Connect CKAN ## Overview Connect an existing `portaljs-catalog` portal to a live CKAN backend for the "decoupled / any backend" path. The portal stops reading the static `datasets.json` manifest (and files in `/public/data/`) and instead feeds its two data surfaces — the **`/search` catalog** and the **`/@namespace/slug` showcases** — straight from a CKAN instance's REST API (`package_search` / `package_show`) through a generated fetch client. Output is plain, editable Next.js code with **no runtime dependency** — never `@portaljs/ckan`, whose bundle wires React UI components to React 18 internals and crashes at import under the template's React 19. Pages fetch CKAN server-side in `getStaticProps`/`getStaticPaths`, so the catalog is pre-rendered at build time and the site can still be statically deployed. Run this right after `portaljs-new-portal` to swap a freshly scaffolded portal's sample data over to CKAN. ## Prerequisites - A scaffolded PortalJS portal (see `portaljs-new-portal`) with `package.json`, `pages/`, `datasets.json`, `pages/search.tsx`, and `pages/[owner]/[slug].tsx` present. - A CKAN base URL that is publicly reachable, e.g. `https://demo.dev.datopian.c
- Overview
- Prerequisites
- Instructions
- Output
- Error Handling
- Examples
- Example 1 — Public CKAN demo, no filters
- Example 2 — Restrict the catalog to one organization
- Example 3 — Filter by group and target a specific portal directory
- Resources
What does the portaljs-connect-ckan skill do?
Wire a scaffolded PortalJS portal to a CKAN backend over its API. Generates a tiny server-side fetch client (no runtime dependency) and feeds the /search catalog and /@namespace/slug showcases from CKAN instead of datasets.json. Use when connecting an existing portal to a live CKAN instance instead of a static manifest.
How do I install it?
Run `npx skills add datopian/portaljs --skill portaljs-connect-ckan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From datopian/portaljs, a repository with 2,337 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.