LNK FAQ Pro: a PrestaShop FAQ that answers where the customer asks

A standalone FAQ page gets few visits: customers ask their question on the product page or in the checkout, rarely after looking for the link to the FAQ. LNK FAQ Pro groups questions into categories, then shows each category in the positions you choose:

A category can have as many positions as needed. Delivery questions under product pages, returns on the home page, payment terms on the CMS page about them: the same answer serves everywhere and is maintained in one place.

All these positions are native PrestaShop hooks, provided by the official themes. If your theme has no hook point where you want it, we add it for you free of charge.

The /faq page gathers the categories placed on it, with a heading, a title tag and a meta description, all translatable. A search box filters the questions as the visitor types, with no server request, highlights the matched word and says “2 results out of 9 questions”. A link to /faq#a-question opens the targeted answer directly. An optional footer block links to the FAQ and to its first questions (zero to ten).

Each answer opens in a native <details> element: the accordion works with the keyboard and without JavaScript, one answer open at a time per group.

A shop running our LNK FAQ module (lnk_faq) has nothing to type again. When FAQ Pro is installed or updated, the content is taken over: blocks, questions, answers, every language (matched by language id), same pages, same order, same look, same texts around the blocks.

Every imported text is then read back and compared with the source, language by language and shop by shop:

• when everything matches, LNK FAQ is disabled (its data stays in the database, nothing is uninstalled) and FAQ Pro takes its exact place in each hook;
• at the slightest difference, everything imported is removed, LNK FAQ keeps running, and the back office shows the reason with a "Try the import again" button.

Imported answers go through the same filter as the answer field of the form (PrestaShop's HTML purifier, then the isCleanHtml check). Any answer this filter changes visibly is listed in the report, for review.

Measured on a copy of a real three-language shop (French, English, Arabic, PrestaShop 9.1.4, PHP 8.4): 30 blocks and 222 questions imported, 84 pages compared before and after, no difference.

By default, the module takes the theme's colors and fonts. The appearance settings go further, with no CSS to write:

• Colors: accent, headings, answer text, rules.
• Sizes: headings, questions, answer text, in pixels.
• Answer text strength: applied in the color itself, never through transparency; below 100 %, the settings screen reminds you to check the contrast.
• Block heading: the FAQ page title, or the name of the category shown.
• Texts around the blocks, in each language: eyebrow, introduction, contact link text. Left empty, they use the module's translation.

A field left empty keeps the theme's look. Settings are applied as CSS variables on the block itself: no file is generated on disk.

For integrators, the public --lnk-faq-* variables (accent, border, muted, gap, title-color, muted-opacity, title-size, question-size, text-size) can be set from the theme in one line. They fall back to the LNK themes' base tokens (--lnk-accent, --lnk-border, --lnk-muted), and the former --lnkfaq-* names are still read.

On PrestaShop 9, the module's screens are built with the Symfony components of the back office, with no AdminController and no HelperForm:

• native grids for categories and questions: filters, sorting, drag and drop ordering, one-click status, bulk delete; questions are shown one category at a time;
• Symfony forms with translatable fields and a rich text editor for answers;
• a settings screen covering the FAQ page, the blocks and the appearance.

Every page carrying a FAQ publishes a JSON-LD FAQPage block (schema.org) with its questions and answers, and only one per page, even when several blocks are shown there. A question without an answer is left out, because an empty entry invalidates the block. A switch turns this data off if another module already publishes a FAQPage on the same pages.

Questions and answers are text in the page's HTML, readable by a search engine or a conversational assistant that does not run scripts. The module makes your answers readable; their content does the rest. Details are in SEO.md.

Every question, answer, category name and FAQ page text is entered in every language of the shop. Texts are stored in PrestaShop's native _lang tables, one row per language. The module ships in French, English and Arabic, and the stylesheet handles right-to-left writing.

Questions accept up to 512 characters.

The 2.9.0 package installs on PrestaShop 9 only. Shops on 1.7 and 8 get the 2.1.0 package, with the same features and no Symfony file.

Updating from a 1.x version is automatic: categories and questions move to the native _shop multistore association tables, each one keeps its shop and its order, and your per-language texts are kept.

This module installs no override. The override/ folder does not exist.

For an agency, this means no conflict with another module overriding the same class, no orphan file after a PrestaShop update and nothing to clean up before a migration.

Figures measured on the shipped module, gzip-compressed (level 9). On the front office: a 3,999-byte stylesheet (3.9 KB) and a 2,279-byte script (2.2 KB), no jQuery. The script only loads on the /faq page, where it runs the search and opens a question from its link; every other page loads 0 bytes of it. The stylesheet only loads on pages that can carry a FAQ (home, product pages, category pages, CMS pages, /faq), or shop-wide when the footer block is on. No remote font, no CDN, no external call.