Give a page its own fields in the admin
wp-fields-group="Menu" The name of the box of fields the client sees when editing the page. Every page with editable content needs it, and it is the first attribute to place.
Where it goes
On the <body> of each page: <body wp-fields-group="Menu">. All the fields you mark on that page land in one box with this title on the page’s edit screen.
On index.html the box belongs to the home page, on menu.html to pages using the Menu template, on single.html to blog posts. For site-wide settings it goes on the <body> of theme-options.html.
Example: the Menu page
<body wp-fields-group="Menu">
<h1 fld-text="Title">Menu</h1>
<p fld-area="Lead">Espresso runs on our “Warm” blend.</p>
</body>Espresso runs on our “Warm” blend.
What matters
- Without
wp-fields-groupthe page gets no fields at all, and the build log says nothing about it. Check it first when the admin looks empty. - Give every page its own name: “Menu”, “Contacts”, “Home page”. The name is what the client reads above the fields.
- A page can have several groups: put the attribute on sections instead of the
<body>, and each section gets its own box.
Common mistakes
The build log is the “Logs” tab of your project on themeforge.pro; the free markup check shows the same notes.
<body>
<h1 fld-text="Title">Menu</h1>
</body>A page without a group name: the template reads the fields, but the admin never creates them, and the log is silent.
<body wp-fields-group="Menu">
<h1 fld-text="Title">Menu</h1>
</body>The same page with wp-fields-group on the <body>.
Alternative spelling
wp_meta works the same: the build gives an identical theme.