Projects and Things
Understand repositories, physical parts, assemblies, and revisions.
Projects hold the design
Projects open at the current commit of their default branch; publishing a release is optional. A project is a Git repository and its collaboration space: files, README, Things, issues, pull requests, and releases. Public projects appear in discovery and profile pages immediately, even without a release. Private projects are restricted by project access controls.
Things describe physical objects
A Thing can be a PCB, populated board assembly, printed part, fastener, generic component, or assembly. It belongs to a project and connects a physical object to the files that define it. Files such as a schematic are design documents, not necessarily separate manufactured objects.
Assemblies and BOMs
The Thing tree groups assemblies and their children. Open a Thing’s BOM to inspect its components, quantities, references, manufacturer data, and available sourcing information. A Thing can occur more than once in a BOM; its identity is separate from the quantity used in an assembly.
Tabs follow the Thing type
Different types expose different tools. A PCB may have Gerbers and a model view; a PCBA may also have a schematic and BOM. Files and Sourcing connect the design to its source documents and manufacturing options.
Releases preserve context
Use the version selector to switch branches or releases. Links to a release identify a specific snapshot. Check the selected version before reviewing changes, downloading files, or preparing a quote package.