Publishing to dalea.market
From workspace template to public package, with versioning.
Once a template is stable in your workspace, you can publish it as a package on dalea.market so other teams (in your org or in the wider community) can install it.
Templates are one of four package types you can publish:
| Type | What it is |
|---|---|
| Template | A reusable document blueprint, with optional locking. |
| Block | A single block (e.g. a configured 96-well plate, a complex chart) reusable across documents. |
| Environment | A data schema — tables, columns, naming schemes — without rows. Shared as a starting point for studies that need the same shape. |
| Bundle | Multiple of the above, shipped together. Common pattern: an environment plus the templates that write into it. |
Scopes — your namespace on dalea.market
Every package on dalea.market lives under a scope, written @scope/name.
Scopes are like npm namespaces:
- Personal scope (@your-handle)
- Created automatically when you join dalea.market. Only you can publish under it. Useful for personal templates and experiments.
- Organisation scope (@your-org)
- Created when an org first publishes. Members with publishing rights publish under it. The org name is unique on the marketplace.
Org scopes are the right choice for shared institutional templates (your IACUC template, your standard ELISA SOP, your cell-line registration form). Personal scopes are right for individual contributions and experiments.
Permissions
To publish under an org scope you need the publish permission on the org. Owners and admins have it by default; org admins can also assign a custom "publisher" role to specific members.
To publish under a personal scope you need only your own account.
The publish flow
- Open your template in the workspace
Templates → pick the one to publish.
- Click Publish to dalea.market
A dialog opens.
- Pick a scope
Choose between your personal scope (
@your-handle) and any org scopes you can publish under. If your org isn't listed, ask its admin to grant you publish rights. - Set package metadata
- Package name — kebab-case, unique within the scope (
iacuc-submission-acme). - Display name — what users see (
IACUC submission — Acme institutional). - Description (short and long) — short shows in search results; long is the full package page.
- Tags — things like
iacuc,protocol,in-vivo,mouse. Up to 10. - License — pick from a dropdown (MIT, Apache-2.0, CC-BY, Proprietary).
- Homepage / repo — optional URLs for documentation or source.
- Package name — kebab-case, unique within the scope (
- Set version
Default is
1.0.0. Use semantic versioning: bump the third number (patch) for fixes, the second (minor) for non-breaking additions, the first (major) for changes that break documents that already use the package. - Add a changelog (optional but recommended)
A short summary of what's new. Markdown allowed.
- Publish
Dalea uploads the package and registers it on dalea.market. Within a few seconds it's discoverable on the public catalog and via in-product package search.
After publishing
Each published version is immutable. To "edit" a package you publish a new version (1.0.1, 1.1.0, 2.0.0…). Old versions stay listed and remain installable until you yank them.
Maintenance you'll do over time:
- Updates — publish new versions as your template evolves. Update the changelog so consumers know what changed.
- Reviews and discussions — community members can leave 1–5 star reviews and start discussions on your package page. Respond promptly; high-quality packages have engaged maintainers.
- Stars — track which versions are popular. Useful signal for what to invest in.
- Deprecation — flag a package as deprecated with a message ("Use the newer @your-org/iacuc-submission-acme-v2 instead"). Existing installs keep working but new discovery is gated.
- Yank — pull a specific version if it has a serious bug. Existing installs of that version are warned; the version stays in history but no longer installs.
A realistic example
Your institution wants every research group to use the same IACUC template:
Scope: @acme
Name: iacuc-submission-mouse
Display name: IACUC submission — mouse studies (Acme institutional)
Tags: iacuc, protocol, in-vivo, mouse, regulatory
License: Proprietary
Homepage: https://wiki.acme.com/iacuc
Description: Acme's institutional IACUC submission template for mouse
studies. Pre-filled with our reviewer language; structure
and default text are locked. Editable form fields cover
study justification, animal counts, route-of-administration.
Publishing this once means every new programme inside Acme starts the same way. When the institutional language changes, you publish v2 — every team gets a prompt to migrate.
Tips
A bundle is the right shape when a template only makes sense alongside its
environment. Example: the cell-line registry bundle ships an
environment (Cell lines table with STR, authentication, freeze
locations) plus the registration template that writes into it. Installing
the bundle gets users both pieces in one click.
Anything you publish under your personal scope is visible on dalea.market. For internal-only sharing between workspaces in the same org, use workspace-to-workspace template duplication instead — see your org admin.