Skip to main content
Every Squeditor project runs entirely based on its local squeditor.config.js file. This is the single source of truth that tells the core framework engine what CSS/JS to bundle, what pages to crawl, and how to distribute the final website. Here is a full breakdown of every available configuration option.

Core Settings

Define the core identity of your project and link it to the framework engine.

Component Selection

The components array is the most critical part of Squeditor’s architecture. It explicitly defines which UIKit3 modules should be compiled into your final uikit-components.css and uikit-components.js files. If a component is not in this list, its code will never load in the browser, keeping your site incredibly fast.

GSAP Integration

If your project utilizes the GreenSock Animation Platform (GSAP), configure the plugins and initialization scripts here.

Build Server & Snapshot Routing

Squeditor uses Vite for asset bundling and a PHP endpoint crawler for static HTML generation.

Multi-Theme Configuration

Use the themes object to generate multiple distinct websites (with different styling and page routing) from the same codebase simultaneously during the npm run build process.

Media Optimization

Squeditor includes an automated pipeline for compressing images and generating blurred placeholders natively during the build sequence.

Distribution

Configures how the final dist/ folder is archived into a .zip file for client handoff, and dictates which CLI tool (netlify or vercel) publishes the temporary preview URL.