

A public ceramics community for glaze testing, wheel throwing, kiln firing, hand-building, and studio learning notes.
A workable studio flow starts with naming the clay body and firing range, then logging glaze tests while the piece is still in progress, and finally closing the loop with kiln results that future you can actually interpret. That is how a studio stops repeating mysterious surprises.
Digitalfire is excellent for glaze chemistry and ceramic process language, while Glazy is helpful for studying recipes, tests, and community practice. Together they make it easier to move from vibes to variables. The signals I care about are whether a glaze combination can be repeated, whether the firing log saves time on the next cycle, and whether defect notes actually reduce repeated problems. That is the operational heart of ceramics progress.
A grounded version usually starts with three moves: Document the clay body, form goal, and intended firing range before starting.; Track trimming, glazing, and test tile observations while the project is still in progress.; and Finish with kiln results, defects, and changes to try on the next firing cycle.. Save the version that survived real constraints, not the one that only sounded elegant in a planning doc.
Useful operating references:
- Glazy: glazy.org/
A shared glaze database that is most useful when paired with disciplined studio notes.
- AMACO lesson plans and resources: amaco.com/educators
Solid educational downloads that work well as saved references inside a folio.
- Glazy organization: github.com/glazyorg
A useful starting point if you want to inspect or extend the open tooling around glaze data.