All features

Content backend for custom websites.

Give clients and teams a real content admin while you keep full control over the frontend. Model pages, blocks, media, forms, taxonomies, and localized content through Arky.

Best for

  • marketing sites
  • content-heavy business sites
  • portfolio and catalog pages
  • localized websites

Use it when the website is custom-coded but the client still needs to edit content without calling a developer.

What this module gives your project.

Content nodes and blocks

Use this capability from your custom frontend while the operational side stays manageable in Arky admin.

Rich text and media

Use this capability from your custom frontend while the operational side stays manageable in Arky admin.

Forms and submissions

Use this capability from your custom frontend while the operational side stays manageable in Arky admin.

Localization

Use this capability from your custom frontend while the operational side stays manageable in Arky admin.

Admin editing

Use this capability from your custom frontend while the operational side stays manageable in Arky admin.

Custom UX without rebuilding backend state.

  • Content by key or ID
  • Localized fields
  • Media URLs and responsive assets
  • Form definitions and submissions

A client-facing back office for the same module.

  • Page and block editing
  • Media library
  • Taxonomies
  • Submission history
  • Localized content controls

Code the frontend. Connect Arky underneath.

Start with the frontend stack the project deserves, then connect only the Arky modules it needs. The admin, API, SDK, and backend workflows stay behind the custom experience.

  1. Model the content structure
  2. Fetch CMS nodes in the frontend
  3. Hand the admin editor to the client
import { createArkyStore } from "arky-sdk/storefront-store";

const arky = createArkyStore({
  baseUrl: "https://api.arky.io",
  storeId: "your-store-id",
  locale: "en",
});

await arky.setup({ hydrateCart: true });

// Use the module helpers your frontend needs.
// The client keeps full control over markup, routing, and UX.

Useful integration touchpoints.

  • GET /v1/storefront/{storeId}/nodes/key/{key}
  • POST /v1/storefront/{storeId}/forms/{id}/submit
Talk to us

Early access for custom frontend teams.