WordPress

The Brandfine WordPress plugin is a thin connector that lets a WordPress site act as a render-and-collect surface for the Brandfine services your workspace has active. Same data model as the npm SDK consumers, accessed through WordPress instead of via @brandfine/client.

What you get

• Booking widget for appointments via the [brandfine_appointments] shortcode + a "Brandfine Appointments" Gutenberg block. Visitors pick a slot, submit, and the request lands in your Brandfine appointments inbox.
• Privacy-friendly analytics auto-injected into every public page when you flip the toggle. No cookies, no consent banners.
• Centralized management. Approve, reschedule, or cancel appointments — and every config knob (business hours, slot duration, notification settings) — lives in your Brandfine workspace, not in WordPress. One dashboard for every site you run.

What it's NOT

• Not a CMS replacement. WordPress keeps being your CMS. Brandfine is the cross-site service layer for forms, appointments, and analytics.
• No content sync. Posts in Brandfine don't flow to WordPress (and vice versa). This is deliberate — see the plan doc for the reasoning.

Architecture in one breath

The WordPress plugin holds your workspace API key server-side, in wp_options. Every browser-side call (fetch availability, submit a booking) goes through a WP REST proxy at /wp-json/brandfine/v1/* which adds the X-Api-Key header and forwards to Brandfine's /external/* API. Your visitors never see the API key.

This sidesteps the "publishable keys" question that's still open for the npm SDK on static sites — the WP plugin uses your existing WordPress server as the trust boundary.

System requirements

Next steps

• Install + connect →
• Embed the appointments widget →
• Enable analytics →
• REST proxy reference → (for plugin developers)
• Theme the widget →