Darshit Rajyaguru

TypeForge CPT and Meta Builder is a lightweight, performance-optimized WordPress admin interface for creating custom post types, taxonomies, and post meta configurations without writing code. Perfect for developers who want a faster alternative to page builders for content structure setup.
Why TypeForge? 
– Lightning-fast performance with minimal database overhead 
– Zero dependencies – works standalone without ACF or other plugins 
– Clean, developer-focused UI 
– Export PHP snippets for version control 
– Portable JSON configurations for multi-environment workflows 
– Full REST API support out of the box 
– SEO-friendly with proper WordPress integration
Key Features:
<ul>
<li>⚡ Performance-First Design – Lightweight codebase, optimized queries, lazy-loaded assets</li>
<li>🏗️ Custom Post Type Builder – Configure all standard CPT options with live validation</li>
<li>📂 Taxonomy Builder – Create hierarchical or flat taxonomies, assign to multiple post types</li>
<li>🏷️ Meta Field Builder – 13 field types including flexible content for repeatable data</li>
<li>📱 Mobile-Ready Forms – Responsive meta boxes that work on all devices</li>
<li>💾 Code Generation – Download ready-to-use PHP snippets with proper registration</li>
<li>📤 Portable Config – Export/import JSON for easy deployment across environments</li>
<li>🔌 REST API Ready – Built-in REST endpoint support, no additional setup needed</li>
<li>🎨 ACF Compatible – Generate ACF-compatible JSON when ACF is active</li>
<li>🔒 Secure by Default – Proper sanitization, nonce verification, capability checks</li>
<li>♿ Accessible – WCAG-compliant markup and keyboard navigation</li>
</ul>
The plugin does not bundle or require Advanced Custom Fields. ACF JSON export is a bonus when ACF is active.
<h3>Usage Guide</h3>
Getting Started in 5 Minutes:
<ol>
<li>Activate the plugin</li>
<li>Go to TypeForge CPT Builder in admin menu</li>
<li>Create your first custom post type (e.g., “Portfolio”)</li>
<li>Add a taxonomy (e.g., “Portfolio Category”)</li>
<li>Add custom meta fields (e.g., “Project URL”, “Client Name”)</li>
<li>View live meta box in post editor</li>
<li>Export PHP code for production use</li>
</ol>
<h4>Dashboard</h4>
The dashboard provides a quick overview of your content structures: 
– Post Types Count – All registered custom post types 
– Taxonomies Count – All registered taxonomies 
– Meta Fields Count – All configured meta fields 
– REST Enabled – Count of REST-enabled structures
Use quick action buttons to create new structures, generate code, or manage configurations.
<h4>Custom Post Types</h4>
Configuration Fields: 
– Singular Name – Grammatically correct singular label (e.g., “Portfolio Item”) 
– Plural Name – Plural form (e.g., “Portfolio Items”) 
– Slug – URL-safe identifier, no spaces or special chars (e.g., “portfolio”) 
– Menu Icon – Choose from 300+ Dashicons 
– Menu Position – Order in admin menu (5-100) 
– Description – Helpful text for admin users 
– Supports – Editor features (title, editor, thumbnail, etc.) 
– Public – Visible on frontend (affects archive, search, REST) 
– Hierarchical – Enable parent/child relationships 
– Archive – Show post type archive page 
– REST Support – Enable REST API endpoints
Tips: 
– Archives need “Hierarchical” off and “Archive” enabled 
– Public CPTs require “Show UI” and “Public” both enabled 
– Change slug-related settings before publishing content 
– REST support is recommended for headless/block editor usage
Example: Portfolio Post Type 
 <code>Singular: Portfolio Item 
Plural: Portfolio Items 
Slug: portfolio 
Menu Icon: dashicons-images-alt 
Supports: title, editor, thumbnail 
Public: Yes 
Archive: Yes 
REST: Yes</code>
<h4>Custom Taxonomies</h4>
Configuration Fields: 
– Name – Taxonomy display label (e.g., “Project Categories”) 
– Singular – Singular form (e.g., “Category”) 
– Slug – URL identifier (e.g., “portfolio-category”) 
– Hierarchical – Enable parent/child like categories (vs tags) 
– Post Types – Assign to one or more CPTs 
– Show in REST – Enable REST API support 
– Rewrite – Update URL structure after creation
Tips: 
– Hierarchical taxonomies work like categories (parent/child) 
– Flat taxonomies work like tags (no hierarchy) 
– Assign to multiple post types for shared taxonomy 
– Visit Settings > Permalinks after slug changes
Example: Portfolio Tags Taxonomy 
 <code>Name: Project Tags 
Singular: Tag 
Slug: portfolio-tag 
Hierarchical: No (flat like tags) 
Post Types: portfolio (check) 
Show in REST: Yes</code>
<h4>Meta Fields</h4>
Field Types Supported: 
– Text – Single-line text input 
– Textarea – Multi-line text editor 
– Number – Numeric input with validation 
– Email – Email field with validation 
– URL – URL field with validation 
– Checkbox – Boolean true/false 
– Radio – Single select from options 
– Select – Dropdown selector 
– Date – Date picker field 
– Time – Time picker field 
– Image – Media library image uploader 
– File – Media library file uploader 
– Flexible Content – Repeatable layout blocks (new!)
Configuration: 
– Post Type – Which CPT this field applies to 
– Label – User-friendly field name 
– Meta Key – Internal database key (underscore-prefixed recommended) 
– Type – Choose from 13 field types 
– Options – For select/radio (one per line) 
– Default Value – Pre-fill when creating posts 
– Placeholder – Example text in input 
– Description – Helper text below field 
– Required – Mark field as mandatory 
– Show in REST – Expose to API
Tips: 
– Use meta keys like <code>_portfolio_client</code> (underscore prefix hides from custom fields) 
– Required fields work with JavaScript validation 
– Flexible content is perfect for modular content blocks 
– REST-enabled fields auto-register with proper schema
Example: Portfolio Meta Fields 
 <code>1. Client Name (text) - _client_name - Required: Yes 
2. Project URL (url) - _project_url - Required: No 
3. Project Budget (number) - _project_budget - Show in REST: Yes 
4. Case Study (flexible_content) - _case_study</code>
<h4>Code Generator</h4>
The Code Generator creates production-ready PHP snippets. Perfect for: 
– Version control integration 
– Continuous deployment pipelines 
– Moving from staging to production 
– Sharing configurations across teams 
– Local development workflows
Generated Code Includes: 
– CPT registration with all options 
– Taxonomy registration with assignments 
– Meta field registration with schema 
– REST endpoint examples 
– Proper capability checks 
– Inline documentation
Quick Generate Feature: 
Simply enter a name and TypeForge auto-generates slug, singular/plural forms: 
– “Event” → slug: event, singular: Event, plural: Events 
– “Author” → slug: author, singular: Author, plural: Authors 
– “Testimonial” → slug: testimonial, singular: Testimonial, plural: Testimonials
Export Options: 
– Copy code to clipboard (Ctrl+C ready) 
– Download as .php file for version control 
– ACF-compatible JSON (when ACF is active)
<h4>Import / Export</h4>
Use Cases: 
– Backup configurations 
– Transfer between environments (local → staging → production) 
– Share configurations with team members 
– Version control content structures 
– Disaster recovery
Workflow: 
1. Go to Import/Export page 
2. Click “Export JSON” to download current configuration 
3. On another site, click “Import JSON” and select the file 
4. Review configuration preview 
5. Click “Import” to activate structures
JSON Format: 
The exported JSON includes all CPTs, taxonomies, meta fields, and settings. Keep backups in git for version history.
<h4>Troubleshooting</h4>
Post Type Not Appearing? 
– Check “Show UI” and “Public” are enabled 
– Visit Settings > Permalinks and save 
– Clear browser cache 
– Refresh WordPress admin
Meta Fields Not Showing? 
– Verify field is assigned to correct post type 
– Check post type has meta box support 
– Ensure meta field is not hidden (show_in_rest) 
– Clear admin bar cache
REST API Not Working? 
– Enable “Show in REST” on CPT and fields 
– Verify REST is not disabled in settings 
– Test with REST CLI or Postman 
– Check user capabilities allow API access
Import Failing? 
– Verify JSON file is valid (use online JSON validator) 
– Check file size is under 30MB 
– Ensure proper permissions 
– Try export/import on fresh installation first
Settings > Permalinks Not Saving? 
– Disable plugins temporarily to check conflicts 
– Verify .htaccess is writable 
– Try “Plain” permalinks then switch back 
– Check with hosting provider for rewrite rules
<h4>ACF Compatible JSON</h4>
TypeForge generates ACF-compatible JSON when Advanced Custom Fields is active. This allows: 
– Easy ACF integration for clients 
– Switching between ACF and TypeForge 
– Export structures for ACF field groups 
– Backup ACF fields in portable format
Note: TypeForge is fully independent and works without ACF. ACF compatibility is optional.
<h3>Support</h3>
Need Help? 
– Read the comprehensive FAQ section above 
– Check the Troubleshooting guide in Usage section 
– Visit WordPress.org support forums 
– Report bugs or suggest features via GitHub
For Developers: 
– Hooks: Use <code>typeforge_cpt_meta_builder_*</code> filters 
– Configuration: Modify via <code>typeforge_cpt_meta_builder_config_updated</code> action 
– Extend: Hook into registration functions 
– Version control: Export JSON and commit to git
<h3>Performance & Optimization</h3>
TypeForge is built for speed:
<ul>
<li>Lightweight Code – ~50KB of PHP, no heavyweight dependencies</li>
<li>Efficient Queries – Configuration cached per-request</li>
<li>Smart Asset Loading – CSS/JS only load on plugin pages</li>
<li>Database Optimization – Uses WordPress options API efficiently</li>
<li>REST API Ready – Automatic REST registration without extra overhead</li>
</ul>
<h3>Security & Compliance</h3>
TypeForge follows WordPress security standards:
<ul>
<li>✅ Proper input sanitization and escaping</li>
<li>✅ Nonce verification on all forms</li>
<li>✅ Capability checking (filterable <code>manage_options</code>)</li>
<li>✅ PHPCS WordPress-Core standard compliance</li>
<li>✅ No external API calls or tracking</li>
<li>✅ Privacy-focused (zero user data collection)</li>
<li>✅ Regular security audits</li>
</ul>
<h3>Contributing</h3>
TypeForge welcomes community contributions. To contribute:
<ol>
<li>Fork the repository</li>
<li>Create feature branch (<code>git checkout -b feature/amazing-feature</code>)</li>
<li>Commit changes (<code>git commit -m 'Add amazing feature'</code>)</li>
<li>Push to branch (<code>git push origin feature/amazing-feature</code>)</li>
<li>Open Pull Request</li>
</ol>
<h3>Rate & Review</h3>
If TypeForge helps your WordPress project, consider leaving a review on WordPress.org. Your feedback helps other developers find this tool.
⭐⭐⭐⭐⭐ Your review matters!

TypeForge CPT and Meta Builder

Lightweight, fast custom post type, taxonomy, and meta field builder for WordPress. Perfect for developers.

dirlikdesigns

Easy to use XML feed importer with the ability to map feed items onto (custom) posts and their meta fields.
<h4>Usage Notes</h4>
<ul>
<li>The feeds are managed (added / edited / deleted) like normal posts.</li>
<li>To import a new feed, you must first save the post with at least the title and URL fields filled in.
<ul>
<li>This is because the importer downloads a copy of the feed and works with that copy.</li>
<li>If you try to import before the feed is saved, the importer has no copy to work with yet.</li>
</ul>
</li>
</ul>
<h4>Form explanation</h4>
<ul>
<li>Import
<ul>
<li>It’s the first field in the form, but the last step.</li>
<li>There is no cancel button, so once you click the ‘import’ button, you can only refresh (or move away from) the page to cancel the import.</li>
<li>The import is done 10 feed items at a time, the progress is shown under the import button.</li>
<li>The import sends ajax requests until the import is done at which point the spinner stops spinning and the progress message shows ‘n posts imported’</li>
</ul>
</li>
<li>URL
<ul>
<li>the feed url</li>
</ul>
</li>
<li>Required Fields (optional)
<ul>
<li>comma separated list of (custom) post fields</li>
<li>if a field in this list has no mapping, than the import will fail</li>
<li>if the mapping of a field in this list turns out to be empty, than the corresponding feed item is skipped.</li>
</ul>
</li>
<li>Unique Fields (optional)
<ul>
<li>comma separated list of (custom) post fields</li>
<li>unique fields are not implicitly required</li>
<li>skips a feed item if a field with this value already exists.</li>
</ul>
</li>
<li>CSV delimiter (optional)
<ul>
<li>if this field is empty, the plugin assumes the URL links to a XML file</li>
<li>if this field is non-empty, the plugin assumes the URL links to a CSV file, with the given value as the delimiter</li>
<li>a CSV file will be converted to XML, so the further usage of the plugin remains the same.</li>
</ul>
</li>
<li>Select root
<ul>
<li>select the path to the items that should be mapped</li>
<li>i.e. you want to import products into your woocommerce installation</li>
<li>xml : <products> <product></product> … <product></product> </products></li>
<li>then the root should be /products/product</li>
<li>you can use the plus and minus buttons to go a level up or down</li>
<li>the select boxes show the possible paths for a given level</li>
<li>Click the ‘Select’ button to confirm the root</li>
<li>The XML area should fill up with the first item that matches root.</li>
</ul>
</li>
<li>Select post field
<ul>
<li>the first select box shows the registered post types and Taxonomies.</li>
<li>the second select box shows the corresponding fields. (Even columns like ID which you probably shouldn’t set manually)</li>
<li>many of the fields are always the same and correspond to the columns in the <code>wp_posts</code> table in the database, but the meta fields can differ.</li>
<li>the plugin needs at least one existing object of the selected post type to find these meta fields.</li>
<li>the meta fields are based on the first post of the selected post type it finds.</li>
</ul>
</li>
<li>Map
<ul>
<li>this shows the current mapping</li>
<li>if you have selected a mapping, it can be removed with the ‘x’ at the right hand side</li>
<li>if you are satisfied with the mappings, click ‘Save map’</li>
</ul>
</li>
<li>XML
<ul>
<li>once you have selected a root, the first xml item at this path will be shown here.</li>
<li>click anywhere on the XML to get the corresponding paths</li>
<li>the selected path will appear above the colourful XML</li>
<li>if the path contains attributes, they will appear as selectboxes</li>
<li>if the desired path depends on a sibling in the XML, follow these instruction:</li>
<li>some XML looks like this ..<parent> <key>name</key><value>Dirlik<value></parent> …</li>
<li>in this case, click on the value tag in the XML and the corresponding path appears: ‘Assign path: …/parent/value’</li>
<li>now click on ‘parent’ in the path and 2 new selectboxes appear and an ‘Add to attribute list’ button</li>
<li>in our example you would select ‘key’ in the first selectbox and ‘name’ in the second</li>
<li>click ‘Add to attribute list’ and the path changes accordingly</li>
<li>once you see the path you want, click the ‘Add to map’ button.</li>
<li>The Map will now reflect that the path you chose is mapped om the selected post field.</li>
</ul>
</li>
</ul>
<h3>WARNING</h3>
This plugin is new and requires more testing. If you decide to use the plugin, please make a backup of your database first. 
Once you click the <code>import</code> link, there is no cancel button, you can refresh (or move away from) the page to cancel the import. 
On your first go, try a smaller feed to make sure you mapped it right.
<h3>TODO</h3>
<ul>
<li>add row actions</li>
<li>define type of imported value (now images only work with _thumbnail_id meta value)</li>
</ul>

XML Import

XML feed importer with ability to map feed items onto (custom) posts.

TypeForge CPT and Meta Builder vs XML Import