Guides hub
Practical guides for third-party compatibility literacy
Notes you can skim before citing a program or sharing a mechanic publicly.
Track which program PDF, which attribution line, and what you marked closed. That trail is the craft.
Session zero for powered-by / third-party compatibility literacy
Agree which program PDF you cite and what stays out of scope before anyone pastes a logo publicly.
Clocks, resources, and pacing
Citation hygiene is the clock: primary license first, trademark check second, attribution third.
NPC and faction sheets that stay small
Keep compatibility notes thin: program name, PDF date, out-of-scope list. No invented seals.
Teaching the table without a lecture
Walk one primary license page together. Glossary for powered-by marks; then verify a cite.
One primary license link, one trademark check, one attribution reminder—before you paste a logo.
Primary license pages, trademark/copyright overviews, and named publisher terms beat anonymous permission myths.
Date which program PDF you checked and what you marked as out of scope. Co-authors need a trail.
Guides for literacy; Glossary for powered-by vocabulary; Resources for primary doors. Then verify the cite.
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.