Questions the client can add

A site is handed to a client in the end. What the client can change without calling the developer is the value of the hand-over, and what they cannot break is the developer's peace. 0.9.34 moves both forward.

The FAQ widget

A design from T-Design, or any template, carries its questions as a plain list. Until now the converter kept each question as a block of HTML: correct on the page, hopeless to edit. From today a list of questions becomes one FAQ widget. Every question is an item in the repeater, with its answer as rich text and a switch for "open at first". The client presses the plus for the next question and types. Nothing else to learn.

The widget is written with the browser's own <details> element, so it needs no script, opens and closes without a flicker, and can keep one answer open at a time. It adds FAQPage structured data, so the questions can show under the result in Google. The developer sets the look once: hairlines, cards or plain, the mark on the right, the type of question and answer, the width of the answer.

The converter reads the design's type and colours into those settings, so the page looks as it was drawn and edits like a widget.

Developer or client

T-Builder's own widgets, the FAQ, the Items grid, the Slider and the Marquee band, now show their Style tab to developers only: administrators, and any role you give the t_builder_develop capability. Everyone else sees the content, the items and the links, and never the colours, the spacing or the type. A client who adds a fourth service card cannot move the whole grid by accident.

Where a site needs a different rule, the t_builder_developer filter decides who counts as a developer.

Inside the plugin

A theme built from a conversion carries the FAQ widget with it, like the other shared widgets, so a page keeps its questions without the plugin. Sites update themselves from the account as usual.