A question and answer section your experts actually answer.
An Elementor widget that turns the comments WordPress already has into a moderated Q&A section. Visitors ask, nothing appears until someone approves it, and an answer from the expert looks different from an answer from the support desk. No forum plugin, no external service, and every colour, font, spacing and word is editable in the panel.
A Pigment Dev product, installed and configured as part of the sites the studio builds, and available on its own. I co-founded Pigment Dev and lead its development.
Your questions
12 publishedIs the follow up visit necessary if everything looks normal after two weeks?
Yes, keep it. Two weeks is early for the result we are checking, and the visit takes only a few minutes.
We have sent you the available times by email. Reply to that message to pick one.
Your name
M
Please write your full name, at least two characters.
Your question
Type your question here
Every question waits for approval. Links inside a question are never clickable.
پرسشهای شما
۱۲ منتشرشدهاگر بعد از دو هفته همهچیز طبیعی به نظر برسد، باز هم ویزیت پیگیری لازم است؟
بله، حتماً بیایید. دو هفته برای نتیجهای که بررسی میکنیم زود است و ویزیت فقط چند دقیقه طول میکشد.
زمانهای خالی را برایتان ایمیل کردهایم. برای انتخاب وقت، به همان پیام پاسخ دهید.
نام شما
م
لطفاً نام کامل خود را بنویسید، دستکم دو حرف.
پرسش شما
پرسش خود را اینجا بنویسید
هر پرسش پیش از انتشار بررسی میشود. پیوندهای داخل پرسش قابل کلیک نیستند.
What is in that section
The section follows the page
Switch the language: the section mirrors, the badges change, and the date turns Jalali with Persian digits.
// why
A site with an expert behind it gets asked questions. WordPress had two answers for that, and both were wrong.
Option one
Anyone can post, the newest thing sits at the bottom, and there is no way to tell that the person answering is the specialist the visitor came for. It reads like a comment thread, because it is one.
Option two
A second user system, a second set of templates that never match the theme, its own tables, and a chunk of load on a page that needed one section, not a community.
The details were where it really fell apart. A question with a link in it, published unreviewed, is a spam delivery system. A captcha sends visitor data to a third party for what is, in the end, a name and a sentence. The date reads in a calendar half the audience does not use. And when the client wanted one word of the form changed, the answer was a code snippet.
The data model was already right. Everything missing was presentation, moderation and language.
Native comments already give you threading, moderation, notification, spam hooks and an export. What they do not give you is a section that looks like a Q&A, an answer that visibly comes from the expert, and a form a client can rewrite without a developer. Those were the parts worth building.
So one Elementor widget renders a post's comments as a Q&A section. The form submits without reloading and falls back to a plain round trip when JavaScript is off, with the values restored and no white error page. Spam is stopped on the site itself, with nothing sent to an outside service. Every visitor-facing string can be translated and then overridden per widget, dates are Jalali with Persian digits or Gregorian by page language, and the whole appearance, sixteen groups of it, lives in the Elementor Style tab.
// two-layers
The question a visitor really has is whether the answer came from the expert. The section answers that before they read a word.
A question never carries a badge, and the visitor avatar is your choice: nothing at all, the first letter of the name, or Gravatar.
Two levels: the question and its answers. No nested arguments, no pagination surprises, no thread that walks off the edge of the screen.
When an answer is published, the person who asked receives an email in the language they asked in, if they left an address.
// the-form
Name, question, an optional email and a remember me box. No website field, because that field exists for spam. Everything else is about what happens when something goes wrong.
A token is fetched, the question is posted, and the answer comes back in place. The page keeps its scroll position and a slow network never costs the visitor what they typed.
Sixteen validation cases, each with its own sentence under the field it belongs to, a banner counting what needs fixing, and focus moved to the first problem.
The plain form posts, and the page comes back to the section with the banner and the typed values restored. Never the white WordPress error page.
A live count that turns amber near the ceiling and red past it, with the send button disabled rather than the question silently truncated.
A tab left open for hours gets a clear notice instead of a silent failure, and the text stays in the browser so nothing is retyped.
When questions are closed on a page, the form becomes a calm notice with a link to your contact page, and the existing questions and answers stay where they were.
A set number of questions is shown and the rest arrive behind one button, with focus on the first new card so a keyboard user is not sent back to the top.
// anti-spam
A name and a sentence do not justify shipping your visitors to someone else's servers. Everything here runs on your site.
Fourteen WordPress discussion settings that this section depends on are applied on activation, then audited on the settings page and inside the widget panel, with a tick or a warning for each. One button sets them all again if a later change knocks one out of line, and the previous values are kept so you can see what was changed and why.
// languages
Every word a visitor sees comes from one of three places, and the more specific one wins. A translator, a site owner and a page designer can all change text without overwriting each other.
The plugin's own language files
English in the code, Persian bundled. Follows the language of the page automatically.
WPML string translation
Every visitor-facing string registered under one context. A third language is translated once and applies everywhere.
The widget panel
Text typed into one widget wins over both, for that widget only.
Dates and links follow the page too: Jalali with Persian digits or Gregorian by page language, and the contact link resolved per language.
One card per text, each language side by side, with a live filter. Type email and only the email texts stay on screen.
Logical properties throughout, so the section mirrors correctly rather than being patched with direction-specific overrides.
The settings page and the widget panel are bilingual themselves and follow each administrator's own dashboard language.
// the-panel
The rule this plugin was built on: if a client can describe the change, they should be able to make it without a developer and without CSS.
What the section shows, and every word it says.
Sixteen groups, each with typography, colour, spacing, border, radius and shadow. No CSS.
Eight tabs, for the things that belong to the site rather than to one widget. Docs explains every setting with developer samples; Changelog lists every version with its date.
// telegram
Six moments in the life of a question, each able to send its own message to a group, a channel or a private chat, written by you with macros.
The events
Written by you with formatting, with two buttons underneath: view on the site, open in the dashboard. A test send before you save anything.
Questions and answers can go to different chats. Every event is off until someone switches it on deliberately.
So a slow Telegram never slows a visitor down.
Through the bot the site already has in Toolkit, with filters on the message, the receivers and the buttons for anything unusual.
The question
The asker
The answer, page and site
The macro list is generated inside the plugin, with a searchable picker beside the message editor, and your own macros can be added through a filter.
// developers
An event for every moment, a filter at every seam, and a module tree that can be lifted into another plugin.
// Do something when the expert answers add_action( 'pgqa/event/answer_pro', function ( array $ctx ) { $link = $ctx[ 'macros' ][ '{answer_link}' ]; // notify a CRM, log it, post it somewhere else } ); // Or listen to everything add_action( 'pgqa/event', function ( string $event, array $ctx ) { // $event: question_submitted, answer_pro, answer_edited ... }, 10, 2 ); // Add your own macro to every message add_filter( 'pgqa/macros', function ( array $macros, array $ctx ) { $macros[ '{clinic_branch}' ] = get_post_meta( $ctx[ 'post' ]->ID, 'branch', true ); return $macros; }, 10, 2 );
One action per event and one catch-all, both carrying the comment, the post and the resolved macros. Decide whether an event fires at all, per event and per context.
The event bus means email, SMS or any other service is a listener, not a fork.
The questions and answers are marked up so search engines read the section as a Q&A, and a shortcode renders the same section outside Elementor.
The same code ships standalone or inside our toolkit, with the settings store injected.
Every hook is documented with a copy and paste sample inside the plugin, under Settings, Docs.
// tested
Before a release goes to a site, the section is driven by a headless browser on a real page and the result is measured. A sample of what gets checked every time.
| Check | What is measured | Result |
|---|---|---|
| The section renders | Column width, title and body sizes, line height, avatar size and answer indent, on desktop and mobile | Pass |
| Language follows the page | Title, badges and the date format switch with the page language, in both directions | Pass |
| Empty and short fields | The right message under the right field, a banner counting them, focus on the first one | Pass |
| A question over the limit | Counter turns red, the button disables, nothing is silently truncated | Pass |
| A real submission | The question lands in the moderation queue and the visitor is told they will hear back | Pass |
| The same question twice | A notice that it has already been received, rather than a duplicate card | Pass |
| Four submissions in a row | The rate limit message and a countdown on the button | Pass |
| The network drops mid send | An error banner, the typed question kept, the button usable again | Pass |
| A page left open for hours | A clear notice about the stale page, with the text preserved in the browser | Pass |
| Honeypot or time trap tripped | Discarded silently, and the bot is shown the success message | Pass |
| JavaScript switched off | Errors and success both return to the section with a banner and restored values, no white page | Pass |
| Show more | The hidden cards appear and focus moves to the first new one | Pass |
| Answering from the dashboard | An answer published as the expert carries the expert badge on the front end | Pass |
| The rest of the site | Home, blog and contact still return normally after install | Pass |
// questions
Q&A Comments is installed and configured as part of the sites Pigment Dev builds, and is available on its own: the section you need, the languages it has to speak, and who should be answering.
No. Questions and answers are ordinary WordPress comments, so moderation, notifications, export and every tool you already use keep working. Uninstalling the plugin leaves the content exactly where it was.
The widget needs Elementor, and it is how you get the full content and style panels. There is also a shortcode for the same section, for pages and themes built another way.
There is no captcha and no external service. A honeypot, a time trap, a per-address rate limit, duplicate detection and forced moderation do the work, and nothing about your visitors is sent anywhere.
As many as the site has. English and Persian ship with the plugin, and every visitor-facing string is registered for translation under one context, so a third or fourth language is translated once and applies everywhere. A single word can still be overridden inside one widget.
It is built to win on specificity rather than force, with no !important anywhere, and it uses logical properties so a right-to-left site mirrors correctly. Defaults are read from your theme's global colours, so it matches before you change a thing.
It uses the bot your site already has configured in Toolkit, so there is nothing to create twice. Notifications stay off until you switch on the events you care about.
// products/
Plugins, apps and internal systems. Each one is shipped, documented, and still looked after.