If you've ever spent a sprint building internal docs tooling, a changelog page, or a blog feed from scratch, you know the drill: wire up a backend, design a layout, add search, handle routing, and repeat for every content type. What if you could skip all of that and have a polished, fully interactive knowledge base, blog, and changelog live on your site in under 30 minutes — with a single script tag?
That's exactly what we've been building. Here's what just shipped.
A Blog Feed That Actually Looks Like a Product
The blog embed widget got a complete overhaul. Gone is the old inline full-content feed. In its place is a card-based layout with a hero post at the top and a responsive 3-column grid of post cards below — the kind of layout you'd expect from a well-resourced content team, not a weekend side project.
Each hero card surfaces the title, excerpt, date, reading time, and a CTA. Category badges now appear on every card, and the hero post gets a "Featured" label automatically. The layout is fully responsive: it collapses to two columns at 900px and a single column at 600px, so it looks right whether you're embedding it in a wide dashboard or a narrow sidebar.
The detail view is just as considered — a three-column layout with a sticky "On this page" table of contents on the left, the article body in the center, and social share buttons (X/Twitter, LinkedIn, copy-link) on the right. Headings get slugified anchor IDs with smooth scroll and active highlighting as you read. JSON-LD structured data is baked in for SEO. And a "Back to Blog" button is wired to the onNavigate callback so host-page routing works exactly the way you'd expect in a Next.js or React app.
A Knowledge Base with Search, Categories, and Sub-Page Routing
The knowledge base widget now punches well above its weight. Articles are automatically grouped into categories — Features, FAQ, Getting Started, and more — and those categories are editable inline from the dashboard if the generated assignment isn't quite right.
Search is opt-in with a single attribute (data-search="true") and works client-side with debounced input, filtering by title, content, and category, with match highlighting in results. The search field auto-focuses on load, so users can start typing immediately.
Sub-page navigation means the KB embed behaves like a mini SPA inside your site. Article cards link to full detail views with a back button, a search dropdown, and a related articles section — all within the Shadow DOM. For teams using Next.js or any SPA framework, the onNavigate callback hands routing back to your own router, so the browser URL updates naturally and deep links work. You can also pass initialArticle to drop users directly into a specific article on load. External sites get the same fluid navigation without writing a single line of routing code.
One Embed Script, Three Content Types
What ties all of this together is a unified embed pattern. The same script tag, the same configuration options, the same Shadow DOM isolation — whether you're embedding a changelog widget, a blog feed, or a knowledge base. Drop the script on your page, pass your API token and content type, and you're live.
The configuration surface is deliberately simple but covers the cases that actually come up in production: category filtering to show only relevant content, onNavigate for SPA routing, sub-page routing for article deep links, and --ss-dropdown-bg and other CSS custom properties for theming. The embed also captures the URL it's running on automatically via the Referer header, so your dashboard shows exactly where each piece of content is live — no manual tracking needed.
For teams building on React or Next.js, the dual-init strategy handles client-side navigation gracefully, so the widget reinitializes correctly after route changes without flickering or stale state.
Full API Reference and Docs, Live Now
Alongside the embed improvements, a full documentation site just launched — covering authentication, sandbox testing, error handling, and a complete API reference for the changelog, blog, and knowledge base endpoints. It's linked from the marketing footer and mirrors the same dark theme as the rest of the product.
The goal has always been to give developers a way to ship polished user-facing content infrastructure without building it themselves. The embed widgets are getting closer to that promise every week — and there's a lot more coming on the configuration and customization side.