Three years ago, I published a small plugin both on GitHub and in the plugin repository that made it possible view WordPress page templates in the admin.
I called it Page Template Dashboard – naming things isn’t easy, and even when you do, it’s obviously not great – but WordPress has changed a lot in three years.
In three years, a lot can change in your personal life too, and this makes it hard to work on personal projects. But when you can steal a few hours – usually late at night – it makes it possible to revisit and update projects like this.
So last night, I release the latest version of Page Template Dashboard.
View WordPress Page Templates
The whole idea behind Page Template Dashboard is simple:
An easy way to see which templates your pages are using without having to view the page editor.
If you navigate to the All Pages view in the WordPress admin, then you’ll see a new column that contains one of two options:
- if a template is used, you’ll see the name of the file,
- otherwise, you will see ‘Default’ listed.
I’ve tried to make this as easy as possible to use (though feedback is always welcome) and it includes bother user and developer-centric features.
To get up and running with the plugin, you can either download the plugin from within the WordPress itself (by searching for it), or you can download it from the page above.
Once installed, it “just works” in that there are no options to configure. The new column is added when the plugin is active and removed when the plugin is deactivated.
Page Template Dashboard includes
composer.json so you can download the plugin to your local development environment, install the PHP CodeSniffer, and then work on the plugin using whatever rules you prefer.
The codebase was also refactored so that:
- the implementation of the singleton pattern was completely removed,
- a locale property was removed in place of strings for proper internationalization,
- the code was brought up to the WordPress Coding Standards.
I don’t necessarily consider this a plugin that’s useful for developers. But for those who want to grab a copy of it, open issues, fork it, add a pull request, or any of the above, you can grab it on GitHub.
No Specific Roadmap
When it comes to plugins like this, I usually don’t maintain roadmaps; however, if there’s additional feedback then I’m happy to take a look at it.
I usually don’t pay attention to the built-in forums in the Plugin Repository (and I have a policy for that!), but I do pay attention to all emails and notes on GitHub.
Worth a Share?
Finally, if you’re a fan of this plugin or feel generous, I’m always grateful for those who feel so inclined to share its repository page on networks like, you know, Twitter.
It’s fun to work on these, and a few people do use the plugin. But plugins tend to slowly die and interest wanes when it’s more or less forgotten amidst the thousands upon thousands of plugins available.
That’s completely fine, too – if it’s time for something to retire, I’m happy to oblige – but sharing the occasional plugin goes a long way. Especially if you’ve found it useful. 😇