• Resolved mw13068

    (@mw13068)


    I’m a longtime LAMP dev, investigating WordPress as a possible replacement to my custom-built CMS. I’ve created a plugin to implement my Custom Post Type, with meta fields, a data import routine, with taxonomies, etc. The Plugin Guide recommended keeping one’s data in a CPT to keep it separate from the Core Posts. What about Pages? Do I create another CPT to deal with Pages, or use the Page functionality in the Core?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator bcworkz

    (@bcworkz)

    If this plugin is not intended for distribution to others, you may do whatever you wish, it’s your site.

    If your CPT “pages” are simply website pages just like core pages, there’s little reason to have another CPT, but of course you may do so if it makes sense for some reason. As you likely know, the only difference between a “post” CPT and a “page” CPT is one is hierarchical and the other is not. If you need a hierarchical page-like CPT for any reason, go for it, but don’t feel like it’s a necessity 🙂

    Thread Starter mw13068

    (@mw13068)

    Thanks. That’s what I surmised, but as a beginner, I wanted confirmation of my general understanding.

    I’ll skip making a Page CPT and move on to learning about theme/template building.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.