Experienced users and developers will use the word “template” casually in and around WordPress to mean slightly different things in slightly different contexts. There are four general things that people will be referring to when they say the word, all substantially different. They may be saying “template” when they mean:
- A raw-HTML file or set or files (usually for sale)
- A WordPress theme
- A file in the WordPress template hierarchy
- A Handlebars, Twig, PHP, etc template file
Each of these usages is good to know of, and to understand in a bit more detail. So let’s get to explaining them.
As a Raw HTML File
For people like me who simply can’t make any design look good, HTML templates are a salvation.
For people like me who simply can’t make any design look good, HTML templates are a salvation. Whatever I’m using to run the site — raw HTML documents I edit, WordPress, or some other CMS or web framework — I can take the (usually sold for money, but sometimes free) template and have something that probably looks about 10x better than I could do.
If you’re working in WordPress, this generally isn’t in play as much because of the next definition. But for people who’ve been around longer, or who aren’t familiar with WordPress, this may well be what they mean by the word “template.”
[…] Four Different Meanings of “Template” a WordPress Pro Should Know […]
[…] is a pattern that is often used in web applications to keep your data (model), your templates (view), and behavior (controller) from walking all over each other. The ugliness I mentioned about […]
[…] is a pattern that is often used in web applications to keep your data (model), your templates (view), and behavior (controller) from walking all over each other. The ugliness I mentioned about […]
[…] so easy: just put some more PHP in the file (we talked about this more recently in “The Four Types of Templates…“), but that doesn’t make it a good idea. Our theme pages should be as clear and simple […]