Glossary
Shared language for powered-by / third-party compatibility literacy
Working definitions so your table argues about choices, not vocabulary.
One primary license PDF and one trademark check beat a folder of anonymous 'you can publish' myths.
- Powered-by mark
- Branding that signals compatibility under a program.
- License grant
- What you may copy or reference.
- Prohibited content
- Themes or assets a program disallows.
- Submission portal
- Where some programs require listings.
- Royalty vs flat
- Compensation models vary—read current terms.
- Compatibility logo
- Visual rules for cover use.
- Primary source rule
- Always trust the official license PDF over summaries.
- Community pack
- Fan bundles that may not be commercial.
Keep a one-page reference for house rulings. If a call comes up twice, write it down so the table trusts the process.
Track which program PDF, which attribution line, and what you marked closed. That trail is the craft.
Readable reference sheets and clear links beat pretty PDFs with broken cites.
Date which program PDF you checked and what you marked as out of scope. Co-authors need a trail.
You will not find invented product prices or fake stock counts here. Orientation only: how people learn, where they discuss, which public references stay trustworthy.
Date which program PDF you checked and what you marked as out of scope. Co-authors need a trail.
Related desks in this neighborhood
Play and community siblings (.cc, .org, crate, reforged, store) cover table practice beyond licensing.