Find the right website building block, understand what a change affects, and open its original editor. The website administrator curates a small handover guide; content stays in WordPress and its active builders. You do not need a guide for every content item. Start with frequent maintenance tasks, common stumbling blocks and shared templates whose changes affect several places.
Version 1.0.0 · Stable Release · WordPress 7.0+ · PHP 8.0+
User guide · FAQ by topic · Documentation · Deutsch
- At a glance
- Getting started
- Features
- Everyday tasks
- Frequently asked questions
- Data and lifecycle
- Optional online services
- Testing status
- Changelog
- About the author
- Issues and support
- Support development
- License and bundled components
- Find everyday tasks using search and website areas.
- Open the original WordPress or builder editor with existing permissions.
- Explain usage, effects and numbered editing steps.
- Curate WordPress content, navigation and active builder templates.
- Provide reader help and an optional support contact.
- Choose reader roles and adapt the admin menu label and icon.
- Copy guide links and duplicate guides into hidden drafts.
- Install the supplied plugin ZIP on a staging website and activate Builder Content Guide.
- Open Find content → Manage guide as a website administrator.
- Pick a few useful tasks, such as renaming a menu item, updating the footer phone number or maintaining a shared contact template.
- Add a guide entry, choose an original and describe name, purpose, area, effects, usage and editing guidance.
- Enable visibility deliberately. Under Guide access, explicitly select the roles that may read visible entries.
- Try three actual maintenance tasks with an editor before using the guide for a client handover.
- Menu paths use the default name Find content; a custom menu name replaces that entry point on your website.
Compact task list with search by name, purpose and original title, an area filter and a detail panel. Direct admin submenus provide access to finding content, managing the guide and adding entries.
WordPress pages, posts, template parts, block navigation and classic menus; patterns, active Elementor Free/Pro documents, Bricks templates and GeneratePress Elements.
Manual effect and usage explanations, editing guidance and deliberately enabled reader visibility.
Separate reader access and management permissions. Editor links require existing original and builder permissions.
Missing, trashed and disabled sources keep their references and have no active editor link.
Reader help explains supported sources and shows an optional, administrator-maintained support contact. Extra search terms make everyday tasks easier to find.
Search/filter originals by provider and content type; add or find guides at originals, open checked example pages, follow ordered steps, copy direct links and duplicate guides as hidden drafts.
Adapt the top-level admin menu name and icon per website, for example Instructions. Leave the name empty to restore the translated default Find content.
The German demonstration view shows three everyday tasks: change contact text, rename a menu item, and change the footer phone number. The custom menu name is Anleitung (Instructions).
No. Focus on typical problem cases, common stumbling blocks and frequently edited templates. A few clear instructions can be more useful than a complete catalog.
No. It stores original references and explanations. Original content remains in its own system.
No. Reader access only reveals curated explanations. WordPress object permissions and Bricks builder permissions still control editing.
No. The administrator describes them manually. Unknown effects are labeled Check usage. No automatic usage counts are shown.
Its reference and last known title remain. The administrator sees a review notice and readers have no active edit action.
Guide entries and role grants belong to each website. Network activation is supported; new sites start with an empty guide and no role grants.
Guide entries and access settings remain. The updater cache is removed. The embedded Library follows its shared last-host cleanup rules and preserves data by default.
Guide entries, reader access, support contact and menu preferences are stored separately for each website. Original content remains in its own system. Deactivation and uninstall preserve guide data and settings. Uninstall removes the updater cache; the shared Library retains its own data by default.
The guide works locally and has no cloud or AI service dependency. Bundled deckerweb Library 0.8.1 offers an optional plugin catalog; its online catalog starts disabled. The bundled deckerweb Updater 2.1.0 uses GitHub through the native WordPress update workflow. GitHub receives standard WordPress HTTP request metadata and the public repository path. No guide entries or original content are sent. Source code is available at https://github.com/deckerweb/builder-content-guide. No stable release has been published yet.
Runtime checks: WordPress 7.0 with PHP 8.1.29 and WordPress 7.1.3 with PHP 8.4.5. PHP 8.0 has not been tested. Tested with Elementor Free 4.3.4 and Elementor Pro 4.3.1. Inactive document types are unavailable; clipboard failure falls back to selecting the link for manual copying.
- New: Curated content guide for WordPress patterns, Bricks templates and GeneratePress elements.
- New: Reader help with supported content types and an optional support contact.
- New: WordPress pages, posts, template parts, block navigation, classic menus and active Elementor Free/Pro document types.
- New: Searchable original selection, related guide links, example pages, ordered editing steps, copyable direct links and duplication as invisible drafts.
- New: Customizable site admin menu name and bundled WordPress icon.
- Improved: Direct admin submenus for finding content, managing the guide and adding entries.
- Improved: Additional search terms, help after unsuccessful searches and reminders before editing shared building blocks.
Developed and maintained by David Decker – DECKERWEB. Builder Content Guide focuses on a small editorial handover rather than a second template library.
Report vulnerabilities privately using GitHub private vulnerability reporting. Do not publish unpatched vulnerability details in public issues. For reproducible non-security bugs use GitHub Issues.
For editing help on your website, use the support contact configured by your administrator.
Ko-fi · Buy Me a Coffee · PayPal
Copyright © 2026 David Decker – DECKERWEB. GPL-2.0-or-later. Bundled unchanged deckerweb Library 0.8.1 and deckerweb Updater 2.1.0 by David Decker, both GPL-2.0-or-later. Sources: https://github.com/deckerweb/deckerweb-plugin-library and https://github.com/deckerweb/deckerweb-updater. No Elementor, Bricks or GP Premium source code is included.