29 posts tagged with "Shortcodes"

The question: a "Photo Scatter" effect — photos scattered flat on a tabletop, gliding in from the edges, dwelling, then reshuffling to the next set — is unmistakably a gallery. The core [gallery] element already has 20+ layout designs. So does a new gallery design belong there, or in the Animation Engine's [gallery_3d]?

The question: [posts post_type="fw-portfolio"] already renders project listings with layouts, card styles and pagination. Should [portfolio] stay a lightweight filter-grid and steer users to [posts], or grow into the full portfolio element?

The question: The Posts "Card Style" list felt redundant — several styles are just an image mask or a fill on top of a base layout, and we already have Box Presets. How should image treatments be organized, and should they become a reusable Theme Settings preset?

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: 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?