Forma pillar

What the Guild can make

Every design operation and every workshop capability is one of the names below. It is one list because both sides have to be comparable - and it is Forma's, because "laser cutting" and "lasercut" cannot be two different answers to one question.

This is a making list, not a printing one: routing, cutting, bending, welding, coating, upholstery, finishing and assembly are the same kind of row, and a workshop claims whichever it actually runs. The ids in mono are what a manifest carries and what routing compares. 9 processes and 6 materials today - see which of them the Guild actually covers near you.

Processs

  • CNC routingcnc_router
  • Laser cuttinglaser_cut
  • Tube bendingtube_bending
  • MIG weldingmig_welding
  • TIG weldingtig_welding
  • Powder coatingpowder_coating
  • Upholsteryupholstery
  • Finishingfinishing
  • Assemblyassembly

Materials

  • Birch plywoodbirch_plywood
  • Maple plywoodmaple_plywood
  • Solid oakoak_solid
  • Steel sheetsteel_sheet
  • Steel tubesteel_tube
  • Wool fabricwool_fabric

Something you make has no name here?

Ask for it. A workshop proposes what it runs; a designer asks for the name a design needs - the queue does not care which you are. Every ask is recorded as one voice for that name, Forma's operators read the queue, and every voice for the same capability counts. An accepted ask enters the vocabulary in a release, because a process is code and reference data rather than a row somebody inserts - and the decision comes back onto this page, under your asks.

Sign in to ask

A request belongs to an account, so a decision has somewhere to come back to - reading the list needs no account at all.

The list belongs to the platform, not to a workshop: it is what makes a claim and a requirement the same kind of statement. If you are opening a workshop, the join flow asks you to claim from it; if you are publishing a design, its manifest declares from it too.