OMG! I’ve entered the plugin territory!


Credit: Infologs

As a new player in this fancy game of WordPress Themes development, I have a lot to learn, and things explode in my face from time to time.

So i was trying to get my new WordPress theme to comply with the WordPress Theme Requirements using the Theme Check plugin, and I got this…

REQUIRED: The theme uses the register_post_type() function, which is plugin-territory functionality.

I freaking knew it. But as with other things, I was delaying it. I was not adding too much functionality to my theme, but there’s something I’ve actually added, and I knew it would explode in my face sooner or later.
Shame on me. I mean this item from the Theme Review Handbook:

Since the purpose of Themes is to define the presentation of user content, Themes must not be used to define the generation of user content, or to define Theme-independent site options or functionality.

Yep, mamuso, you knew it. You entered plugin territory long time ago.

Then, looking for people with the same problem, I learned a new hateful word. Portfolio. It hasn’t even a clean translation to my mother tongue (Spanish, by the way). Tell me if you know it. I hate that word.

However I have the gut feeling that I will love it soon. You know, love and hate are almost the same.

So the next steps will involve using the Custom Content Portfolio plugin and add it to my theme as a requirement using TGM plugin activation. Or maybe making my own plugin, I don’t really know yet. I really like the spirit of what Justin Tadlock is doing, but I don’t know if it’s better for me to make a custom plugin. I was thinking about uploading this and maybe subsequent themes to themeforest, because I’m poor and I need coffee. I’m very bad at guessing what I can and what I can’t do with each license (who isn’t?), and I think I have kinda GPL-phobia. Perhaps someone could enlighten me.
If you’re in the same boat as me, take a look at some blog posts that talk about plugin territory, like this, or this one.

Leave a Reply