Convert Figma logo to code with AI

Squidex logosquidex

Headless CMS and Content Managment Hub

2,252
451
2,252
4

Top Related Projects

Welcome to the home of the Hot Chocolate GraphQL server for .NET, the Strawberry Shake GraphQL client for .NET and Banana Cake Pop the awesome Monaco based GraphQL IDE.

27,495

The flexible backend for all your projects 🐰 Turn your DB into a headless CMS, admin panels, or apps with a custom UI, instant APIs, auth & more.

63,346

πŸš€ Strapi is the leading open-source headless CMS. It’s 100% JavaScript/TypeScript, fully customizable, and developer-first.

The superpowered headless CMS for Node.js β€” built with GraphQL and React

3,260

Build bespoke content experiences with Craft.

Quick Overview

Squidex is an open-source headless CMS and content management hub built with ASP.NET Core and Angular. It provides a flexible and scalable solution for managing content across various platforms and devices, offering a powerful API for developers and an intuitive interface for content creators.

Pros

  • Highly customizable and extensible architecture
  • Supports multiple languages and localization
  • Offers a GraphQL API in addition to RESTful APIs
  • Includes built-in asset management and versioning

Cons

  • Steeper learning curve compared to traditional CMSs
  • Limited themes and templates available out-of-the-box
  • Requires technical expertise for setup and customization
  • Smaller community compared to more established CMS solutions

Getting Started

To get started with Squidex, follow these steps:

  1. Install Docker on your machine
  2. Run the following command to start Squidex:
docker run -d -p 80:80 --name squidex \
    -e URLS__BASEURL=http://localhost \
    -e EVENTSTORE__MONGODB__CONFIGURATION="mongodb://mongo" \
    -e STORE__MONGODB__CONFIGURATION="mongodb://mongo" \
    -e IDENTITY__ADMINEMAIL="admin@squidex.io" \
    -e IDENTITY__ADMINPASSWORD="<your-password>" \
    squidex/squidex
  1. Access the Squidex dashboard at http://localhost
  2. Log in with the admin email and password you set in the Docker command

For more detailed instructions and advanced configuration options, refer to the official Squidex documentation.

Competitor Comparisons

Welcome to the home of the Hot Chocolate GraphQL server for .NET, the Strawberry Shake GraphQL client for .NET and Banana Cake Pop the awesome Monaco based GraphQL IDE.

Pros of graphql-platform

  • Focused on GraphQL implementation, providing a comprehensive solution for building GraphQL APIs in .NET
  • Offers code-first approach, allowing developers to define schemas using C# classes
  • Includes built-in support for real-time subscriptions and data loaders

Cons of graphql-platform

  • Steeper learning curve for developers new to GraphQL concepts
  • Less suitable for content management scenarios compared to Squidex's headless CMS approach
  • May require additional setup for features like content versioning and localization

Code Comparison

graphql-platform:

public class Query
{
    public Book GetBook() =>
        new Book { Title = "C# in depth", Author = "Jon Skeet" };
}

Squidex:

[RuleAction]
public sealed class CustomAction : RuleAction
{
    public override Task ExecuteAsync(IRuleEventContext context)
    {
        // Custom action logic
    }
}

While graphql-platform focuses on defining GraphQL schemas and resolvers, Squidex provides a more content-centric approach with features like custom rule actions for content management workflows.

27,495

The flexible backend for all your projects 🐰 Turn your DB into a headless CMS, admin panels, or apps with a custom UI, instant APIs, auth & more.

Pros of Directus

  • More flexible data modeling with support for various field types and relationships
  • Extensive API options, including REST, GraphQL, and real-time subscriptions
  • User-friendly interface with a modern, customizable admin app

Cons of Directus

  • Steeper learning curve due to its extensive feature set
  • Potentially higher resource requirements for larger projects
  • Less focus on content management specific features compared to Squidex

Code Comparison

Squidex (C#):

public class ContentController : ApiController
{
    [HttpGet]
    [Route("api/content/{app}/{schema}")]
    public IActionResult GetContent(string app, string schema)
    {
        // Content retrieval logic
    }
}

Directus (JavaScript):

router.get('/items/:collection', async (req, res) => {
    const { collection } = req.params;
    const items = await getItems(collection);
    res.json({ data: items });
});

Both projects offer robust content management capabilities, but Directus provides a more flexible and extensible platform for various data-driven applications. Squidex, on the other hand, focuses more on traditional content management scenarios and may be easier to set up for simpler use cases.

63,346

πŸš€ Strapi is the leading open-source headless CMS. It’s 100% JavaScript/TypeScript, fully customizable, and developer-first.

Pros of Strapi

  • More extensive plugin ecosystem and marketplace
  • Larger community and more active development
  • Better documentation and learning resources

Cons of Strapi

  • Higher resource consumption, especially for larger projects
  • Steeper learning curve for complex customizations
  • Less flexible content modeling compared to Squidex

Code Comparison

Strapi (JavaScript):

module.exports = {
  lifecycles: {
    async beforeCreate(data) {
      data.slug = slugify(data.title, { lower: true });
    },
  },
};

Squidex (C#):

public class SlugifyContentTrigger : IContentTrigger
{
    public Task<ContentData> OnCreatedAsync(IContentEntity content, ContentData data)
    {
        data["slug"] = SlugifyTitle(data["title"].ToString());
        return Task.FromResult(data);
    }
}

Both Strapi and Squidex are headless CMS platforms, but they differ in their approach and implementation. Strapi offers a more user-friendly experience with its extensive plugin ecosystem and active community. However, it may consume more resources and have a steeper learning curve for complex customizations. Squidex, on the other hand, provides more flexibility in content modeling and potentially better performance for larger projects, but has a smaller community and fewer out-of-the-box features compared to Strapi.

The superpowered headless CMS for Node.js β€” built with GraphQL and React

Pros of Keystone

  • More flexible and customizable, allowing developers to create complex data models and relationships
  • Offers a GraphQL API out of the box, providing a powerful query language for data retrieval
  • Supports serverless deployments, making it easier to scale and manage infrastructure

Cons of Keystone

  • Steeper learning curve due to its flexibility and extensive feature set
  • Requires more setup and configuration compared to Squidex's more opinionated approach
  • May have higher resource requirements for larger projects

Code Comparison

Keystone schema definition:

const { Text, Relationship } = require('@keystonejs/fields');

const listSchema = {
  fields: {
    title: { type: Text },
    author: { type: Relationship, ref: 'User' },
  },
};

Squidex schema definition:

{
  "name": "blog",
  "fields": [
    { "name": "title", "type": "string" },
    { "name": "author", "type": "references", "references": "users" }
  ]
}

Both Keystone and Squidex offer powerful content management capabilities, but they cater to different use cases. Keystone provides more flexibility and customization options, making it suitable for complex projects with specific requirements. Squidex, on the other hand, offers a more streamlined approach with a focus on ease of use and quick setup. The choice between the two depends on the project's complexity, scalability needs, and development team's expertise.

3,260

Build bespoke content experiences with Craft.

Pros of Craft CMS

  • More mature and established project with a larger community
  • Extensive plugin ecosystem for extending functionality
  • User-friendly control panel for content management

Cons of Craft CMS

  • Requires PHP, which may not be preferred by all developers
  • Commercial license required for some features and use cases
  • Steeper learning curve for developers new to the platform

Code Comparison

Craft CMS (Twig template):

{% set entries = craft.entries()
    .section('blog')
    .limit(10)
    .all() %}

{% for entry in entries %}
    <h2>{{ entry.title }}</h2>
    {{ entry.body }}
{% endfor %}

Squidex (React component):

import { useQuery } from '@squidex/squidex';

function BlogPosts() {
  const { data } = useQuery('blog', { take: 10 });
  return (
    <>
      {data.items.map(post => (
        <div key={post.id}>
          <h2>{post.data.title}</h2>
          <div>{post.data.body}</div>
        </div>
      ))}
    </>
  );
}

Both Craft CMS and Squidex offer powerful content management capabilities, but they cater to different developer preferences and tech stacks. Craft CMS provides a more traditional CMS experience with PHP and Twig, while Squidex embraces a headless approach with a focus on API-first development and modern JavaScript frameworks.

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

Squidex Logo

What is Squidex?

Squidex is an open source headless CMS and content management hub. In contrast to a traditional CMS Squidex provides a rich API with OData filter and Swagger definitions. It is up to you to build your UI on top of it. It can be website, a native app or just another server. We build it with ASP.NET Core and CQRS and is tested for Windows and Linux on modern browsers.

Discourse topics Dev Docker Pulls

Read the docs at https://docs.squidex.io/ (work in progress) or just check out the code and play around.

How to make feature requests, get help or report bugs?

Please join our community forum: https://support.squidex.io

Status

Current Version GitHub release Roadmap: https://trello.com/b/KakM4F3S/squidex-roadmap

Prerequisites

Deployment Options

PlatformDocumentationQuicklink
AzureDocsDeploy To Azure
AWSDocs
DockerDocsDocker Compose
GCPDocs
HerokuDocsDeploy to Heroku
IISDocs
K8SDocs
RenderDocsDeploy to Render
VultrDocsDeploy to Vultr

Contributors

Core Team and Founders

Contributors

  • civicplus (Avd6977, dsbegnoce): Google Maps support, custom regex patterns and a lot of small improvements.
  • cpmstars: Asset support for rich editor.
  • guohai: FTP asset store support, Email rule support, custom editors and bug fixes.
  • pushrbx: Azure Store support.
  • razims: GridFS support.
  • sauravvijay: Kafka Rule action.

Contributing

Please create issues to report bugs, suggest new functionalities, ask questions or just share your thoughts about the project. We will really appreciate your contribution, thanks.

Cloud Version

Although Squidex is free it is also available as a Saas version on https://cloud.squidex.io.