Release 7.24.0 adds a dark theme across the whole UI, background jobs to export and migrate schema contents, console logging for scripts with a log viewer, and new limits for GraphQL and asset processing. Here is what changed and how to use it.
One platform, centralized, connected, scalable.
Create once, publish everywhere — apps, websites, and server applications.
Never lose a change
Squidex tracks every update with full version history. Instantly compare versions, roll back when needed, and view detailed audit logs showing exactly who did what—and when.
Automate everything.
Every action in Squidex triggers an event—so you can connect to any external system. Automatically publish blog posts to Medium, post tweets, or sync updates the moment content changes
Your rules, your workflow.
Define who can create, review, and publish content. Squidex gives you full control with a powerful, customizable workflow engine designed to match even the most complex team structures.
Integrate like a PRO.
Access and control everything with a robust REST API built on modern standards like OpenAPI and OpenID Connect. Ideal for automation, CI/CD pipelines, and multi-language development environments.
Get exactly what you need.
Pull precise data from our GraphQL endpoint—no more over-fetching. Plus, use subscriptions for real-time updates directly in your website or app.
Deploy anywhere.
Squidex runs on any platform—via Docker or OS-specific binaries. Hosting in the cloud? Use our ready-to-go Helm charts for Kubernetes and scale effortlessly.
Speed at scale.
Powered by blazing-fast .NET 10, Squidex handles hundreds of thousands of content items with ease. Built from the ground up for high performance and low latency.
Command your content.
The CLI lets you sync data between instances, import/export assets, and manage configurations—fast and efficiently.
Peace of mind, built-in.
Move between on-premise and cloud with ease. With integrated backup and restore, your content is always safe—and always in your control.
Release 7.24.0 adds a dark theme across the whole UI, background jobs to export and migrate schema contents, console logging for scripts with a log viewer, and new limits for GraphQL and asset processing. Here is what changed and how to use it.
Most marketing sites start with one schema per page template and end up with a dozen near-identical models that no one dares to change. Modelling reusable blocks that mirror your front end components instead turns a page into an ordered list, and this post shows what that JSON looks like, how a renderer consumes it, and what it costs the people who have to edit it.
GraphQL and REST are usually treated as an either/or decision made once, at the start of a project. Comparing them on payload shaping, reference resolution, caching, tooling and error handling shows that the honest answer differs per request, and that mixing both in one application is a reasonable design rather than a failure of discipline.
Squidex 7.22.0 and 7.23.0 brought a simpler way to make string fields searchable, resolvable comments with a dedicated view, HTTP requests from scripts, and an upgrade to .NET 10 and Angular 21. The follow-up release added SSRF protection for asset downloads and scripting HTTP clients.