Ceramics Studio

Ceramics gets more intelligible when clay body, glaze, and firing are recorded together instead of as separate memories. The makers who improve quickly usually keep the failures as carefully as the wins because the defects teach just as much about the system.

Three signals I would keep in view:
- Ceramics practice gets easier to improve when makers record clay bodies, glaze combinations, and firing conditions together.
- Studio learning compounds when test results are saved in a way that others can actually reuse.
- A good ceramics library balances inspiration with technical notes that explain outcomes.

Read first:
- Digitalfire: digitalfire.com/
A superb public reference for glaze chemistry, bodies, and ceramic processes.
- Glazy: glazy.org/
A shared glaze database that is most useful when paired with disciplined studio notes.

Documents worth saving:
- Glazy: glazy.org/
An unusually useful public resource for glaze reference, surface ideas, and recipe notes.
- AMACO lesson plans and resources: amaco.com/educators
Solid educational downloads that work well as saved references inside a folio.

If this post is useful, the next contribution should add a real example, a worked document, or a failure case someone else can learn from.

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.

Three metrics worth pressure-testing:
- success rate of repeated glaze combinations
- time saved by reusing firing logs
- reduction in recurring defects after documenting test results

Source material behind the scorecard:
- Digitalfire: digitalfire.com/
A superb public reference for glaze chemistry, bodies, and ceramic processes.
- Ceramic Arts Network: ceramicartsnetwork.org/
A broad public resource for technique, studio practice, and project ideas.

If your team has a sharper dashboard, share the metric definitions and the decisions they actually change. That is what makes numbers reusable.

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 stack categories worth comparing here:
- glaze test and recipe journals
- firing schedule references
- studio workflow and defect checklists

Open materials worth opening side by side:
- Glazy organization: github.com/glazyorg
A useful starting point if you want to inspect or extend the open tooling around glaze data.
- Digitalfire: digitalfire.com/
A superb public reference for glaze chemistry, bodies, and ceramic processes.

Working documents and guides:
- Glazy: glazy.org/
An unusually useful public resource for glaze reference, surface ideas, and recipe notes.
- AMACO lesson plans and resources: amaco.com/educators
Solid educational downloads that work well as saved references inside a folio.

Firing log:

firing:
  clay_body:
  cone:
  kiln:
  glaze_layers:
    - name:
      coats:
  result:
    color:
    surface:
    defects:
  next_test:

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.

A sequence I would actually hand to a teammate:
1. Document the clay body, form goal, and intended firing range before starting.
2. Track trimming, glazing, and test tile observations while the project is still in progress.
3. Finish with kiln results, defects, and changes to try on the next firing cycle.

Useful operating references:
- Glazy: glazy.org/
A shared glaze database that is most useful when paired with disciplined studio notes.
- Glazy organization: github.com/glazyorg
A useful starting point if you want to inspect or extend the open tooling around glaze data.

If your team has a better workflow, post it with the context around team size, constraints, and exactly where the process tends to break.