TypeForge CPT and Meta Builder

Dashboard

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.

Custom Post Types

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 Singular: Portfolio Item Plural: Portfolio Items Slug: portfolio Menu Icon: dashicons-images-alt Supports: title, editor, thumbnail Public: Yes Archive: Yes REST: Yes

Custom Taxonomies

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 Name: Project Tags Singular: Tag Slug: portfolio-tag Hierarchical: No (flat like tags) Post Types: portfolio (check) Show in REST: Yes

Meta Fields

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 _portfolio_client (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 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 Generator

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)

Import / Export

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.

Troubleshooting

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

ACF Compatible JSON

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.

Support

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 typeforge_cpt_meta_builder_* filters – Configuration: Modify via typeforge_cpt_meta_builder_config_updated action – Extend: Hook into registration functions – Version control: Export JSON and commit to git

Performance & Optimization

TypeForge is built for speed:

• Lightweight Code – ~50KB of PHP, no heavyweight dependencies
• Efficient Queries – Configuration cached per-request
• Smart Asset Loading – CSS/JS only load on plugin pages
• Database Optimization – Uses WordPress options API efficiently
• REST API Ready – Automatic REST registration without extra overhead

Security & Compliance

TypeForge follows WordPress security standards:

• ✅ Proper input sanitization and escaping
• ✅ Nonce verification on all forms
• ✅ Capability checking (filterable manage_options )
• ✅ PHPCS WordPress-Core standard compliance
• ✅ No external API calls or tracking
• ✅ Privacy-focused (zero user data collection)
• ✅ Regular security audits

Contributing

TypeForge welcomes community contributions. To contribute:

1. 08Fork the repository
2. 09Create feature branch ( git checkout -b feature/amazing-feature )
3. 10Commit changes ( git commit -m 'Add amazing feature' )
4. 11Push to branch ( git push origin feature/amazing-feature )
5. 12Open Pull Request

Rate & Review

If TypeForge helps your WordPress project, consider leaving a review on WordPress.org. Your feedback helps other developers find this tool.

⭐⭐⭐⭐⭐ Your review matters!