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.

TeaCii

This plugin allows you to display the value of a custom field on a page or post. Permitted values are raw text, html, javascript, javascript file url, css, css file.
Since version 1.1.x it also allows you to show a custom field of any page or post, provided you have the id.
One of the intended use of this plugin is to provide just in time code without editing the theme. Often code, especially css, gets lost with theme change. This techniques will ensure the values are loaded only on the given page and they will survive changes of themes and other plugins.
You can also use this to include javascript snippets or files. They will only be loaded on the given post or page. This in turn allows for loading of scripts only where needed.
You may use the plugin in two ways: 
[dcf field=”name_of_custom_field”] 
or optionally you can 
– define the type of the field value. By default the type is “raw”. 
– provide the id number of the page or post. By default, it would be the current page/post id. 
[dcf field=”name_of_custom_field” type=”value_type” id=’post_or_page_id_number’]
The accepted value types are:
“raw” – this is the default and you do not need to specify this type. It outputs the value as it is. You can use html code in the values quite safely.
“js” – use this to specify that the value is actually javascript. Do not wrap it with the script tag. Remember that $ is not a valid jQuery replacement in WordPress. You should use “jQuery” instead.
“jsf” – You may need to include a javascript file. The value of the custom field should be a fully qualified javascript file url.
“css” – use this to specify css code in the value of the custom field.
“cssf” – You may need to include a css file. The value of the custom field should be a fully qualified css file url. Here I would like to note that: 
– It is highly unusual to include css files in the body. However, it does work. 
– There may be a side effect that some elements may not show properly until the css file is completely loaded.

Display Custom Fields

This plugin allows you to display the value of a custom field on a page or post. Permitted values are raw text, html, javascript, javascript file url, …

TypeForge CPT and Meta Builder vs Display Custom Fields