Plus for FluentCommunity v2 User Manual

Requirements

Installation & Upgrading to v2

1. Upload the Plus v2 ZIP through Plugins → Add New Plugin → Upload Plugin, install it through your normal WordPress plugin workflow, or update an existing Plus installation.
2. Activate Plus for FluentCommunity if this is a fresh installation.
3. If upgrading from v1.x, allow v2 to migrate existing compatible settings. Do not remove your old configuration before confirming the migration.
4. On a first v2 install or the first upgrade into v2, Plus can route the administrator to the new Plus 4 FCom → Control Center and display the v2 welcome screen.
5. Continue setup from the Control Center and enable only the add-ons and integrations the site needs.

The v2 Welcome Experience NEW IN V2

The v2 welcome screen is a one-time orientation layer for the new interface. It introduces the Control Center, points users to Theme Studio and the v2 manual, and explains the new top-level Plus location. Routine updates within v2 do not keep reopening the welcome screen.

Dashboard & Metrics

The Control Center uses grouped cards to keep the v2 interface focused. The two primary groups are Add-Ons and Enhancements, with live state and useful metrics shown where applicable.

Customize Control Center

Use Customize CC to control which supported cards appear on your Control Center. This keeps the home screen relevant to the way each site actually uses Plus.

Core Feature Catalog

Messaging Controls

Messaging Controls extend Fluent Messaging with staff-aware restrictions and group controls.

Theme Studio NEW IN V2

Theme Studio is a new visual-design workspace and Add-On introduced in Plus v2. Enable it from the Add-Ons screen when you want to use it, or disable it to stop its admin workspace and frontend styling runtime. Saved Theme Studio settings are retained when the add-on is disabled.

Module Manager

The compact Modules manager shows how many Theme Studio modules are enabled and expands only when you need to change them. This keeps Theme Studio usable as more design modules are added in future releases.

• Menu: enables or disables Menu Styling.
• Topics: enables or disables Topic Styling.
• Badges: enables or disables Badge Styling.
• Saved settings are preserved: disabling a module stops its styling runtime without deleting the module's existing configuration.

Preview & Device Viewports

Theme Studio uses a virtual viewport for the FluentCommunity preview. This is important because FluentCommunity changes its own layout according to viewport width. If the preview iframe were simply squeezed into the editor column, FluentCommunity would interpret that narrow width as a tablet or mobile device even while you were trying to design the desktop layout.

The stage visually scales the selected viewport to fit the available editor area. The viewport itself remains at the selected dimensions, so responsive behavior comes from FluentCommunity rather than from Theme Studio artificially forcing a layout.

Menu Styling

Menu Styling controls the FluentCommunity sidebar/navigation behavior. In v2 these settings are part of Theme Studio rather than being treated as a disconnected design screen.

Topic Styling

Topic Styling controls the topic filters displayed in FluentCommunity spaces. Select the Topic area in Theme Studio, then choose the topic you want to style from the topic selector. The controls apply to the selected topic and its interaction states.

Badge Styling

Badge Styling lets you override FluentCommunity badge presentation from Theme Studio. Select the Badge area, choose a badge from the badge selector, and then configure that badge's visual properties.

Live Changes & Saving

Supported Theme Studio changes are designed to update the preview as you edit. This makes it possible to adjust colors, spacing, and presentation while looking at the affected FluentCommunity element instead of repeatedly saving and reopening the designer.

• Live preview: supported controls update the preview immediately.
• Selection-aware controls: choosing a menu, topic, badge, or other supported element determines which settings are shown.
• Saved output: save the Theme Studio configuration to make the styling persistent on the live community.
• Responsive validation: switch Desktop, Tablet, and Mobile after styling to verify the same design across FluentCommunity breakpoints.

Admin Notes

Private staff notes remain available in v2, including member-specific notes, pins, urgent status, tags, image attachments, watch notifications, viewed-by tracking, audit history, filtering, CSV export, and bulk management.

Profile Fields

Add custom profile data fields with configurable layouts, field types, and visibility rules. Supported use cases include text, long text, email, URL, date, select, checkbox, and radio inputs.

Webhooks

Send event payloads to automation services such as Flowmattic, Zapier, Make, or custom endpoints. Badge assignment/removal workflows remain supported.

Integrations

Integration cards use a consistent layout for supported third-party tools and bridges. Integrations are intended to be optional: enable only the connections your site actually uses.

Feeds in Spaces NEW IN V2

Feeds in Spaces is a new v2 content-ingestion and publishing workspace. It imports external content into FluentCommunity using RSS/Atom sources or a public FluentCommunity Space with optional topic filtering.

• New feeds start safely: newly added feeds begin disabled and Manual-only until you configure and enable them.
• Delete feeds: saved feed configurations can be deleted. Deleting a feed removes its queued items without deleting posts that were already published.
• Duplicate protection: feed items use a stable fingerprint/idempotency check and a short publish lock to prevent a queued item and an automated/manual publish from creating the same FluentCommunity post twice.
• Queue vs. automation: a feed configured to auto-post can honor that setting during a per-feed fetch, while Manual/queue-only feeds remain in the Review Queue.

Public FluentCommunity Spaces

Choose Sitemap / XML when the source is a publicly readable FluentCommunity Space. Although the setting retains its general Sitemap / XML label, Plus first requests FluentCommunity’s public feed endpoint with the saved Space and topic filters. This produces the same filtered collection visitors see in the source community. If that endpoint is unavailable or returns an unsupported response, Plus falls back to sitemap URL discovery and public-page metadata.

Test First, Then Automate

1. Select the intended destination Space and posting identity.
2. Enable This source is active.
3. Set Automatic behavior to Manual only — I will fetch it myself.
4. For the first test, set Items to check per fetch to 5, choose the desired post layout and excerpt length, and enable a clickable source link when attribution is wanted.
5. Save the source, then choose Fetch this source now.
6. Open the Review Queue. Confirm the titles, excerpts, original links, posting identity, and destination before publishing one test item.
7. Fetch again and verify the published item is not added as a duplicate.

WP Posts in Spaces NEW IN V2

WP Posts in Spaces is a new v2 rule-based publishing system for sending eligible WordPress content into FluentCommunity. Each Publishing Rule owns its source filters, destination Space, posting identity, automation behavior, and message format, so the same source can be presented differently in different Spaces.

Publishing Rules

Create separate rules for separate source-to-Space workflows. Supported WordPress sources include Posts, Pages, public custom post types, Slayers News, and Slayers Guides. When Slayers Inc. Builds is active, native public Slayers Builds can also be selected.

Post Content (Per Rule)

The Post content panel customizes the FluentCommunity message for that individual rule. It applies to every supported WordPress publishing source—not only Slayers content—and can therefore vary by source and destination Space.

Automatic Publishing and Updates

With the add-on and rule enabled, Plus listens for eligible source publication events and applies that rule automatically. A new matching WordPress record can create one community post; a later material update can update the mapped post when update handling is enabled.

• Slayers Builds v1.1.9+: Plus receives the stable sib_build_published event after individual community/verified publication and once per build during bulk publication.
• Visibility: native Slayers Builds automation accepts newly published public community or verified builds and ignores private, unlisted, draft, and pending-review records under the integration rules.
• Duplicate protection: clicking Publish again for an already-published build does not represent a new publication transition; Plus also checks the existing destination-specific mapping before creating.
• Required configuration: the WP Posts in Spaces add-on, the individual rule, and automatic publishing must be enabled, and the destination Space must still exist.

Preview Rule

Use Preview rule on a saved rule to inspect its final formatted FluentCommunity message without publishing it. The preview uses that rule’s source, destination, and Post content settings and reflects the Slayers Builds no-embedded-image exception.

1. Save the rule.
2. Select Preview rule from its actions.
3. Review the resolved source record, destination, expected Create/Update/Skip action, and formatted message.
4. Return to Publishing Rules to make changes and preview again.

Historical Scan and Backfill

Historical backfill finds older eligible records for one saved rule and compares each record with its destination-specific FluentCommunity mapping before anything is pushed.

1. Save the rule and run its historical scan.
2. Review the proposed actions and select eligible records.
3. Push the selection and review Created, Updated, Skipped, and Failed totals.
4. Run the scan again when needed; unchanged mapped records resolve to Skip instead of becoming new creates.

Discord in Spaces NEW IN V2

Discord in Spaces imports Discord content into FluentCommunity. It is the inbound side of the Discord integration: Discord is the source, and FluentCommunity spaces/posts are the destination. v2 separates this from outbound Discord publishing so it is always clear which direction content is moving.

Connection

The Connection area identifies the Discord server Plus is allowed to read and provides the credentials needed for inbound imports.

Mirror Structure

Mirror Structure helps recreate a Discord hierarchy inside FluentCommunity. The current v2 model associates a mirror with a specific Discord server and uses the source structure to determine the FluentCommunity destination.

Import Rules

Rules let you import selected Discord channels without mirroring an entire server. Multiple rules can be created so different Discord channels can feed different FluentCommunity spaces.

How Imported Discord Content Is Built

Discord messages are converted into FluentCommunity posts while preserving useful context and avoiding formatting that does not translate cleanly between platforms.

Automatic Sync & Activity

After the connection and rules are working manually, automatic synchronization can keep Discord and FluentCommunity reasonably current without requiring an admin to press Import repeatedly.

• Near-real-time scheduling: run lightweight scheduled checks at an interval appropriate for the site instead of performing expensive work on every page request.
• Rule isolation: activity identifies a problem with an individual channel/rule without treating it as a successful import.
• Activity log: record imports, skips, errors, and useful source/destination context.
• Clear Activity: remove old Discord activity history when it is no longer useful without deleting the underlying Discord rules.

Integration Gate

The main Discord integration supplies the shared Discord connection and inbound foundation. When Discord is enabled, Discord in Spaces is available as part of that inbound system rather than requiring a second duplicate integration toggle.

Outbound Workflows

Configure each outbound workflow independently; enabling one direction does not automatically activate unrelated Discord publishing.

Archive Rules & Scans

Archive rules determine what is eligible to leave the live FluentCommunity dataset. Rules can consider content age, volume, and supported exclusions. Use Run Scan to evaluate current content against those rules.

Archive Library & Community Archive

Open Archive provides the administrative view of archived content, while the frontend Community Archive provides a lightweight reading experience for content the current visitor is allowed to see. Posts and comments remain separate record types.

• Filter/search archived posts and comments independently.
• Archive detail pages include a clear Back to Community Archive action.
• Archive visibility follows FluentCommunity access: visitors see only public content, while logged-in users see additional archived content only when their community access/roles permit it.
• Private/restricted Space names and archive URLs are kept out of visitor-facing filters and public sitemap output.
• Images referenced by archived posts/comments are rendered from lightweight media references and lazy-loaded instead of copying image binaries into every archive record.
• Other active community sessions receive lightweight archive invalidation so newly archived posts/comments disappear without requiring a full page reload.

Restore, Unarchive & Re-archive

Restoring returns archived content to FluentCommunity. The archive system must distinguish an intentional restore from ordinary new content so automatic rules do not immediately archive it again.

For user-facing archive access, the long-term design also allows an archive list and an unarchive/request workflow without exposing unrestricted administrative archive controls to ordinary members.

Export & Long-Term Storage

The archive format is intentionally lightweight. Normal archive viewing uses a precomputed Lite snapshot instead of loading FluentCommunity's full application state or decoding the canonical restore payload on every request.

• Display snapshots keep only useful semantic content and minimal media references.
• Images are referenced rather than duplicated, with lazy loading used on archived detail pages.
• The full canonical FluentCommunity data is retained separately for accurate restore/export operations but is not needed for ordinary archive reading.
• Archive packages can be exported as ZIP files with the metadata needed to understand and later restore the source content.

Tracking Settings

Analytics is opt-in by event type. Enable only the tracking you need; data begins accumulating after the relevant toggle is enabled.

Extended Tracking

Extended Tracking enriches activity with additional request/device context such as IP address, country/city, device type, browser, operating system, external referrer, and UTM campaign values.

Dashboard

The dashboard supports period filtering and drill-down cards. Typical cards include All Activity, Total Members, Posts, Spaces, Downloads, Top Country, Device, Browser, OS, Referrer, and UTM Source.

• Change the reporting period (for example 7, 30, 90 days, or all time).
• Open summary cards for detailed breakdowns.
• Filter activity by type and space.
• Sort and paginate detailed activity.

Data Management & Export

Maintenance & Diagnostics

System Tools is the administrative utility area for operations that are useful occasionally but do not belong in everyday feature configuration. Depending on the enabled v2 modules, this can include diagnostic/status information, cleanup actions, repair operations, and feature-specific history management.

History & Log Cleanup

Features such as Discord synchronization and other operational tools can accumulate history. Use the relevant clear-history action when those logs are no longer useful. Analytics has its own data-management controls under Community Tools → Analytics. Clearing a log should not disable the feature or remove its configuration unless the action explicitly says it will.

When to Use System Tools

• After a failed import/sync when you need diagnostic context.
• When an activity/history table has grown unnecessarily large.
• When a repair or scan action is specifically recommended by a Plus update or support instruction.
• Before/after major migrations when you need to verify stored state.

Activating a License

1. Open the Plus license area from the v2 admin interface.
2. Enter the license key supplied with your purchase.
3. Activate the license.
4. Return to Add-Ons and enable only the premium modules you want to use.

Moving or Deactivating a License

Translation Files

Use the plugin translation template as the source for your language files, then sync translations again after updates to pick up newly added v2 strings.

Updating Translations

Common Issues

Visual Troubleshooting