The Listener A remix starts a new draft from a published build, carries over selected setup details and credits the original. Add your own content and explain what changed before submitting it for review.
Why it matters
A remix records how your project relates to an existing build. It gives readers a route back to the source while leaving you room to document different parts, construction or results. The original author's page remains separate from your draft.
The starting details save some setup work. They do not make a finished Showcase or Build Guide. Your photos, explanation and remix note need to show what you made and how it differs.
How it works
Sign in and use Create remix on an eligible published build. The new build belongs to you and starts as Draft. Its initial title is the source title followed by “(Remix)”. It gets its own address from its own title.
The draft carries over these details from the published source:
- Categories, tools and skills.
- The project status and the Build Guide's presence and guide level.
- The saved bill of materials.
- The published guide licence, including its custom name and terms when applicable.
- A reference to the original build and a record of its source licence.
It does not copy the body text, photos, build steps, downloadable resources, measurements, system diagram, journal updates, reviews or statistics. Check the carried-over bill of materials against your version, then add the parts and nodes your own diagram needs.
In your editor, complete What did you change?. This remix note is required before the build can enter review. The field allows up to 1,000 characters. Name the differences directly: the drivers you changed, the smaller cabinet you built, or the crossover you revised. Explain the change rather than repeating the source title.
The public remix shows a link to the original build, its author when available, and your remix note. The link preserves the source credit; the note tells readers what to look for in your version.
What to check
Read the source licence before starting. Bassilisk blocks public remix creation for licences that do not permit it, including personal-use-only and all-rights-reserved selections. With custom terms, read and acknowledge them before creating the draft. Acknowledging them does not replace reading them.
Access and permission are separate checks. Being able to read or buy a guide does not automatically make its remix action available. See Licences for guides and files for the distinction between access and permitted use.
Check the inherited project status and guide level against your own work. A source marked Finished does not mean your new project is finished. A copied Full guide selection does not supply the missing instructions. Set those choices to match the content you actually provide.
Write your Showcase and any Build Guide content, add your own supporting files, and inspect the source credit and remix note before submission. The new draft follows the normal build-review process.
Common mistakes
- Expecting the source's photos, guide steps or diagram to appear in the new draft.
- Leaving the inherited status and guide level unchanged when they overstate your progress.
- Using the remix note as the whole guide. It explains the differences; the rest of the build still needs its own content.
- Assuming access to a download grants permission to redistribute it in your remix.
Related
- Showcase and Build Guide explains what to write in each editor.
- Draw a system diagram covers parts, nodes and connections.
- Publish your build covers submitting the finished draft.