Access is decided per article, not per site
Most WordPress documentation themes solve structure — categories, sections, a sidebar. Manual's vendor description spends more detail on who gets to read a given page. Each documentation post, and each knowledge base post, can be public, open to any logged-in user, or limited to specific logged-in users with special permissions. The same choice is offered at two levels: on a single post, or across every post filed under a category.
Attachments are governed separately. The vendor says documentation and knowledge base posts can carry unlimited file attachments, and that you decide whether those files are public or only available to logged-in users, independently of the article's own setting. If you publish a public release note that references a premium download, that distinction is what keeps the article visible and the file gated.
Neither feature depends on a plugin from the vendor's list; the restrictions are described as theme options driving the WordPress content you already have. Still, permission behaviour is the kind of thing that only reveals its edges when real roles are involved, so it is worth testing with a genuine subscriber, a member and an anonymous visitor rather than a single admin session.
Live search that can be narrowed to the fields you care about
The vendor describes live search with an unusual number of dials. Basic ones first: AJAX or standard search behaviour, a configurable search box, term highlighting in results, trending searches printed below the box, and a switch for whether private articles appear in results.
The narrower controls matter on a manual that has grown past a few dozen pages. You can target search at specific post types and at categories within documentation and knowledge base content. Matches can be limited to titles, to content, or to excerpts — so a manual can favour headings without surfacing every passing mention in a long tutorial. Search can be restricted to chosen taxonomies, run against a particular author's posts, or set to exclude older results.
The last group is technical and worth reading twice: the relationship between multiple search terms can be set to AND or OR, and queries can match exactly or partially. On a help site where users type "invoice export" and mean both words, AND is the useful default; on a site with product names that share prefixes, partial matching saves failed searches. Neither setting is right everywhere, which is presumably why the vendor exposes it.
The reading page: tree menu, table of contents, voting
Navigation for documentation runs through a tree menu with its own options: private articles can be hidden from it, the tree can open expanded, and a scrollbar can appear once the menu passes a set height. The documentation page then adds choices that change how reading feels. Articles can load through AJAX or load normally, the tree sidebar can sit in different positions, and a table of contents can be inserted inside the post alongside a selectable post title tag.
Feedback tools sit on the same page. Article voting can be turned on or off and its access limited, comments can be switched off, and related posts and next/previous links can each be shown or hidden. On knowledge base single pages the vendor describes a conditional comment box: it appears only after someone clicks the thumbs-down feedback button. That is a narrow feature, but it changes the conversation — a comment prompt arrives attached to a complaint rather than sitting open under every article.
The knowledge base category page has shorter controls: sidebar on or off, whether child categories are listed under the parent, and the order records display in. FAQ follows a similar pattern with its own twist, a hash search that shows results on the same FAQ page instead of sending visitors elsewhere.
Printing moved into the theme in 7.5.4
The version 7.5.4 changelog entry dated 24 May 2024 records that the theme no longer needs the Print-O-Matic plugin because it has its own print function. The vendor's instruction attached to that entry is direct: disable Print-O-Matic after upgrading. Anyone maintaining an older install that relied on the plugin should treat that as an upgrade step rather than an optional tidy-up, since two print paths on one documentation page would be redundant at best.
That entry is also the clearest available signal of how this theme ages. It is maintenance of the documentation features themselves — printing, attachments, the article page — rather than a new demo. Which version arrives in any given package is a separate question the product page interface answers.
What ships and what the vendor claims compatibility with
The vendor names an unusually wide plugin set: WPML for translation, LearnPress for courses, bbPress for forums, Elementor and WPBakery for page building, and Contact Form 7 for forms, alongside WooCommerce for a shop. The package is described as including WPBakery pro files and pro files for Ultimate Addons for WPBakery, plus a child theme and translation-ready .po files. These are vendor statements about the product; the marketplace file list itself names PHP, CSS and JS files.
There is a label worth understanding. The listing marks Gutenberg Optimized as No, while the vendor separately offers an on/off switch for the Gutenberg editor when creating documentation, knowledge base, portfolio and FAQ articles. That switch suggests the theme has taken a position on the block editor rather than ignored it, but the listing label should not be read as proof that the block editor is unavailable — read the vendor's editor option instead, and check it on your own install.
The theme's declared WordPress support in the metadata observed on 3 November 2026 runs from 5.9.x to 6.5.x, with WooCommerce 8.x.x and 7.x.x and 6.x.x named in the compatibility attributes. The vendor's own update note is older than that observation, so treat the upper end of the range as a claim to confirm before committing.
Manual's vendor description frames it as a documentation and support product first and a multipurpose theme second. If your project is a help centre, a product manual or a customer knowledge base with gated content, three checks in a staging install will tell you more than any feature list: whether your access rules and file permissions behave as described across roles, whether live search returns sensible results at your real article volume, and whether the print and comment behaviour matches how your team answers support questions.
Questions & answers
Can parts of a Manual documentation site be private?
Yes, according to the vendor description. Documentation and knowledge base posts can be public, visible to any logged-in user, or restricted to specific logged-in users with permissions, set either on a single post or across all posts in a category. Files attached to those posts have their own public-or-logged-in setting.
Does Manual work with the block editor?
The marketplace listing marks Gutenberg Optimized as No, but the vendor describes a toggle that activates or disables the Gutenberg editor when creating documentation, knowledge base, portfolio and FAQ articles. The listing label alone does not establish whether the block editor can be used — test the toggle on your install.
Which page builders does the vendor list for Manual?
The vendor claims compatibility with both Elementor and WPBakery, and states the package includes WPBakery pro files and pro files for Ultimate Addons for WPBakery. These are vendor claims about the package, not a description of what the marketplace file list contains.
Do I still need the Print-O-Matic plugin?
No, from version 7.5.4 onwards. The changelog entry of 24 May 2024 says the theme now has its own print function and asks users to disable Print-O-Matic after upgrading.
