Template

Templates can be used for posts, pages, archives, search results and other views. In block themes they are composed from blocks and template parts. In practical terms, Template belongs to the publishing and site-management layer. Knowing that layer is important because it tells you what the term can change, what it cannot change, and where to look when something behaves unexpectedly.

The common mistake is to use Template as if it also meant Template Part. That blurs two separate decisions and usually sends troubleshooting in the wrong direction. A better test is practical: Edit the template only when the structural change should affect every item that uses it.

In day-to-day work, Template matters when the concept needs to be identified precisely instead of being grouped with a nearby term. The practical value is not the vocabulary itself; it is being able to identify the right control, file, setting or decision when the concept becomes relevant.

A single-post template controls the structure used to display many posts, while the individual post supplies its own content. That example is useful because it turns the definition into something you can recognize, test and discuss with other people working on the same project.

Use these references when you need documentation-level detail, specifications or product-specific behavior beyond the plain-English explanation above.