Card-style UI lives or dies on whether the whole card is clickable. The DesignSetGo Clickable Group extension makes any container block a link โ without sacrificing accessibility or nested links.
An FAQ accordion is a lightweight UX pattern that also happens to be one of the highest-leverage SEO wins available โ if you wire it up to FAQPage schema. Here’s the pattern.

Version 2.1 is the biggest DesignSetGo release yet: a full Dynamic Query block family, an Elementor-style Dynamic Tags picker, native WordPress 6.9 Block Bindings, field sources for Meta Box / Pods / JetEngine, conditional block visibility, per-URL Markdown, and a rebuilt editor experience across the entire block library.
find-blocks and batch-update are the two DesignSetGo abilities that make sitewide content operations a single LLM prompt instead of a weekend of clicking. Here’s how to use them safely.
Scroll-triggered animations don’t need AOS, GSAP, or a page-builder dependency. DesignSetGo’s Animation extension adds tasteful, performant motion to any block โ core or DesignSetGo โ with a few checkboxes.
Section, Row, and Grid all arrange blocks โ but they solve different problems. Here’s a plain-English guide to when each one is the right tool, with concrete examples you can steal.
Once your LLM is wired up to the DesignSetGo Abilities API, the next question is: what do I actually say to it? Here are ten prompts โ from hero sections to site-wide rebrands โ that produce real, polished pages.

DesignSetGo ships with a full set of Abilities API endpoints โ a standardized way to let Claude, ChatGPT, or any LLM insert, configure, and modify blocks in your WordPress pages. Here’s how to wire it up.
Version 2.0.45 fixes a critical error some users experienced when trying to delete DesignSetGo through the WordPress plugin dashboard. Update to resolve the issue.

If you’ve been paying attention to how AI tools interact with the web, you’ve probably noticed a growing problem: language models are terrible at reading websites. They choke on navigation menus, sidebars, cookie banners, and JavaScript-rendered content. The information they need is buried under layers of HTML that was never designed for them. Enter llms.txt, a