Licenses
Circuit Dessert is open. Copy it, remix it, fork it for your own team, and credit the source. Three kinds of material live here, and they have three different owners.
| What | License | Where it is |
|---|---|---|
| Code: the site templates, build scripts and schematic generators | MIT | LICENSE in the repository |
| Written content and drawings: recipe and part write-ups, tables, guides, our redrawn schematics, and photos that contributors add | CC BY 4.0 | LICENSE-CONTENT.md in the repository |
| Manufacturers’ material: datasheets, application notes, their figures, names and logos | Not ours. It stays with its owner | Linked and credited, never relicensed |
Using the content
Section titled “Using the content”The written content and drawings are under Creative Commons Attribution 4.0. You can copy, share and adapt them for any purpose, including commercial use, as long as you:
- Give credit. Name “Circuit Dessert contributors”, link to the page or the site, and link the license.
- Say what you changed, if you changed anything.
A suggested credit line:
Based on "Page title" from Circuit Dessert(https://circuitdessert.org), CC BY 4.0. Changed: what you changed.There is no share-alike condition. What you build on the content can stay private or go under a license of your own.
Forking for internal use
Section titled “Forking for internal use”Yes, you can fork the repository and run your own internal version.
- Keep the notices. Leave the MIT copyright and license text with the code, and keep the credit on content you reuse.
- You don’t have to publish anything. Your internal designs, parts and notes stay yours.
- Mind other people’s documents. If you add datasheets or other manufacturers’ documents to your copy, their terms apply, not ours. The same goes for anything confidential that you add. Keep it out of any pull request you send back.
What stays with the manufacturers
Section titled “What stays with the manufacturers”A manufacturer’s reference design stays credited to its maker. Our write-ups are in our own words, our drawings are redrawn, and every page links to the original. The license on this site covers our words and drawings. It does not cover the circuit, the specifications or the figures the manufacturer published.
Datasheets and application notes are linked, not copied or hosted here. Some carry their own terms or a confidentiality marking, and our pages say so when they do. Check the source before you rely on a document commercially. Manufacturer and product names are trademarks of their owners and are used only to identify parts.
A recipe’s own license
Section titled “A recipe’s own license”Some recipes describe a design whose author shares its files (schematic, layout, firmware) under a license of their own. Those recipes show a Design license under the title. It covers the files the author published, not the write-up on this site, which is CC BY 4.0 like the rest of the content. A recipe for a manufacturer’s design shows no design license, so see the source.
Contributing
Section titled “Contributing”By opening a pull request you confirm that:
- you wrote the material, or have the right to share it;
- you license written content and drawings under CC BY 4.0 and code under the MIT license;
- you keep your own copyright, and your name stays on your commits and in the page’s byline.
Don’t submit text or figures copied from a datasheet, or photos you didn’t take. A CC license can’t be withdrawn from people who already have the material, so think before you submit. See Bring a circuit to the table for how contributions work.
No warranty
Section titled “No warranty”The designs here are documentation, not tested products, and can contain errors. Each recipe lists what has and hasn’t been checked. Build at your own risk. Mains-voltage circuits can kill. Both licenses disclaim any warranty.
Written content and drawings: CC BY 4.0 · Code: MIT · Manufacturers' documents, designs and trademarks belong to their owners · License details