The practical way to create a WordPress knowledge base is to use a documentation plugin, design your product-and-section hierarchy before writing, then publish task-focused articles with search, breadcrumbs, and related links. For a video-game site, that can turn scattered setup guides, controller fixes, account instructions, and patch notes into a help center that readers can navigate without opening a support ticket.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Start by deciding who the documentation serves and whether one site will cover one game, a studio’s catalog, or several unrelated products. Then choose a plugin whose content model, search behavior, theme support, and multi-product structure match that decision. The workflow below covers planning, installation, article production, discovery, testing, and maintenance.
As an Amazon Associate I earn from qualifying purchases.
What a WordPress knowledge base should do
A knowledge base is a dedicated documentation area rather than a chronological blog. Readers arrive with a specific problem—such as linking a controller, recovering a save, or understanding a multiplayer setting—and need a direct answer, a reliable path to related procedures, and a search box that recognizes the words they use.
A suitable WordPress knowledge-base plugin normally adds an article content type and taxonomies for organizing it. Depending on the plugin, you can also get hierarchical navigation, breadcrumbs, live search suggestions, related-article panels, reusable blocks or shortcodes, and an automatic table of contents. Those features matter because a help center is useful only when readers can find the correct article and understand where it belongs.
#1 Best Overall
Plan the information architecture before installing anything
Define the audience and scope
Write down whether the documentation is for customers, internal staff, developers, or a mixture. A public game-support center may need plain-language troubleshooting, while developer documentation needs API references and version-specific implementation notes. If several audiences share one site, decide whether they should have separate top-level areas.
Also list the products covered. One game can use sections such as Getting started, Accounts, Gameplay systems, Troubleshooting, and Accessibility. A site covering several games should give each game its own product area so a reader never has to distinguish one title’s controller instructions from another title’s.
Sketch a hierarchy readers can predict
Draft the top-level products or audiences and the sections beneath them in a document or whiteboard before creating content. Keep section names stable and reader-facing. A player is more likely to look for “Controller and input” or “Account and login” than an internal team label such as “Platform operations.”
Use hierarchy for broad grouping and tags for cross-cutting subjects. For example, a “PC installation” article can live in the PC section while carrying tags for Steam, launch errors, and graphics settings. Do not create a new category for every phrase that appears in a search query; that produces a menu no one can scan.
Choose a content model
A dedicated plugin is the practical route when you need a separate article type, taxonomies, parent-child hierarchy, searchable archives, related articles, breadcrumbs, or reusable display components. Keeping documentation as ordinary posts can work for a small blog, but it becomes difficult to keep support content separate from news and editorial updates as the library grows.
The two common models are a single knowledge base with products, sections, and tags, or several independent knowledge bases. Choose the first when all products share one search and visual system. Choose independent bases when each product needs a distinct home, navigation tree, or editorial ownership.
WordPress knowledge-base plugins to evaluate
These options are documented for different types of documentation sites. Feature lists and compatibility requirements can change, so check each plugin’s current listing before installation.
| Option | Best fit | Structure and discovery | Documented distinguishing capabilities |
|---|---|---|---|
| Knowledge Base by WebberZone | Customer help center, FAQ, wiki, or multi-product documentation | Products, sections, tags, article custom post type, live search, related articles, breadcrumbs, blocks, automatic table of contents | The listing documents a setup wizard, Multi-Product mode, article creation, live search suggestions, related articles, and article, section, and product blocks. |
| Documentation by itthinx | Manuals, developer documentation, team wiki, or a documentation portal | Separate document area, parent-child hierarchy, categories, tags, search form, widgets, and shortcodes | The listing says documentation is kept separate from regular posts and pages, supports thousands of documentation pages, and provides navigation shortcodes. |
| BasePress Docs | Several independent product or service knowledge bases | Multiple knowledge bases, sections, and articles | Its setup wizard requires a knowledge base, a section, and an article before the knowledge base appears, and it is designed for multiple independent bases. |
| AssistCamp | Documentation sites using either a block theme or a classic theme | Adaptive URLs, REST live search, onboarding wizard, and navigation blocks | The listing documents support for full-site-editing and classic themes, adaptive URL structure, onboarding, and live search. |
Compare the factors that affect your decision
- Content model and taxonomy: Check whether the plugin gives you the article type, products, sections, categories, tags, and parent-child relationships you mapped.
- Search quality: Look for live suggestions, relevant matching, and a search form that can be placed where readers expect it.
- Navigation: Confirm support for breadcrumbs, section lists, child-document lists, related articles, and automatic tables of contents if those are part of your design.
- Theme and editor compatibility: Verify whether your site uses a block theme, a classic theme, blocks, widgets, shortcodes, or a combination.
- Multiple products or bases: Determine whether products are taxonomies inside one base or separate knowledge bases with independent navigation.
- Access control and analytics: If some documents are private or you need article-level usage data, verify those capabilities directly rather than assuming the plugin includes them.
- Migration and export: Decide how articles, taxonomy assignments, and URLs could be moved if you later change plugins.
Install and activate the plugin
- In the WordPress dashboard, open Plugins and choose Add New.
- Search for the plugin name or for “Knowledgebase” or “Knowledge Base.”
- Install the selected plugin and choose Activate.
- Open the new knowledge-base menu. The Knowledge Base listing says activation opens its setup wizard; other plugins may place onboarding under their own menu.
Before importing a large library, create a staging copy or at least back up the site. Confirm that the plugin’s current WordPress-version requirements, theme support, and editor behavior match your environment; those details are subject to change.
Build the structure in the setup wizard
Knowledge Base by WebberZone
Choose Multi-Product mode when one site documents several games or services. Add the products first, create the sections beneath each product, then use Knowledge Base » Add New to create articles and assign them to the appropriate sections. Use tags only for useful cross-product subjects.
Documentation by itthinx
Create the separate documentation area, then establish parent and child documents, categories, and tags. This keeps manuals and reference material apart from ordinary posts and pages while preserving a hierarchy readers can browse.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteBasePress Docs
Follow its wizard to create a knowledge base, at least one section, and an article. The listing states that all three are needed before the knowledge base is displayed, so do not stop after creating only the top-level container.
AssistCamp
Complete the onboarding wizard, then check the generated URL structure and navigation blocks in both the editor and the front end. Its documented adaptive URLs and REST live search make an early theme-and-permalink check especially important.
Create products, sections, categories, and tags
Products
Use a product level when the reader’s first decision is “Which game or service is this about?” Give each product a clear landing page that lists its sections and offers search scoped to the site’s documentation.
Sections
Organize sections around jobs readers perform, not around the department that wrote the content. A game-support structure might include Installation, Accounts, Controls, Online play, Accessibility, Troubleshooting, and Safety. Keep the number of top-level sections small enough to scan.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Categories and parent-child documents
Use categories or parent documents for depth that genuinely helps. For a developer portal, an SDK overview can parent authentication, error handling, and versioning pages. For player support, a “Fix launch problems” parent can lead to platform-specific child articles.
Tags
Tags are most useful when an article belongs in one section but should be discoverable through another concept, such as a platform, error code, or feature. Review tags periodically and merge near-duplicates; a tag cloud with dozens of one-off labels is not navigation.
Write task-focused articles
Match titles to real questions
Use titles that resemble the words a reader types: “How to remap a controller on PC,” “Why does the game show a sign-in error?” or “How to restore cloud saves.” Put the outcome in the title and avoid internal ticket numbers.
Give each article one clear outcome
Start with a short statement of what the reader will accomplish and any prerequisite, then provide numbered steps. If a problem has separate Windows and console procedures, split them into clearly labeled branches rather than mixing instructions in one paragraph.
Recommended Free Tools
Use a repeatable article pattern
- Outcome: State the result in one sentence.
- Before you start: List account access, permissions, platform, or version requirements.
- Steps: Number the exact clicks, menu names, commands, or settings.
- Expected result: Tell the reader what they should see after completing the procedure.
- If it fails: Add the next diagnostic action or link to a focused troubleshooting article.
- Related tasks: Link to the next likely procedure, not to a random list of content.
Add screenshots carefully
Use screenshots when a control is difficult to identify, and annotate only the relevant area. Include alternative instructions when a WordPress, game, or plugin update changes the interface. Keep image captions specific so a reader can understand the step without guessing what to look at.
Publish search and navigation paths
After creating content, publish the plugin’s knowledge-base archive or page and make it reachable from the site’s main navigation. Put a search form near the top of the knowledge-base landing page and on article pages where the plugin permits it.
Knowledge Base documents live search suggestions, related articles, breadcrumbs, article, section, and product blocks, plus an automatic table of contents. Use those components to provide several routes: search for a phrase, browse a product, move through sections, or jump to a heading inside a long article.
Documentation provides a search form, hierarchy, category lists, child-document lists, widgets, and shortcodes. Place the search form on the landing page, use category and child-document views where they clarify the hierarchy, and reserve shortcodes for layouts that blocks or widgets cannot provide.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesDo not rely on search alone. A reader who searches for “controller not detected” should find a useful result, but a reader who opens the controller section should also see the likely setup and troubleshooting articles without entering another query.
Support several products on one WordPress site
One WordPress installation can document multiple products when the plugin supports a product taxonomy or multiple independent knowledge bases. Choose a shared base with product separation when you want one search experience, shared design, and common tags. Choose independent bases when each product needs its own navigation, ownership, or URL structure.
Keep each product’s sections separate. Shared tags such as “account,” “controller,” or “accessibility” are helpful only when they lead to genuinely related articles across products. If a tag returns a confusing mixture, replace it with product-specific categories or clearer titles.
Give every product a recognizable landing page and test that breadcrumbs identify both the product and section. This prevents a reader from following a link from one game’s article into another game’s instructions.
Free tools Windows power users keep installed
One-click scans. No signup required.
Test the reader journey before launch
- Collect real support questions from search logs, tickets, comments, or community posts.
- Enter each question into the knowledge-base search and note whether the first results use the same language as the question.
- Open a result and follow every numbered step on a clean account or test environment where practical.
- Use breadcrumbs, section navigation, related-article links, and the table of contents to reach the next likely task.
- Repeat the journey on a phone and a desktop browser. Check that menus, code samples, screenshots, and search suggestions remain usable.
- Test product boundaries by opening an article from each product and confirming that navigation does not silently switch to another one.
Troubleshoot common setup problems
The knowledge base page is empty
Check that the required structure exists. BasePress Docs specifically requires a knowledge base, a section, and an article before display. In other plugins, confirm that at least one article is published, assigned to a visible section, and not excluded by a status or visibility setting.
Search returns no useful results
Compare the reader’s wording with article titles and headings. Add the exact terms people use, then retest with synonyms, platform names, and error codes. Confirm that the search form points to the plugin’s documentation search rather than the site-wide blog search.
Best Value
Breadcrumbs or child pages show the wrong order
Review parent assignments and section or category ordering. Remove duplicate parent relationships and use a consistent naming pattern. Test the front end after changing permalinks or URL settings.
The layout conflicts with the theme
Check the plugin in both the editor and the published page, then test at mobile widths. A block-based plugin may need different placement from a widget or shortcode-based layout. Disable one conflicting customization at a time so you can identify whether the issue comes from the theme, a page builder, or another plugin.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →A live-search suggestion opens an unexpected URL
Inspect the article’s permalink, product assignment, and redirects. For plugins with adaptive URLs or REST-powered search, verify that the generated URL remains valid after changing the site’s permalink structure.
Maintain the documentation as a product
Assign ownership
Give each product or section an owner responsible for accuracy. Ownership should include reviewing reader feedback, checking outdated screenshots, and deciding when a duplicate article should be merged or retired.
Review high-traffic articles first
Prioritize pages that readers reach most often or that generate repeated support questions. Confirm that the procedure still matches the current WordPress, plugin, game, platform, or account interface before changing lower-use reference pages.
Update after interface changes
When WordPress or the knowledge-base plugin changes its menus, repeat the reader journey and replace screenshots that no longer match. If a game update changes a setting name or location, record the affected version in the article and revise the steps.
Keep navigation clean
Retire obsolete procedures, redirect their URLs when necessary, and merge articles that answer the same question. Recheck category and tag names during each review cycle so the structure remains understandable to a new reader.
A practical selection checklist
- Have you identified the audience and every product or service the site will document?
- Can the plugin represent your planned products, sections, hierarchy, categories, and tags?
- Does its search provide the behavior you need, including live suggestions if required?
- Can readers browse with breadcrumbs, section lists, related articles, or child-document navigation?
- Will the plugin work with your block or classic theme and your preferred blocks, widgets, or shortcodes?
- Do you need one shared knowledge base or several independent bases?
- Have you checked current WordPress-version requirements, compatibility, access controls, analytics, migration, and export options?
- Is there an owner and review schedule for every product or section?
What success looks like
A well-built WordPress knowledge base lets a reader arrive with a question, find an article that matches the question, complete one focused procedure, and move naturally to the next task. The plugin supplies the content model and discovery tools; your information architecture, writing discipline, testing, and maintenance determine whether the help center is actually usable.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
