Ghost Kit's blocks (Advanced Columns, Pricing Table, Accordion, Tabs, Testimonial, Changelog, Table of Contents, Number Box, Progress, Carousel, Code Highlight, Form) serialise into wp_posts.post_content as wp:ghostkit/* markup. At render time they resolve to real HTML with the actual data the visitor sees. SleekAI reads the rendered page, so a Pricing Table becomes plan rows with values, an Accordion becomes Q&A pairs, a Changelog becomes a list of versioned changes with dates, and a Number Box becomes a labeled metric.

Ghost Kit also ships with an Effects extension, Display extension, and Custom CSS/JS extension. None of those alter what the bot sees because SleekAI reads post-render HTML rather than block source. The data-source wizard pulls ACF fields, custom taxonomies, and any postmeta referenced from a block, so a docs page mixing Ghost Kit Tabs with custom version meta can answer questions from both.

Display conditions scope different bots by post type, taxonomy term, user role, or URL pattern. Conversations log inside WordPress with the model name, token usage, and page URL. The JS API and PHP embed open the bot from a custom Button or Circle Button click, with the current page already loaded as context, so a click on a Changelog item can open the bot with that version's notes in the prompt.

Ghost Kit is a favorite for developer-tool docs sites and product marketing pages thanks to its Tabs, Table of Contents, Code Highlight, Changelog, and Pricing Table blocks. The downside is that a generic chatbot ignores all that structure. It hallucinates version numbers, invents migration steps, and quotes plan details that don't match the page.

SleekAI reads the rendered Ghost Kit output, so the bot lifts the Changelog entry for v2.4 exactly, points to the correct Tab for the migration steps, and quotes the Pricing Table from the same page the visitor is reading. Because the read happens at request time, shipping a new release or rewriting a docs page shows up in the next answer without retraining. Multibot mode lets a pricing bot, a docs bot, and a changelog bot share the install with separate prompts and scopes.

Conversation logging surfaces which versions or sections cause the most confusion, so you can either tighten the docs or rewrite a tricky migration step. The end result is a chatbot that stays in sync with the developer docs without becoming a release-day chore.