Before diving into Field Forge, it helps to understand the vocabulary you will encounter throughout this guide and inside the plugin itself. These terms come up repeatedly in menus, tooltips, documentation, and conversations with your developer. Learning them now saves confusion later and makes every other section of this guide easier to follow.
Field Forge is a WordPress plugin that lets you add structured data fields to your posts, pages, and custom post types without writing code. Instead of cramming everything into the main content editor, you create dedicated inputs — text boxes, image pickers, dropdowns, toggles, and more — that content managers fill in when editing a post. Your developer then uses those values in theme templates to display them on your website.
Glossary of Key Terms
| Term | What It Means | Real-World Analogy |
|---|---|---|
| Field | A single input that captures one piece of data. It could be a text box, an image upload button, a dropdown menu, a date picker, or any other input type. Each field has a Label (what editors see) and a Name (what developers reference in code). | A single question on a paper form — “What is your name?” is one field. |
| Field Group | A collection of fields that belong together and appear as a unit when editing a post or page. A field group has a title, a set of fields, and location rules that determine where it shows up. | A section of a paper form — the “Personal Information” section that groups Name, Email, and Phone together. |
| Location Rule | A condition (or set of conditions) that tells Field Forge which posts, pages, or screens should display a particular field group. Without a location rule, a field group exists but never appears anywhere. | An instruction on a paper form that says “Only fill out Section B if you are applying for a business account.” |
| Sub-field | A field that lives inside a compound field such as a Repeater, Group, or Flexible Content layout. Sub-fields work exactly like regular fields, but they are nested one level deeper. | A column in a table — the “Name” column inside a “Team Members” table. |
| Metabox | The bordered box that appears below the WordPress content editor when you edit a post. Each field group renders as its own metabox with a title bar and the fields inside it. Content managers interact with metaboxes every time they edit a post that has custom fields. | A physical card pinned below the main writing area on a desk, with blank spaces to fill in. |
| Options Page | A dedicated admin screen for site-wide data that is not tied to any single post or page. Options Pages appear in the WordPress sidebar menu and hold settings like your company phone number, social media URLs, or a global announcement banner. This is a PRO feature. | A company-wide settings sheet that applies everywhere, not just to one document. |
| Conditional Logic | Rules that show or hide a field at runtime based on the value of another field. Field-level rules are configured in the field group editor (toggle “Conditional Logic” on any top-level field, then add rules joined by AND inside a group and OR across groups). The metabox renderer evaluates them server-side on initial load and the JS runtime keeps state in sync as triggers change. Sub-field rules inside Repeater / Group / Flexible Content are stored but not yet evaluated at runtime. | A form instruction that says “If you answered Yes to question 3, please fill in question 4.” |
| Wrapper Width | A percentage setting on a field that controls how much horizontal space it takes up in the editor. Two fields set to 50% each appear side by side on the same row. Three fields at 33% create a three-column layout. This is purely a visual layout choice for the editing screen. | Arranging form fields in columns on a printed form instead of stacking them all vertically. |
| Field Name (slug) | The machine-readable identifier for a field, usually auto-generated from the label (for example, “Hero Title” becomes hero_title). Developers use the field name in theme code to retrieve and display the data. Once a field is in use on a live site, changing the name breaks the connection to saved data. | A database column name — invisible to the person filling out the form but essential for the system that processes it. |
| Layout (in Flexible Content) | A section template inside a Flexible Content field. Each layout has its own set of sub-fields and represents a distinct section type that editors can add to a page. For example, a “Hero Banner” layout, a “Features Grid” layout, and a “Testimonials” layout. | A card in a card catalog — each card type has a different format, and you pick which cards to include in your binder. |
| Revision | A saved snapshot of a field group at a specific point in time. Field Forge automatically creates a revision every time you save a field group, allowing you to compare versions and roll back to a previous state if something goes wrong. | A version history in Google Docs — you can see who changed what and restore an earlier version. |
How the Pieces Fit Together
Think of building custom fields as a three-layer process. First, you create a Field Group — this is the container. Second, you add Fields inside that container — these are the individual inputs your editors will fill in. Third, you set Location Rules on the field group — these determine which posts, pages, or screens display the fields. When a content manager opens a post that matches the location rules, the field group appears as a metabox below the content editor, and they fill in the fields.
Your developer then writes theme template code that retrieves the field values and renders them on the frontend of your website. Content managers never touch code — they only interact with the fields in the WordPress editor.
A Practical Example to Tie It All Together
Imagine you run a restaurant website with a custom post type called “Menu Items.” You want each menu item to have a Price, a Spice Level (mild, medium, hot), a short Description, and a Photo. Here is how the concepts map:
- You create a Field Group called “Menu Item Details”
- Inside it, you add four Fields: Price (number), Spice Level (select dropdown with three options), Description (textarea), and Photo (image)
- You set a Location Rule: Post Type is equal to Menu Item
- Now every time someone creates or edits a Menu Item post, they see the “Menu Item Details” metabox with those four fields ready to fill in
- Your developer adds template code that displays the price, spice level badge, description, and photo on the menu page of your website
> Good to know: Field Forge stores data in its own optimized database tables rather than the default WordPress wp_postmeta table. This means faster page loads and fewer database queries, especially on sites with many fields. Your content managers will not notice any difference in how they enter data — the performance improvement is entirely behind the scenes.
Free vs PRO Concepts at a Glance
Some features in Field Forge are available on the free plan, and others require PRO. You do not need to memorize every detail now — each section of this guide notes which plan is needed — but here is a quick orientation:
- Free plan — You can create up to 3 field groups using 20 field types. This covers Text, Textarea, Number, Image, File, Select, Checkbox, Radio, True/False, Date Picker, Color Picker, and layout helpers (Tabs, Accordions, Messages). You also get Location Rules, Revision History, and ACF field group import.
- PRO plan — Unlocks unlimited field groups, 32 field types (adds Repeater, Group, Flexible Content, Gallery, oEmbed, Clone, Relationship, Post Object, and more), plus Options Pages, AI Field Generation, export/import, and ACF value migration.
Throughout this guide, PRO features are clearly labeled with “(PRO)” in section headings and callout boxes so you always know what requires a paid license.
> Important: The terms in this glossary are used consistently throughout every section of this guide. If you encounter an unfamiliar term later, come back to this page for a quick refresher. Bookmark it.
> Tip: If you are brand new to custom fields in WordPress, the single most important concept to understand is the relationship between Field Groups, Fields, and Location Rules. Everything else builds on that foundation. Read the “How the Pieces Fit Together” subsection above twice if needed — once it clicks, the rest of the plugin makes intuitive sense.
—