What's new

This page tracks the latest user-facing Zeeker releases. The detailed guides linked below are the source of truth for configuration and behavior.

October 24, 2026

Community tools removed

Community tools have been removed from Social, embeds, and the Admin Center. This includes discussion and topic subscriptions, private feedback and knowledge panels, custom member fields, recognition, and event management. The Saved responses composer control has also been removed.

October 22, 2026

Embed installation and migration tools

The Embed dashboard adds reusable configuration templates and brand kits, configuration/live-page diagnostics, portable discussion imports, and statistics with custom date ranges, previous-period comparisons, and CSV export. Host apps can reconfigure their current URL or object without reloading the page.

See Templates, diagnostics, and imports and the JavaScript API.

August 13, 2026

Faster cached feeds, threads, notifications, and Chat

Social now keeps bounded, account-scoped first pages for the surfaces people revisit most often and revalidates them without blocking the initial paint. Feed and reply ordering is owned by the server, and subsequent pages use opaque continuations rather than downloading and re-sorting growing histories in the browser. Posting, replying, reacting, editing, and deleting advance only the affected cache scopes.

Post pages no longer load the Home feed in the background. Their root, connected posts, parent context, and first reply page are fetched as bounded thread data, while references and related content wait until their activity tabs are opened. Notifications use a lightweight unread-count request plus paged history. Chat inboxes, messages, and changed-conversation checks are paged as well, with bounded polling that backs off when the app is idle or hidden.

August 2, 2026

Elements are now Social compositions

Group Chat, MOD Chat, Support Forum, Comments, Reviews, Product Q&A, Community Feed, and Polls are now authoring presets over existing Zeeker Social capabilities—not independent mini-products or runtime feature kinds. A preset initializes ordinary choices for existing feeds, post types, threads, composers, chats, sorting, and presentation. If Zeeker Social does not have an underlying capability, Embed omits it until the capability is added to Social itself.

Community settings are the capability ceiling: visibility, membership, allowed post types, badges, default sort, related-post/external-content policy, chat, moderation, SSO, and whitelabel. Each embed can narrow content and outside access, show/hide the standard community card, native community search, review summaries, or normal Social regions, narrow related posts to community-only/off, position the composer, choose same-embed/new-page post opening, select page/internal scrolling and infinite/Load more loading, and configure the outer container/top header. Element-specific radius is limited to that outer boundary; internal Social components stay canonical.

Group Chat and MOD Chat now start with the same responsive activation contract: a floating host action on desktop and a chat/support action in the mobile host's bottom tray open the existing Chat destination. Every Element can instead use a Zeeker launcher, a host-owned trigger, fixed inline placement, or full-screen placement without changing its underlying Social or Chat capability. Support Forum includes native community-scoped search and a bounded, implementation-owned information box supplied programmatically by the preset—not an Admin Center HTML field or per-embed toggle. The box sits above the filter header, matches the adjacent border treatment, and remains opaque on a transparent canvas. Reviews can independently show Social's rating average/distribution and a grounded AI summary, with only genuine model output labelled as AI. Direct replies to Product Q&A questions use Social's answer type and normal Answer badge.

Each preset still has an illustrated overview at embed.zeeker.com/<element> and a separate interactive example at /<element>/demo. Demo pages place the canonical Social composition inside website and mobile-app host contexts; on a narrow viewport they mount only the mobile runtime and point visitors to a desktop-width screen for the desktop implementation. The overview does not boot a runtime. See Embed Elements.

Per-embed connection, access, login, and theme

Every embed records its Zeeker connection, read access, participation policy, sign-in method, and sign-in timing independently. SSO provider setup remains community-level; an embed can narrow that capability to Zeeker login, community SSO, or either, and can initiate identity on a gated action, automatically on load, or through a host-managed flow.

Explicit Light and Dark selections remain fixed when the host or preview theme changes. Only Auto follows the host color scheme.

Embed only is now a supported deployment capability. When it is available, every post and reply belongs to one exact embed config and is excluded from ordinary Social feeds, search, profiles, notifications, SEO, and shared Social analytics. The runtime uses a short-lived config scope, and every request rechecks the live config revision. Editing, pausing, or unpublishing the config therefore revokes previously issued scope instead of waiting for it to expire. Scoped Chat also rechecks current membership, staff role, community/config chat switches, publication status, and revision on each request or poll.

Isolation still fails closed per deployment. The Embed service reports Embed only only after the shared database boundary and scope-signing secret pass startup checks; missing migrations, constraints, authorization, revocation, or signing configuration make publishing and booting unavailable rather than falling back to Connected. Named guest participation is offered only when the selected Social or Chat surface separately reports its complete exact-config guest boundary. Guest-enabled surfaces keep login/signup and add Continue as guest, which requires a display name and remains scoped to the published Embed.

Real, signed Social previews

The configurator preview loads the real Social surface selected by the generic settings rather than a fabricated Element-specific mockup. Draft overrides require a short-lived, config-bound signed token and are marked read-only across Embed, Social, and Chat. Preview parameters cannot authorize themselves, and verified preview responses are private/no-store.

July 23, 2026

A more immersive Explore reader

Explore stories now use an edge-to-edge lead image, a taller reading canvas, and clearer topic and location labels after the description. Image-less stories are centered in the canvas so short posts remain easy to scan. A compact Read more control on the image opens the publisher, while the rest of the card opens the corresponding Social post.

On mobile, swipe up after reaching the end of a story to open its replies. The app provides haptic feedback when the tray opens. When a story references another post, that related summary appears once in the conversation area immediately above the Replies heading instead of inside the story card.

The topic, location, and date row now follows all story text without an extra panel around it, and the mobile action rail sits closer to the bottom edge. On desktop, larger actions live in a separate rounded rail below the story. The wider conversation pane can be collapsed or expanded, and the Explore menu includes a dark-mode switch.

July 14, 2026

Full-app website embeds

Host-triggered embeds can now open a complete community app instead of only a page discussion or panel. In the configurator, choose Trigger, set Button opens to Community app, then turn on Full screen.

Full-app controls let you:

• Hide the desktop header while keeping the app menu available.
• Show or hide mobile navigation for Home, Search, Create, Notifications, and Profile.
• Enable or disable pull to refresh.
• Preload the app in the background for a faster first open.

The host app owns opening and closing a full-app surface, so Zeeker does not add a second close button. See Container modes and Configurator.

Mobile and embedded navigation

Social and Explore now preserve more navigation context on mobile. Horizontal swipes switch feed tabs without taking over vertical page scrolling; back navigation restores the previous screen and scroll position; returning to Search restores the query and its results. Embedded full-app communities keep their own animated navigation and can expose mobile bottom navigation and pull to refresh.

Safer Admin and Embed access requests

Opening Deploy in Admin now takes you to the Embed Center without submitting anything automatically. When Embed access is restricted, the Embed Center explains the restriction and provides the explicit request form. Pending requests are shown in place so they cannot be submitted twice.

Privileged access approvals also require an active sign-in. If the admin session has expired, Zeeker asks the operator to sign in again before the action can continue. See Sign in & access.

July 13, 2026

Explore preferences follow your account

Feed preferences now stay aligned between zeeker.com and explore.zeeker.com, and signed-in preferences are restored from the backend on another session or device. Signup interests seed the same topic preferences instead of creating a separate personalization profile.

You can tune location, topics, Following only, and whether external news/source posts appear. Community-specific sorting and email choices remain scoped to that community. See Explore preferences.

Platform-aware embed setup

The Embed Center now separates Mobile App and Website setup from the start. App embeds offer full app, community screen, conversation, and community chat scenarios with native iPhone and Android deployment instructions. Website embeds offer floating, fixed/inline, and host-triggered experiences with web-specific install patterns.

July 12, 2026

Community AI controls

Community owners and admins can use Settings → Zeeker AI to control automated posts, curated third-party posts, AI replies, externally grounded replies, and AI reactions. Turning off the master control pauses the capabilities without discarding the individual selections. See Community settings.

Community visibility consistency

Public, unlisted, and private community visibility now applies immediately across feeds and search. Unlisted communities stay out of global discovery even for members; they remain available through their direct community surface. Private-community posts are limited to members.