Skip to content

[00] Subset Fill, User guide

Move content into ACF Flexible Content

Last updated

Move an article into ACF Flexible Content layouts by hand, row by row, or paste it into Subset Fill and review the rows before you save.

To move content into ACF Flexible Content, you add a row for each section, pick its layout and copy each passage into the right sub-field. Subset Fill does the copying for you: paste the whole article, click Build, and the AI places your words into your layouts, word for word, as unsaved rows you review before you click Update.

Doing it by hand

ACF has no import for Flexible Content, so moving an article from a Word file, an old page or a classic editor post is copy and paste:

  1. Read the source and decide which layout each part belongs in.
  2. In the post, click Add Row and choose the layout.
  3. Copy each heading, paragraph, link and image into its sub-field.
  4. Repeat for every section, then check the rows are in the source’s order.

A long page means dozens of rows. The copying takes most of the time, and it’s also where the mistakes happen: a paragraph pasted twice, a link left behind, a heading retyped with a typo.

What Subset Fill does instead

Subset Fill adds a Build from content button to a Flexible Content field. You paste the article, and an AI model chooses a layout for each part and fills the sub-fields from your text. It arranges your content into the layouts you already have. It doesn’t write anything, change your field group or touch your templates.

You need ACF PRO or Secure Custom Fields, because free ACF doesn’t include Flexible Content. Installing the plugin and choosing an AI provider are covered in Getting started.

Set up the field group

The person who builds the field group decides what the AI can do with it. Every setting below is stored on the field, so it travels with your ACF JSON. Edit the field group, open the Flexible Content field and switch on Content builder. Then, for each layout:

  • Builder description says what the layout is for and when to use it, such as “A pull quote with attribution. Use for a standout quote.” The AI chooses layouts by these descriptions, so they matter more than any other setting. When two layouts are close, say what separates them.
  • Builder max per page is the most times the AI may use the layout. Unlike ACF’s own Max, editors can still add more by hand.
  • Builder position is Anywhere, At the start or At the end. Use the start for a hero and the end for a closing call to action.

Each sub-field inside a layout has its own Content builder setting:

  • Fill from pasted content, the default.
  • Always leave for a person, for things your content never contains, such as a background colour. The AI isn’t asked for that field at all, and the editor sees “Left for you” next to it after a build.

The AI also reads each field’s label and instructions. “Headline: the short title at the top of the section” gets better results than “Title”. If a field should only take one kind of text, say so in its instructions, for example “The price, only if the source gives one”.

A layout without a Builder description is chosen by its label alone.

The word-for-word rule

The AI is told to copy text exactly from your content, with the same words in the same order and the same spelling and punctuation. It may not summarise, paraphrase, shorten, translate, correct or add words, and that includes headings and button text. When a field has no matching text, it’s left empty, even when the field is required.

The rule is checked as well as asked for. Before the rows reach the editor, every text value, link, email address, image source and number is compared with what you pasted. Anything that isn’t in your content is cleared, and the field is flagged with “Some of this text wasn’t in your content and was removed. Check it.”

This has one consequence for your layout descriptions. A description such as “A short summary of the section” asks the AI to write a summary, and the check will clear it. Ask for a passage that’s already in your content: “The paragraph that introduces the section.”

Build and review before you save

  1. Open a post that shows the field and click Build from content.
  2. Paste your content. Headings, paragraphs, lists, links, quotes, tables and images come across.
  3. If the field already has rows, choose Add the new rows after them or Replace them.
  4. Click Build.

Long content is split at headings and built in parts, and you’ll see “Building part 1 of 3” while it runs.

The rows appear in the field unsaved. A summary bar shows how many rows were built, how many fields need attention and how many passages weren’t placed. Before you save:

  • Look at each flagged field. It’ll say whether text was removed, nothing matched, or the field type isn’t supported yet and needs filling by hand.
  • Click Show leftovers to see passages the AI didn’t place, and Copy to paste them where they belong.
  • Check image fields. An image is filled only when it’s already in your Media Library, so others are flagged for you to choose.

Click Undo build to put the field back as it was, including any rows you chose to replace. Nothing is saved until you click Update.

Check your descriptions without a build

If you use WP-CLI, --plan prints how your content would be split and the first prompt, with all your layout descriptions, without calling the provider:

wp subset content-builder map field_sections article.html --plan

The first argument is the Flexible Content field key and the second is an HTML or plain-text file. Leave out --plan to run the build and print the rows as JSON. Nothing is saved either way.

With Pro

Subset Fill Pro adds two more sources to the Build box, Word file and Web address, so you don’t have to copy the article out first. It also fills relational fields, nested Flexible Content and clone fields. See Pro in Getting started.