Custom Post Types

Custom Post Types are special content types in WordPress that go beyond the default “Posts” and “Pages.” We create them when a website needs structured, repeatable content that shouldn’t be built manually each time.

Think of a CPT as a custom bucket for a specific kind of content. Each bucket has its own fields, layouts, and rules to keep everything consistent.

🔧 Why We Use CPTs

KIJO uses Custom Post Types to make content management foolproof and scalable.

Instead of building team profiles, guides, logos, case studies, or services manually with Elementor, a CPT provides:

A dedicated admin menu for that content
Custom fields (e.g., job role, logo image, guide category)
A consistent template that automatically formats each entry
Faster content updates without touching page layouts
Cleaner data for future updates, redesigns, or migrations

🧱 Common CPT Examples We Create

Depending on the project, typical CPTs might include:

Guides / Articles – structured learning or documentation content
Team Members – name, bio, job title, profile image
Logos / Partners – client or partner logos displayed consistently
Case Studies / Projects – featured images, outcomes, testimonials
Courses or Lessons (when not using LearnDash)
Services – descriptions, icons, pricing blocks, etc.

Each CPT is designed to match how the client will actually use the website — so editing becomes predictable and safe.

✏️ How to Add or Edit a CPT

Log in to WordPress.
In the left-hand menu, look for the custom post type (e.g., “Team,” “Guides,” “Logos”).
Add New to create new content, or hover and Edit to change existing items.
Fill in the required custom fields (these appear below or beside the main editor).
Click Publish or Update.

Most CPTs do not require Elementor, because they’re rendered through predefined templates. You just fill in the fields — the layout takes care of itself.

💡 Best Practices

Don’t alter the template structure. CPT layouts are managed globally.
Use the fields provided. If something is missing, flag it rather than “hacking” a fix.
Keep naming consistent. Titles and slugs feed into SEO and sometimes dynamic templates.
Avoid uploading oversized images. Stick to the recommended sizes noted in the project documentation.