Documentation

Site Configuration

The site configuration page contains settings that affect how your entire content site behaves — from image processing and localization to key naming conventions and site identity. These are site-level controls managed by administrators, accessible from the settings area of the SleekCMS interface.

This page is a reference for every setting on the configuration screen.

Site Builder (SSG)

Enables the integrated static site builder. When active, you can bind EJS templates to your content models and generate a fully deployable static website from within SleekCMS — no external build tools, servers, or repositories required.

With the site builder enabled, the template editor, preview system, and deployment options become available in the interface. Disabling it hides these features and treats the site as a purely headless CMS where content is consumed exclusively through the content API.

→ Site Builder

Page Type Models

Controls whether page models use the "page type" classification — models that behave as entries with a slug field. This affects how content is organized in the editor and how routes are generated.

When enabled, page type models appear alongside standard page models in the modeling interface. This is primarily relevant if you are using the site builder or if your content architecture benefits from treating certain routable content as entry-like structures with slug-based routing.

→ Page Models

Image Processing with Imgix

Enables Imgix as the image processing backend for your site. When active, image URLs are routed through Imgix for on-the-fly transformations — resizing, cropping, format conversion, and optimization — instead of using SleekCMS's default image processing.

Web Folder Source Base URL

When using Imgix, you configure a web folder source base URL. This is the base URL that Imgix uses to fetch your original images. Imgix retrieves the source image from this URL and applies transformations based on query parameters before delivering the optimized result.

To set this up, you need an Imgix account with a web folder source configured to point to your image origin. The base URL you enter here must match the source configuration in your Imgix dashboard.

→ Image Processing using Imgix

Localization and Translations

Enables multi-language content support for your site. When active, you can maintain translated versions of your content across the locales you configure.

Supported locales and languages are configured separately from the main menu. This setting activates the translation workflow — once enabled, content editors see language-switching controls in the editor and can create and manage translated content for each configured locale.

The content API respects the lang parameter when fetching content, returning the appropriate translation for the requested locale. In the site builder, templates have access to the current language context during rendering.

// Fetch content in a specific language
const client = await createSyncClient({
  siteToken: 'your-site-token',
  lang: 'es'
});

const page = client.getPage('/about');
// Returns the Spanish translation of the page

→ Supporting Multiple Languages

Attribute Key-Name Style

Controls the naming convention used when auto-generating handles (the programmatic key names used to access content fields in API responses and templates). When you create a field or model and provide a display name, SleekCMS auto-populates the handle based on the convention selected here.

For example, a field named "Hero Image" might produce a handle of hero_image, heroImage, or hero-image depending on the selected style.

This setting applies to auto-generated handles only. You can always override the auto-generated handle with a custom value when creating or editing a field or model. Changing this setting does not retroactively rename existing handles — it only affects newly created fields and models going forward.

→ Key Naming Default Style

Display Name

The display name of your content site. This is the human-readable label that appears in the SleekCMS interface — in the site switcher, the dashboard, and anywhere the site is identified by name.

The display name is purely cosmetic and does not affect URLs, API endpoints, or content delivery. Change it at any time without impacting your content, templates, or integrations.

Site Clone Token

A clone token allows anyone who has it to create a complete copy of your site — including all models, content, and site builder code (templates and assets). Each clone token corresponds to a snapshot of the site at the moment the token was created. Changes made to the original site after the token was generated are not reflected in clones made from that token.

Clone tokens are useful for creating starter templates, sharing site architectures with clients or team members, or bootstrapping new projects from an existing site structure. Treat clone tokens with the same care as credentials — anyone with the token can duplicate your entire site.

Delete Site

Permanently deletes the content site and all associated data — models, content, entries, templates, assets, media, and configuration. This action is irreversible. There is no recovery mechanism once a site is deleted.

Before deleting, ensure you have exported any content or templates you want to preserve. If you are using the site builder, consider downloading the generated site as a ZIP archive before deletion.

→ Static Site Downloads

What's Next