General Questions​

Summary: Get clear answers to common Antimanual Builder questions about theme compatibility, page builders, AI keys, licensing, content limits, and editing workflows before you start building your WordPress pages.

General questions about Antimanual Builder typically focus on compatibility, workflow, and how the plugin behaves in a real WordPress environment. This section explains the most common concerns so you can assess whether Antimanual Builder fits your site, your team, and your publishing process.

If you are planning to use the builder for existing pages or new documentation layouts, it is important to understand the relationship between the free plugin, the Pro add-on, and any optional companion plugin. For setup details, see Optimizing WordPress: Disabling Forum and eCommerce Features While Retaining Helpdesk Functionality and How to Install the Docy Core Plugin for the Docy WordPress Theme.

Will my pages match my theme?

Antimanual Builder is designed to work within your WordPress environment while respecting your theme’s existing presentation rules. In most cases, the final appearance will follow the typography, spacing, and layout behavior defined by your active theme and global settings.

That said, exact visual results can vary depending on custom CSS, theme templates, and page-specific settings. If your site uses highly customized design rules, test a few sample pages before rolling out a full documentation set. This helps confirm that headings, buttons, content width, and responsive behavior display as expected.

• Theme styles can influence typography, spacing, and colors.
• Global WordPress settings may affect page layout consistency.
• Custom CSS can override builder output in specific areas.
• Desktop, tablet, and mobile testing is recommended before publishing.

Can I use Antimanual Builder alongside other page builders?

In many cases, yes. You can keep other page builders installed if they are required for existing content or legacy pages. This is useful when a site is migrating gradually rather than replacing all layouts at once.

For the best experience, decide which builder is responsible for each content area. Mixing multiple builders on the same page can create inconsistent spacing, script conflicts, or duplicate design controls. A clear content strategy helps keep editing predictable for both developers and content teams.

• Use one primary builder for new pages whenever possible.
• Keep legacy builders only where they are still needed.
• Check compatibility after activating new plugins or theme updates.

Do I need the companion plugin or a Pro license?

Whether you need the companion plugin or Pro license depends on the workflow you want to use. The free plugin provides the required base installation, while Pro unlocks advanced features and premium workflows. The companion plugin is optional in some setups but may be required for AI-driven features or integrated assistance.

If your goal is to build pages manually, you can often begin with the base plugin and expand later. If you want AI-assisted generation, conversational refinement, or deeper connected workflows, review the licensing and dependency requirements before starting. For more detail, see and How to Customize 404 Page Text and Images in WordPress Themes.

Do I need an AI API key?

You only need an AI API key if you plan to use AI-powered features such as page generation, refinement, or AI-assisted migration. The AI provider is used only when you explicitly trigger an AI action in the interface.

This makes the workflow straightforward for teams that prefer manual editing. If you are still deciding which provider to use, verify your configured source, token limits, and provider availability before starting a project. This reduces interruptions during content generation and review.

How many questions or pages can I generate at once?

Antimanual Builder is designed to support practical, repeatable workflows rather than forcing a single large export. For FAQ-style generation, you can work in batches and run the tool multiple times to create a larger library. This is helpful when you need different sets for products, departments, or audience segments.

For broader page creation, large imports and multi-page projects are handled with features such as chunked uploads, background processing, and per-page previews. These tools are intended to make bigger jobs easier to manage without losing visibility into what is being created.

• Use smaller batches for easier review and approval.
• Split content by topic, product, or user role.
• Review generated output before publishing.

Will my content remain editable?

Yes. Antimanual Builder is intended to support ongoing editing, not just one-time generation. You can review content, adjust it manually, and continue refining pages as your documentation evolves. This is especially important for teams that maintain product guides, support content, or onboarding material.

Generated content should be treated as a starting point. Use it to accelerate production, then verify accuracy, tone, and structure before publishing. If your site depends on changing product behavior or policies, schedule periodic updates so the documentation remains aligned with reality.

What is the best workflow for new users?

New users usually get the best results by following a staged workflow: install the free plugin, confirm requirements, activate Pro if needed, and then create a test page before building the full content set. This approach lowers risk and makes it easier to identify theme or permission issues early.

• Confirm WordPress and PHP versions first.
• Install and activate the free base plugin.
• Set up Pro or the companion plugin only if your workflow requires them.
• Build one sample page and test it across devices.

If you need help deciding between manual editing and AI-assisted creation, review the build options in How to Keep All FAQ Tabs Closed on Page Load in the Docy Theme (Elementor) and How to Install the Docy Core Plugin for the Docy WordPress Theme.

Quick answers at a glance

• Yes, pages generally follow your theme’s existing design rules.
• Yes, other page builders can remain installed when needed.
• No, you do not need AI for manual workflows.
• Yes, you can generate content in batches and refine it later.
• Yes, content remains editable after generation or import.

Understanding these general questions helps you plan a smoother setup and avoid common implementation issues. Once the basics are clear, you can move confidently into installation, first-page creation, and advanced content workflows.