The CPT Builder lets you register custom post types and taxonomies from the admin — no code — so you can model content like Services, Listings or Team members.
Where: WP Admin → Tiger Elements → CPT Builder.
Creating a post type
Give it a name, choose supports (title, editor, thumbnail, etc.), set a URL slug and whether it’s public, then save. The type registers on the next load and appears in the admin menu like any built-in type. Taxonomies work the same way and can be attached to one or more post types.
Safe by design
Definitions are stored as plain option data, so they survive plugin/module toggles and are easy to export. Reserved or invalid keys are skipped rather than guessed at, so you can’t accidentally clash with core types. Your CPT content then works everywhere Tiger does — Query Builder, Loop Grid, dynamic tags and the Theme Builder.
Meta Boxes — custom fields
Add a Meta Box and attach it to any post type — a built-in one (Post, Page) or any custom type from Tiger Elements or another Tiger plugin (Service, Room, Product, and more). Set the placement Context (Normal, Side, or Advanced) and optionally narrow it to specific pages, page templates, or a parent page and its children.
Fields are stored as namespaced post meta (tcp_<key>). Nineteen field types are available — text, textarea, WYSIWYG editor, number, email, URL, phone, date, time, date & time, select, radio, checkbox, color, image, gallery, Group and Repeater (to nest sub-fields), and Relationship (link to another post — put the target post type’s slug in Select options, e.g. post, tiger_service).
Site Options & User Fields
| Tool | What it’s for |
|---|---|
| Site Options | Site-wide fields not tied to any single post — a phone number, address, social links. Output anywhere via the Elementor dynamic tag Tiger · Site → Site Field. |
| User Fields | Scalar fields added to every user’s profile screen, stored as user meta. Output the current post’s author value via the dynamic tag Tiger · Author → Author Field. |
Dummy Data & portability
Dummy Data generates sample entries for a post type so you can preview a template or loop grid before writing real content. Export JSON downloads your entire CPT Builder schema (post types, taxonomies, meta boxes) as one file; Import JSON loads it back in — useful for moving a content model between a staging site and production, or reusing it on a new build.