Back to News

Generated artifact folders are reserved for automation

Project pages now expose stable target paths for schematics, firmware bundles, and mechanical exports published by other repositories.

Apr 7, 20264 min readMaintainers
automationgithub actionsartifacts

The convention is now explicit

Each project page publishes the expected folder targets for board-dimensions, code, data-sheets, datasheets, and schematics.

That makes it straightforward for another repository to push outputs into the docs site during a release workflow.

No frontend rewrite required

Because the paths are part of the project model, adding real files later does not require new routes or hand-edited pages. The site just starts serving the generated content as soon as it lands in public/generated.