CPT Builder

No. You name the type, tick the supports you want — title, editor, thumbnail and so on — set a URL slug and whether it’s public, then save. It registers on the next load and appears in the admin menu exactly like a built-in type.

Nothing is lost. Definitions are stored as plain option data rather than inside the module, so they survive plugin and module toggles. Reserved or invalid keys are skipped rather than guessed at, so a new type can’t silently clash with something already registered.

Yes. A Meta Box attaches to any post type, and the checklist includes the built-in Post and Page alongside every custom type on the site — including types registered by other Tiger plugins, such as Service, Room or Product.

Nineteen, covering text, textarea, WYSIWYG editor, number, email, URL, phone, date, time, date & time, select, radio and checkbox among others. Values are saved as namespaced post meta, so they stay tidy and predictable.

With the matching Elementor dynamic tag. A per-post field is a post field, a global value comes from Tiger · Site → Site Field, and an author value from Tiger · Author → Author Field. No template code required.

Yes. Dummy Data generates sample entries for a post type so you can build and check a single template or loop grid against realistic records before writing a word of production content.

Yes. Export JSON downloads your entire CPT Builder schema — post types, taxonomies and field definitions — and Import JSON recreates it on the destination site.