` or a canonical link to another site, check these sources in order: * **Your theme files.** Search the layout, the page's template, and its sections. * **Global Embeds.** List them with `GET /api/global_embeds`, or open **Settings > Global Embeds** in the admin, rather than assuming one is responsible. * **The template's stored head markup.** Some older templates carry head markup that is saved with the template rather than in a theme file. `fluid theme pull` doesn't download it, so searching your theme won't find it. ## Don't paste a whole HTML document into a template Your layout already outputs `<!DOCTYPE html>`, `<html>`, `<head>`, and `<body>`, and each template renders inside `{{ content_for_layout }}`. A template that contains a complete page, often the result of copying another site's source, nests a second document inside the first. Its `<title>`, canonical link, and scripts land in the storefront, where they duplicate or override Fluid's and can send search engines to the other site. When you rebuild a page from another site, move its content into sections and its assets into the DAM. Drop its `<!DOCTYPE>`, `<html>`, `<head>`, and `<body>` tags, and anything that was inside `<head>`. ## Checkout isn't part of your theme Your theme renders the storefront and cart only. Payment, shipping, and tax happen in [Fluid Checkout](/concepts/checkout), a separate app at `checkout.fluid.app`. Nothing in your Liquid, CSS, or JavaScript can change the checkout page. ## Render standalone blocks with `content_for` A block in `blocks/<name>/index.liquid` owns its markup. Render a section's standalone blocks with `{% content_for 'blocks' %}`, and a single fixed block with `{% content_for 'block', type: 'heading', id: 'intro' %}`. See [Blocks and components](/themes/blocks-and-components). `{% render block %}` renders only app blocks from [Droplet theme extensions](/themes/droplet-theme-extensions). For a theme block it outputs nothing. Don't loop over `section.blocks` to render blocks that `content_for 'blocks'` already renders: they appear twice. ## Output `block.fluid_attributes` on every block The Page Editor selects a block by the attributes that `{{ block.fluid_attributes }}` emits. Put it on each block's outer element, whether the block is inline in a section or standalone. Sections don't need an equivalent: Fluid wraps each section with its own attributes. ## Know which settings Fluid resolves Fluid turns the value of these setting types into a Liquid object before your template reads it: `product`, `variant`, `collection`, `category`, `enrollment_pack`, `media`, `link_list`, and `product_list`. Every other type reaches Liquid exactly as saved. A `post` or `collection_list` setting, for example, gives you the stored identifier, not a record. See [Resource selectors](/themes/schema-components#resource-selectors). Composite layout settings such as `padding`, `border`, and `corner_radius` also return structured values. Inspect the value before you interpolate it into CSS. ## Give CSS values a fallback An empty setting interpolated into CSS produces invalid CSS, and the browser drops the whole declaration without an error. For example, `var(--color-{{ section.settings.accent }})` becomes `var(--color-)` when the setting is blank. Give the value a default: ```liquid theme={null} color: {{ section.settings.accent_color | default: 'inherit' }}; ``` ## Expect presets to fill empty sections When a section instance has no blocks, Fluid fills in the blocks from the section's first preset each time the page renders. A section you emptied on purpose shows its preset blocks again. To render nothing, add an empty state in the section's Liquid rather than relying on an empty block list. ## Read the language from `localization` Use `localization.language` and `localization.country` for the visitor's language and country. See [Localization](/themes/theme-variables#localization). The `request` object carries only `path`, `host`, `page_type`, `query_parameters`, and `full_url`, so a value such as `request.locale` renders as an empty string: ```liquid theme={null} <html lang="{{ localization.language.iso_code | default: 'en' }}"> ``` Change the visitor's country or language with the storefront SDK, as shown in [Navbar locale selector](/themes/navbar-locale-selector). Don't write Fluid's locale cookies yourself. ## Country-specific navbars, footers, and layouts You can assign navbar, footer, and layout templates to countries. For each visitor, Fluid serves the newest published template of that type assigned to their country. When none matches, it serves a template that isn't assigned to any country, preferring the default. Page templates aren't chosen by country. To give one market a different page, use a separate template and link to it, rather than branching on the country inside one template. ## A clean lint isn't a working page `fluid theme lint` validates schemas and section references, the same checks `fluid theme push` runs. It doesn't render your templates. After a clean lint, open the page in `fluid theme dev` and check the browser console before you push. See [CLI](/themes/cli).

> ## Documentation Index > Fetch the complete documentation index at: https://docs.fluid.app/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > For new direct REST integrations, use the v2026-04 surfaces. The @fluid-app FairShare SDK continues to use its own published public-v2025-06 contract. > Authenticate with the header Authorization: Bearer ; public storefront read endpoints require no auth. > To sign a new merchant up for Fluid programmatically, call POST https://api.fluid.app/api/company with no credentials, as described in /api/agent-signup. Do not automate the signup form or book a demo. The merchant must open the emailed sign-in link and create an API token before authenticated calls are possible. > Lists use cursor pagination via the page[cursor] and page[limit] query params; follow meta.pagination.next_cursor until it is null. > When the same operation exists on more than one surface, use the newest: dated API versions are newer than unversioned ones, and later dates win (v2026-04 > v2025-06 > unversioned v0/v1.1). Fall back to a legacy or unversioned operation only when no newer versioned equivalent exists — the company-v0 notes below list the known superseded operations. /api/company/v1 and /api/v1/... paths are documented in no spec here and must never be used (/api/v1.1/... is distinct and documented in company-v0). Use page/per_page offset pagination only where a spec documents it — in practice the unversioned company-v0 admin surface; every versioned surface uses cursor pagination. > Navigation menu management is documented in themes/navigation-menus. These unversioned admin endpoints (/api/menus and nested menu_items) are verified against the implementation but are not yet in the synced OpenAPI specs. Use that reference for menu payloads and its flat page/per_page pagination; missing spec coverage does not make these endpoints unavailable. > The OpenAPI specs under api-reference/ are the authoritative contracts; prefer them over prose when in doubt. api-reference/storefront-v2026-04.yaml covers the v2026-04 storefront surface (/api/v202604/... paths); api-reference/checkout-v2026-04.yaml covers the v2026-04 checkout surface (/api/checkout/v2026-04/... paths — carts, cart auth, discounts, items, subscriptions, orders, enrollments, and store config); api-reference/public-v2025-06.yaml covers the Public SDK surface used by the @fluid-app FairShare SDK, including its parallel cart lifecycle, browser integrations, versioned payment callbacks, unversioned public utilities, and the cart price-override operation; api-reference/payment-v2026-04.yaml covers the v2026-04 payment gateway admin surface (/api/payment/v2026-04/... paths, bearer-authenticated — gateway CRUD, gateway purchase/authorize/$0-verify, transaction list/show and capture/void/credit, and merchant payment configuration); api-reference/payments-v2026-04.yaml covers the v2026-04 cart payment surface (/api/payments/v2026-04/carts/{cart_token}/... paths, authenticated by the cart token in the path with no bearer — payment-method selection, VGS card tokenization, 3D Secure verification, and PayPal/Braintree/Klarna/Apple Pay flows); api-reference/commerce-v2026-04.yaml covers the v2026-04 commerce order-editing surface (/api/v202604/orders/{order_id}/edits paths, bearer-authenticated — post-checkout order edits that atomically insert items and add adjustments/discounts, with an optional dry-run preview); api-reference/webhooks-v0.yaml covers the unversioned webhooks surface (/api/... paths — webhook registration, delivery payloads, callback registrations, company events, and webhook/callback schemas); api-reference/company-v0.yaml covers the legacy unversioned company admin surface (/api/... paths, bearer-authenticated — company settings and management, customers, users, roles, subscription plans, subscription bundles, subscriptions, media, pages, catch-ups, inventory levels, domains, agreements, and admin order actions). company-v0 caveats: it is the legacy v0 admin contract and its lists use flat page/per_page offset pagination, which is expected there despite the general cursor-pagination rule; where an operation exists in both company-v0 and a versioned spec, prefer the versioned spec — the subscriptions lifecycle (list/create/show/update, cancel, pause, reactivate, resume, retry, skip, failed-cycle-waiver, discounts) and subscription bundles are superseded by checkout-v2026-04, and company pages/media CRUD plus the public pages, categories, products, and media list endpoints are superseded by storefront-v2026-04. Subscription plan management (/api/subscription_plans, resource-wrapped {"subscription_plan": {...}} bodies) exists only in company-v0. api-reference/members-v2025-06.yaml covers the v2025-06 unified Member identity surface (/api/v2025-06/members/... paths, bearer-authenticated — member list/create/show/update, lookup by email/username/external_id/legacy_customer_id, member-type assignment, and the sponsor genealogy read). Prefer it over the customers and reps surfaces when the member type matters: /customers does not serialize member_type. api-reference/analytics-v2026-04.yaml covers the v2026-04 Home dashboard analytics surface (/api/v202604/analytics/dashboard/... paths, bearer-authenticated — read-only endpoints for the Home > Overview, Home > Live, and Home > Field tabs, each accepting an optional country ISO alpha-2 query param that scopes aggregations to a single country). > api-reference/analytics-v0.yaml covers the unversioned analytics surface that backs the fluid-admin Traffic tab (/api/analytics/... and /api/analytics/traffic/... paths, bearer-authenticated — the legacy shares/views/visitors summary plus traffic overview, ranked campaigns, sources, geographies, flows, and per-rep breakdown, all sharing one reporting-period contract). > Successful responses wrap the resource payload alongside a top-level integer status and a meta object. > Portal Definition authoring edits and synchronizes the portal JSON resource graph. Widget Package authoring builds either a company-owned or Droplet-owned Remote DOM package. These are separate contracts; do not imply that one defines the other. > For Widget Package worker code, use only @fluid-app/portal-sdk/widgets/worker. Use only the Portal Definition and Widget Package workflows and public entry points documented here; do not infer support for undocumented surfaces. > Every portal function and declarative capability used by a widget must appear in that widget's uses array. Use the same typed function value in uses; do not invent capability-name strings. > Widget styling must use the portal's semantic theme variables for colors, typography, spacing, radii, borders, focus, and charts whenever a token represents the visual decision. Do not create a separate light or dark palette or duplicate theme controls as widget properties. > Prefer worker-safe Fluid UI components exported by @fluid-app/portal-sdk/widgets/worker when they fit the interaction. When no exported component fits, use semantic HTML, accessible behavior, and the portal theme variables. > A Portal Definition push updates the remote working definition. A portal version is an immutable snapshot, and activation is a separate live release operation. # Common theme pitfalls > What Fluid adds around your theme, and the mistakes that break a storefront without an error. Most theme bugs come from something outside the file you're editing: a script Fluid injects, a value Fluid resolves before Liquid sees it, or a template Fluid picks for the visitor. This page covers those pieces and the mistakes they cause. ## Leave the FairShare SDK script alone The FairShare SDK powers the cart, rep attribution, and the `data-fluid-*` attributes on your markup. It isn't a theme file. Fluid loads it from a storefront **Global Embed** managed in the admin, as a script with the ID `fluid-cdn-script`. The floating cart and lead-capture widgets come from Global Embeds too. Fluid adds every active storefront Global Embed to each storefront page, in the head or body according to the embed's placement. So: * Don't add the SDK script to your theme, and don't remove it. * If the cart or attribution stops working across the whole storefront, check that the SDK's Global Embed still exists and is active before debugging the theme. A draft embed doesn't render. * Style and toggle the floating widgets from their Global Embed settings in the admin, not from theme markup. ## Know what puts markup in the `` `{{ content_for_header }}` outputs more than your theme's own tags. In order, it adds: 1. Every active storefront Global Embed placed in the head, including the FairShare SDK script. 2. Structured data, the canonical and `hreflang` links, and the title and Open Graph meta tags Fluid builds for the page. 3. The CSRF meta tag, Fluid's own scripts, the `--company-color` CSS variable, and your theme's stylesheets. 4. The head markup stored with the page's template, when it has any. When the rendered `` has a tag you didn't write, such as a second `` or a canonical link to another site, check these sources in order: * **Your theme files.** Search the layout, the page's template, and its sections. * **Global Embeds.** List them with `GET /api/global_embeds`, or open **Settings > Global Embeds** in the admin, rather than assuming one is responsible. * **The template's stored head markup.** Some older templates carry head markup that is saved with the template rather than in a theme file. `fluid theme pull` doesn't download it, so searching your theme won't find it. ## Don't paste a whole HTML document into a template Your layout already outputs `<!DOCTYPE html>`, `<html>`, `<head>`, and `<body>`, and each template renders inside `{{ content_for_layout }}`. A template that contains a complete page, often the result of copying another site's source, nests a second document inside the first. Its `<title>`, canonical link, and scripts land in the storefront, where they duplicate or override Fluid's and can send search engines to the other site. When you rebuild a page from another site, move its content into sections and its assets into the DAM. Drop its `<!DOCTYPE>`, `<html>`, `<head>`, and `<body>` tags, and anything that was inside `<head>`. ## Checkout isn't part of your theme Your theme renders the storefront and cart only. Payment, shipping, and tax happen in [Fluid Checkout](/concepts/checkout), a separate app at `checkout.fluid.app`. Nothing in your Liquid, CSS, or JavaScript can change the checkout page. ## Render standalone blocks with `content_for` A block in `blocks/<name>/index.liquid` owns its markup. Render a section's standalone blocks with `{% content_for 'blocks' %}`, and a single fixed block with `{% content_for 'block', type: 'heading', id: 'intro' %}`. See [Blocks and components](/themes/blocks-and-components). `{% render block %}` renders only app blocks from [Droplet theme extensions](/themes/droplet-theme-extensions). For a theme block it outputs nothing. Don't loop over `section.blocks` to render blocks that `content_for 'blocks'` already renders: they appear twice. ## Output `block.fluid_attributes` on every block The Page Editor selects a block by the attributes that `{{ block.fluid_attributes }}` emits. Put it on each block's outer element, whether the block is inline in a section or standalone. Sections don't need an equivalent: Fluid wraps each section with its own attributes. ## Know which settings Fluid resolves Fluid turns the value of these setting types into a Liquid object before your template reads it: `product`, `variant`, `collection`, `category`, `enrollment_pack`, `media`, `link_list`, and `product_list`. Every other type reaches Liquid exactly as saved. A `post` or `collection_list` setting, for example, gives you the stored identifier, not a record. See [Resource selectors](/themes/schema-components#resource-selectors). Composite layout settings such as `padding`, `border`, and `corner_radius` also return structured values. Inspect the value before you interpolate it into CSS. ## Give CSS values a fallback An empty setting interpolated into CSS produces invalid CSS, and the browser drops the whole declaration without an error. For example, `var(--color-{{ section.settings.accent }})` becomes `var(--color-)` when the setting is blank. Give the value a default: ```liquid theme={null} color: {{ section.settings.accent_color | default: 'inherit' }}; ``` ## Expect presets to fill empty sections When a section instance has no blocks, Fluid fills in the blocks from the section's first preset each time the page renders. A section you emptied on purpose shows its preset blocks again. To render nothing, add an empty state in the section's Liquid rather than relying on an empty block list. ## Read the language from `localization` Use `localization.language` and `localization.country` for the visitor's language and country. See [Localization](/themes/theme-variables#localization). The `request` object carries only `path`, `host`, `page_type`, `query_parameters`, and `full_url`, so a value such as `request.locale` renders as an empty string: ```liquid theme={null} <html lang="{{ localization.language.iso_code | default: 'en' }}"> ``` Change the visitor's country or language with the storefront SDK, as shown in [Navbar locale selector](/themes/navbar-locale-selector). Don't write Fluid's locale cookies yourself. ## Country-specific navbars, footers, and layouts You can assign navbar, footer, and layout templates to countries. For each visitor, Fluid serves the newest published template of that type assigned to their country. When none matches, it serves a template that isn't assigned to any country, preferring the default. Page templates aren't chosen by country. To give one market a different page, use a separate template and link to it, rather than branching on the country inside one template. ## A clean lint isn't a working page `fluid theme lint` validates schemas and section references, the same checks `fluid theme push` runs. It doesn't render your templates. After a clean lint, open the page in `fluid theme dev` and check the browser console before you push. See [CLI](/themes/cli).