Files and resources in a Build Guide

Add resources to your Build Guide as uploaded files or external links. Give each resource a clear title, category and version, then check its licence and access requirements before submitting your build.

Before you start

Open your build's Build Guide editor. Prepare the files another builder needs, such as a cabinet drawing, printable part, project archive or measurement export. Use a description to explain which part of the build each resource belongs to.

Each uploaded resource can be up to 50 MB. Supported extensions are STL, 3MF, GCODE, F3D, BLEND, STEP, DXF, PDF, ZIP, 7Z, DSPPROJ, DSP, XML, MDAT, TXT, CSV, JPG, JPEG, PNG, WEBP and SVG. The resource category does not expand this list.

Use an external link when the resource belongs on another site. It must be a complete HTTPS address. This points readers to the source; it does not upload a copy to Bassilisk.

Steps

1. Find Files & resources and choose Add resource. Choose Upload a file or Add an external link for the resource you are adding.
2. Enter a title that tells a builder what the resource is. Select its category: 3D model, CAD / technical drawing, Documentation, Project archive, Firmware / software, Measurements or Other. Describe the contents and any detail needed to pick the right file.
3. For an upload, choose the file and check the displayed filename, format and size. For an external link, enter the HTTPS address and check the detected provider. You can name the provider when the site is not recognised.
4. Fill in Version when a revision matters. Use a label that matches the file or release you are sharing. The field records the revision; changing that label does not replace the uploaded file. Include the revision in the title or description when readers need to distinguish it.
5. Check the resource's licence. It can inherit the Build Guide licence or use a different one. An external resource can also leave its licence with the source. Read Licences for guides and files before choosing.
6. To update an existing upload, use Replace on that resource. Check the new filename and update the version label to match. Review the description and licence if the replacement changes either.
7. Save the Build Guide. Submit the build for review when its files and instructions are ready. Follow Publish your build for a new build or changes to an already published one.

What happens next

Readers see the approved resources with their titles and descriptions. Uploaded resources show file information; external resources identify the website and open in a new tab. Saving a replacement does not immediately replace the approved public build.

Downloading a file stored on Bassilisk requires sign-in. Further access requirements depend on the build's active access policy. Members access requires sign-in; paid access requires a valid entitlement. New Members and Paid policies protect files and resources, while older policies can cover more of the guide. Follow the access message on that build.

An external website controls access to the file it hosts. A licence describes permitted use; it does not grant access through a sign-in or purchase requirement.

Common mistakes

• Adding a resource with a vague title and leaving readers to guess which revision it contains.
• Changing the version label without replacing the file, or replacing the file without updating its description.
• Assuming a public Showcase makes every download available without signing in.

Related

• Showcase and Build Guide explains where resources belong.
• Share measurements on your build covers measurement charts and capture details.
• Keep a build journal explains how to tell readers about a new file revision.