The question: I want a page-builder column to be able to contain other columns. Do we add a dedicated "Inner Row" element you drag into a column (like Elementor's inner section or WPBakery's inner row), or do we just let a column accept columns directly and build the row ourselves? And how deep should nesting go?
The question: Can we make the Off-Canvas header mode more flexible? Right now it only displays the menu. Can it display Snippets — I want the ability to add shortcodes or custom info in that panel. Perhaps a select where the user chooses default menu or snippet, and for snippet a dropdown of snippets?
The question: I want the Design tab to show only the options that matter for the current choice — so
layout_mode, card_style, pagination_type should become image-pickers that reveal their own
sub-options. But those are existing selects with real saved data, and turning a select (a string) into a
multi-picker (an array) is a value-shape change. How do I do that without breaking every already-saved
Posts/Testimonials block?
The question: The Posts grid's Column Gap and Row Gap were plain px inputs. The rest of the builder (Section, Row, Column) takes gaps from the theme's Gap Scale presets. Should Posts do the same?
The question: Posts now has 20-plus card designs. The markup only ever outputs the chosen design, but does the CSS? Should every page with a Posts block load all designs' styles, or only the one in use — and if only one, how do we wire that without a list to maintain as designs keep growing?
The question: The card read-more link can render as a button. Do we add Button Content and Button Styling tabs to Posts that mirror the Button shortcode's options, so the read-more is as configurable as a real button?
The question: Now that the basic color-picker shows the Color Presets as swatches, should we
just use it for every color in Theme Settings and drop the preset picker? Those colors go into the
dynamic stylesheet, not classes, anyway — so what's the preset picker even for?
The question: I want a shortcode to ship lots of visual designs — and to keep adding more — without the view file turning into an ever-growing pile of conditionals. How should "which design renders" be structured so a new design is cheap and safe to add?
The question: Would it be better to make the testimonial Quote field a wp_editor (a full visual
editor) so authors can format their quotes?
The question: The testimonial rating stars showed up as tofu (□□□□□) on a live site. Do we enqueue
Font Awesome so the fa-star glyphs resolve, or render the stars some other way that doesn't depend on a
webfont being present?