Template:TissueDB Material Class Table

{{TissueDB Material Class Table}} renders a pointer table on a material class page or super-class page. It lists other material pages and nothing else: no build steps, no quantities, no costs, no fidelity ratings.

It is the material-namespace sibling of {{TissueDB Structure Component Tissues Table}}. That template's headers are hardcoded to Tissue / Layer-Position / Key Properties, so it cannot be reused for a table whose rows are materials. The shell is otherwise identical.

The project owner's definition, verbatim:

"The ONLY difference between a material page and a class page is that multiple material names point to a class page, and on that class page you talk about variations of that material, and a single material page just has a single material and all the links pointing to it say the same name of that material."

So a class page is not a new kind of page. It is an ordinary material page that happens to be the target of several name variants, and which therefore discusses the variations rather than one fixed form. Foam, soft and Plastic Tubing are class pages in this sense.

A super-class sits one level above a class page and carries only a pointer table. The owner's specification, verbatim:

"if someone searches on 'castable' they get to a 'castable materials' that doesn't have a lot of info on it, just a set of links in a table including Silicone, castable, Alginate, PVC Plastisol.... Sort of like a structure page that just points to other tissue pages, this page would point to the sub class pages."

The purpose is findability: someone who searches a property ("castable") rather than a product name should land somewhere that routes them onward. That is why a super-class deliberately has little content of its own. Adding build detail to one would defeat the point and duplicate the child pages.

TissueDB/Materials/Castable Materials is the first of these.

Felipe: this is the part worth knowing before you act on any consolidation list.

When names were consolidated, the superseded titles were turned into redirects, not deleted. That was a deliberate instruction from the owner, in her words:

"I was rightfully afraid that it would result in huge loss of work as all those pages got deleted before the info from them was consolidated."

The sequence matters and it is one-way: carry the content across first, verify it is live on the target, and only then repoint the old title. A redirect is reversible; a deletion is not. The project also runs a never-delete policy, so anything superseded goes to an archive with a hold rather than being removed.

Deletion is still the intended end state, but later and separately. The owner:

"A later stage of this will go back and simply fix the links and get rid of all the non-used pages."

So a title that redirects here is not finished work waiting to be tidied — it is a hold that is doing its job. Please do not delete redirect titles as cleanup unless the deletion has been asked for by name.

{{TissueDB Material Layout
| overview =
{{TissueDB Material Class Table
| rows =
<tr>
<td>[[TissueDB/Materials/Silicone, Castable|Silicone, Castable]]</td>
<td>Two-part platinum or tin cure</td>
<td>Mixed and poured into a mould in the build.</td>
</tr>
}}
}}

• Every Material cell links to an existing TissueDB/Materials/ page.
• No build instructions, quantities, costs or fidelity ratings. Those belong on the child page.
• No visual or tactile fidelity columns. Per the owner's ruling those cells stay blank across the project, so this table does not offer them at all.
• Membership is measured, not assumed. A material earns a row because a build actually uses it that way, and the page states the denominator it was measured against.
• Source-traced content only. No inferred properties.