Jolocky uses the standard shadcn CLI distribution engine. You do not need to install custom binary wrappers or lock yourself into an external ecosystem. Every section is distributed as a multi-file registry package.
Adding Free Sections#
You can add any community or free section directly by passing the public registry URL to the add command:
pnpm dlx shadcn@latest add https://jolocky.com/r/aurora-drift
The CLI executes the following steps automatically:
- Downloads the registry specification from Jolocky.
- Resolves and installs all required NPM packages, such as motion, lenis, or lucide-react.
- Places the component files, sub-components, and custom hooks into their designated project folders.
- Updates your Tailwind CSS variables if the section defines custom keyframe animations.
Adding Pro Sections#
Pro blocks require an active Jolocky Pro subscription license key. You can find your license key in your Member Portal at any time.
Pass your license token using the --token flag when installing:
pnpm dlx shadcn@latest add https://jolocky.com/r/golden-hour --token JOLOCKY-PRO-XXXX-XXXX
Alternatively, you can export your license key as an environment variable in your terminal session to avoid retyping it:
export SHADCN_TOKEN="JOLOCKY-PRO-XXXX-XXXX"
npx shadcn@latest add https://jolocky.com/r/golden-hourIf the token is valid and active, the registry engine unlocks the complete multi-file code tree and copies the files directly into your project.
Multi-File Tree Structure#
Unlike generic component libraries that squeeze complex animations into one monolithic file, Jolocky breaks down complex sections into clean modular structures:
- registry:block: The root section layout and composition file, placed into
components/sections/orcomponents/footers/. - registry:component: Sub-components, interactive trigger items, and overlays.
- registry:hook: Custom animation physics hooks, window scroll listeners, or cursor tracking calculations.
- registry:lib: Utility functions, math interpolations, or WebGL vertex and fragment shaders.
Overwriting Existing Files#
If you have modified a local section and want to pull the latest upstream version from Jolocky, use the --overwrite flag:
pnpm dlx shadcn@latest add https://jolocky.com/r/aurora-drift --overwrite
Previewing Changes Without Writing#
To see what files and dependencies a Jolocky section will add before making changes to your repository, run the command with --dry-run:
pnpm dlx shadcn@latest add https://jolocky.com/r/aurora-drift --dry-run