12. The Content Library (factory sounds)

The Content Library repository is the factory sound vault: the presets, drum kits, one-shot samples, loops and demo projects that ship with Nebula so there is something to play with on day one, without you having to make every sound yourself first.

Status today: a skeleton. The folder structure, file-naming rules and the licensing ledger exist and are enforced; the real factory sound packs are still being produced and added.

How it is organised

Folder	Holds
presets/	Synth and effect patches (.nebpatch, .nebpreset)
kits/	Drum Rack kit manifests (.nebkit)
one-shots/	Single-hit samples — drums, bass stabs, foley, sound effects
loops/	Tempo-synced audio loops (rhythms, grooves, arpeggios)
demo-projects/	Whole, playable song projects and starter templates (.nebproj)

Every item follows a consistent naming pattern (role, descriptor, and — for loops — tempo and key) specifically so the sounds can be searched and filtered instantly by category, tempo, key and character, both in Nebula's own browser and by any tool reading the library directly. A machine-readable index.json catalogs everything for exactly that purpose.

Licensing: everything is CC0

Every single asset in the Content Library is dedicated to the public domain (CC0-1.0) — no royalties, no fees, no attribution requirement, ever, for anything you make with them, commercial or not. Anything imported from a third party must have documented, verified CC0 provenance before it is added, and every file is recorded in the repository's own licensing ledger with its origin, author and the date it was checked. This is a deliberate, strict policy, not a default license choice made by accident — it exists so nobody who builds something with Nebula's factory sounds ever has to wonder whether they are allowed to.

Using it

The Content Library ships alongside Nebula itself (see chapter 1 for where Nebula looks for sounds on your machine); most people never need to think about this repository directly. It is public and versioned separately mainly so its licensing ledger and provenance records stand on their own, and so contributors can propose new CC0 content through the normal pull-request path.