This short chapter covers two settings that shape how your finished articles look and feel to both you (as the editor) and your site’s readers.
Overview
Under Post Options in Settings, two toggles control the “shape” of every generated article: whether it’s saved using WordPress’s modern block editor format (so you can easily edit it afterward), and whether the plugin applies its own built-in, reader-friendly visual styling to things like callout boxes, tables, and FAQs on the live site.
How It Works
When Gutenberg blocks is enabled, the plugin converts its generated HTML into the same block format you’d get from typing directly into the WordPress editor – meaning headings, paragraphs, and lists all become fully editable blocks you can rearrange or tweak by hand. When blog content styling is enabled, extra CSS is loaded on the front end of your site so elements the AI creates – like a summary callout at the top of the article or the FAQ section – display attractively without you writing any custom design work.
Step-by-Step Guide
1. Open the Post Options panel
Go to AI News Publisher → Settings and scroll to the Post Options panel.
2. Enable Gutenberg blocks
Tick Save content as Gutenberg blocks so every generated post opens as fully editable blocks in the WordPress editor, instead of one large uneditable chunk of HTML.
3. Enable blog content styling
Tick Apply blog content styling on the frontend to automatically add readable typography, styled callout boxes, tables, and FAQ formatting to every AI-generated post your readers see.
4. Save your settings
Click Save Settings.
5. Open a generated post in the editor
Go to Posts → All Posts, open a recently generated article, and confirm you can click into and edit individual paragraphs, headings, and the FAQ section as separate blocks.
6. Preview the live post
View the published article on your live site and confirm the summary callout, tables, and FAQ section appear with clear, attractive styling rather than plain unstyled text.
7. Adjust to match your theme (if needed)
If your WordPress theme already has strong built-in article styling and the plugin’s styling looks like it clashes, you can turn Apply blog content styling on the frontend off and rely on your theme’s own design instead.
Fields Table
| Field Name | Description | Example |
|---|---|---|
Save content as Gutenberg blocks |
Converts generated HTML into native, editable WordPress block markup. |
Enabled |
Apply blog content styling on the frontend |
Adds built-in CSS styling for summary callouts, tables, and FAQs on the live site. |
Enabled |
Field Explanations
Gutenberg blocks mainly affects the editing experience for you and your team – it makes generated posts feel just like any other WordPress post you’d write by hand, rather than a locked block of code.
Blog content styling mainly affects what readers see on the live site. Turning it off doesn’t remove any content – it simply stops the plugin’s extra visual design from being applied, falling back to your theme’s plain default styling for those elements.
These two settings work independently – you can mix and match them however suits your site, for example enabling Gutenberg blocks for easier editing while relying on your own theme’s styling instead of the plugin’s.
Tips
- Keep both toggles on to start – you get an editable post and an attractive live design with zero extra work.
- Preview a generated post on the live site (not just in the editor) to judge how the styling actually looks to readers.
- If your theme already has custom blog styling, compare both settings on and off to see which combination looks best on your site.
Common Mistakes
- Turning off Gutenberg blocks and then struggling to edit a post. Without it, generated posts save as one large HTML block that’s harder to fine-tune by hand.
- Assuming turning off blog content styling deletes content. It only removes the extra visual design – all the text, headings, and FAQs remain exactly as written.
- Never previewing the live post. The editor view and the public-facing view can look different – always check both.