paper garnet
Mercs are more DIY than more kit-oriented printers, but this means there's a lot of wisdom that's scattered around. This is one reason, IMO, we encourage folks to visit the Discord server with questions.
We get a lot of requests for:
- What's your build configuration?
- Can you share your slicer settings?
- What file did you use for [x]?
- I have [part]. Is there a guide for how to use it?
Build logs are an ideal place to put this info, but build logs can get pretty social and disorganized. A single documentation site for all builds is infeasible, as well.
I propose a simple registry of builds. Any serial owner may submit a markdown file containing information about their build. The below is a basic example:
# [serial]
Builder: [handle](handle_url)
## Configuration
### Hardware
[steppers, electronics, toolhead, etc.]
### ZeroG
[list of printed Merc, Hydra, etc. versions, where applicable]
### Mods
[list of printed mods & links]
## Guides
[useful guides and videos used in your build process & links]
## Repository
[optional section; links to repo with additional info, e.g. slicer profiles, klipper configs, etc.]
I've tried to strike a balance between a keeping it simple and ensuring the relevant information is inside. The above template is meant as starting point for discussion and should not be considered a finished product.
Implementation is pretty simple. Create a git repo. Add folders for each serial grouping (2.0.x, etc.), then drop the markdown files in there. If each file is named [serial].md, they self-sort. Optionally, readme.md could contain a list of serials, as well. Submission would likely consist of pull requests, though manual addition could also be done by copy-paste.
If time available for maintenance is an issue, a volunteer community member could maintain the repository.
opal island
carmine gulch
wanton walrus