Your homebrew, as content the app understands
ProMost homebrew lives in a document. The party's custom spell is a paragraph someone pastes into chat, and no sheet knows it exists. Content packs are the other thing: your material, in the same shape as the SRD content that ships with RollQuest, so it lands on sheets, rolls its own dice and works the way the built-in content works.

Start from a blank page, or from someone else's
Authoring opens with a straight question: how do you want to begin. You can start an empty pack and fill it, or you can fork - take the rows you want out of an existing pack and pull them into one of your own.
A fork is a transform, not a copy. The rows are re-keyed on the way across, and every reference that pointed at an old identifier is rewritten to point at your new one. That matters because it's what makes the result genuinely yours to edit: you get a working starting point rather than a pile of links back into somebody else's pack that break the moment they change it. Forking a row you already own verbatim is refused outright, so you can't end up with two of the same thing fighting over an identifier.
The obvious first fork is the SRD. Take the spells you want, rename them, change the numbers, and you have a house-ruled list that still behaves like real content.

Validated before it ships
Packs are checked, and you see the verdict before anything is saved. The validator reports what's wrong and where, so a broken reference or a duplicate key is something you fix at authoring time rather than something a player discovers mid-session when their sheet won't calculate.
Bound to a table on purpose
A pack doesn't leak into every game you run. You bind it to the table that should have it, and where two packs both want to define the same thing, the binding step makes you choose rather than guessing - the routing decisions are a list of choices, never a free-text box, because getting it wrong silently is how content disappears.
Retiring a pack is its own deliberate action, and it is not called deleting. Games that already use it keep working.
Run the same campaign at more than one table
The point of a pack is not the marketplace. It is that a campaign you have built once - the maps, the enemies, the tables, the sheets - becomes a thing you can hand to a second game and run again, without rebuilding it or copying anything by hand. Keep a pack private and it stays yours: bind it to your Tuesday table and your Sunday table, and both get the same material, at whatever pace each group is going.
That is what most packs are for, and private is where most of them stay.
Publish it
A pack can also go to the marketplace for other tables to install. Going public is a deliberate step and packs are reviewed before they get there, so the shop stays worth browsing - private packs need none of that and are available to your own games the moment you make them. Pro accounts can create and publish up to 20.
If your material is a whole system rather than a set of items, it pairs with the sheet designer: build the sheet, define the calculations, put both in the pack, and someone else can run your game without you sitting next to them.
Works with
Sheet designer builds the sheets and calculations a pack can carry.
Game systems and templates is how a system and its packs get reused across campaigns.
Marketplace is where packs are published, found and installed.
Frequently asked questions
Which plan can create content packs?
Pro, up to 20 published packs. Using packs from the marketplace is free on every plan.
Can I base a pack on the SRD?
Yes. Fork the rows you want and edit them. Both SRD spell lists ship with the app, and you can browse them first in the spell reference.
What happens if my pack conflicts with another one?
Binding it to a table asks you to decide, rather than picking for you.
Can I delete a pack?
You retire it. Games already using it keep working, which is why it isn't called deleting.
Do my players need Pro to use my pack?
No. Authoring is the Pro part; playing with the content is not.
Try it
Creating and publishing packs is on Pro. Installing them from the marketplace is free.