<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sebastian Stehle on Medium]]></title>
        <description><![CDATA[Stories by Sebastian Stehle on Medium]]></description>
        <link>https://medium.com/@sebastian_61919?source=rss-179bebbb4a5a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*epuKHPzQdHjpswOfmgHEeA.jpeg</url>
            <title>Stories by Sebastian Stehle on Medium</title>
            <link>https://medium.com/@sebastian_61919?source=rss-179bebbb4a5a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:50:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sebastian_61919/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Content Modelling for a Design System: Components over Page Types]]></title>
            <link>https://medium.com/squidex/content-modelling-for-a-design-system-components-over-page-types-b525c97a0b9a?source=rss-179bebbb4a5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b525c97a0b9a</guid>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Sebastian Stehle]]></dc:creator>
            <pubDate>Thu, 01 Oct 2026 07:04:36 GMT</pubDate>
            <atom:updated>2026-10-01T07:04:36.153Z</atom:updated>
            <content:encoded><![CDATA[<p>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.</p><p>A marketing site usually starts with a handful of schemas: HomePage, ProductPage, PricingPage, CaseStudy. Each one has exactly the fields its template needs. Hero headline, hero image, three feature columns, a testimonial quote, a closing call to action. It is fast to build and easy for an editor to understand, because the form looks like the page.</p><p>Then the second product launches. The new page needs the same hero, the same feature columns, but a comparison table instead of the testimonial. You copy ProductPage into ProductPageV2. Six months later you have eleven page schemas, four slightly different definitions of a hero, and a design system where the Hero component has one implementation in code and four in the content model.</p><p>The mismatch is the real problem. Your front end already decomposes pages into components. Your content model does not. Every change to a shared component has to be replayed by hand across every schema that happens to inline it.</p><h4>A page is an ordered list</h4><p>The alternative is to model the components, not the pages. One schema per component type: Hero, FeatureGrid, Testimonial, ComparisonTable, CtaBanner. Each has the fields that component actually takes as props, and nothing else.</p><p>A page then shrinks to almost nothing: a slug, SEO metadata, and an ordered list of component instances.</p><pre>{<br>  &quot;slug&quot;: &quot;platform&quot;,<br>  &quot;seo&quot;: {<br>    &quot;title&quot;: &quot;Platform&quot;,<br>    &quot;description&quot;: &quot;What the platform does.&quot;<br>  },<br>  &quot;blocks&quot;: [<br>    {<br>      &quot;type&quot;: &quot;hero&quot;,<br>      &quot;headline&quot;: &quot;Ship content faster&quot;,<br>      &quot;subline&quot;: &quot;One model, every channel.&quot;,<br>      &quot;image&quot;: { &quot;id&quot;: &quot;a31f&quot;, &quot;alt&quot;: &quot;Abstract shapes&quot; },<br>      &quot;variant&quot;: &quot;dark&quot;<br>    },<br>    {<br>      &quot;type&quot;: &quot;featureGrid&quot;,<br>      &quot;columns&quot;: 3,<br>      &quot;features&quot;: [<br>        { &quot;title&quot;: &quot;Schemas&quot;, &quot;body&quot;: &quot;Define fields once.&quot; },<br>        { &quot;title&quot;: &quot;API&quot;, &quot;body&quot;: &quot;REST and GraphQL.&quot; },<br>        { &quot;title&quot;: &quot;Workflows&quot;, &quot;body&quot;: &quot;Review before publish.&quot; }<br>      ]<br>    },<br>    {<br>      &quot;type&quot;: &quot;ctaBanner&quot;,<br>      &quot;text&quot;: &quot;Read the documentation&quot;,<br>      &quot;href&quot;: &quot;/docs&quot;<br>    }<br>  ]<br>}</pre><p>The shape of each entry in blocks is the prop interface of a component. That is the whole idea. If Hero gains a variant prop in code, the Hero schema gains a variant field, once, and every page that uses a hero inherits it.</p><p>How you store this depends on your CMS. Some systems give you a polymorphic list field that holds inline objects of different types. Others model each component as its own content item and let the page hold an ordered list of references. Squidex supports both references between schemas and nested array fields, so you can pick per component: inline for blocks that only ever live on one page, references for blocks that are genuinely shared, such as a footer CTA used site-wide.</p><h4>The renderer is a switch statement</h4><p>On the front end, the payoff is that rendering becomes mechanical. You map a type discriminator to a component and pass the rest through.</p><pre>import { Hero } from &quot;./Hero&quot;;<br>import { FeatureGrid } from &quot;./FeatureGrid&quot;;<br>import { Testimonial } from &quot;./Testimonial&quot;;<br>import { CtaBanner } from &quot;./CtaBanner&quot;;<br><br>const registry = {<br>  hero: Hero,<br>  featureGrid: FeatureGrid,<br>  testimonial: Testimonial,<br>  ctaBanner: CtaBanner,<br>} as const;<br><br>type Block = { type: keyof typeof registry } &amp; Record&lt;string, unknown&gt;;<br><br>export function Blocks({ blocks }: { blocks: Block[] }) {<br>  return (<br>    &lt;&gt;<br>      {blocks.map((block, i) =&gt; {<br>        const Component = registry[block.type];<br>        if (!Component) {<br>          if (process.env.NODE_ENV !== &quot;production&quot;) {<br>            console.warn(`Unknown block type: ${block.type}`);<br>          }<br>          return null;<br>        }<br>        return &lt;Component key={i} {...(block as any)} /&gt;;<br>      })}<br>    &lt;/&gt;<br>  );<br>}</pre><p>Two things to get right here. First, unknown types must not crash the page: an editor may publish a block from a newer deployment, or you may remove a component before the content is cleaned up. Skip and log. Second, generate your TypeScript types from the schema definitions rather than hand-writing them, so that a field rename in the model shows up as a compile error instead of an undefined in production.</p><p>A stable key matters too. The array index works until someone reorders blocks and React reuses state across different components. If your CMS gives each block instance an id, use it.</p><h4>What this costs editors</h4><p>Be honest about the trade-off, because it is real.</p><p>With page types, the editing form is a description of the page. Fill in the hero headline, fill in the three features, done. Nothing can be in the wrong order, nothing can be missing, nothing can be duplicated by accident.</p><p>With components, the editor gets an empty list and a menu of twenty block types. That is more freedom and more ways to produce something ugly: four heroes stacked on top of each other, a dark section next to another dark section, a page with no call to action. The design system constrains how each block looks, not how they combine.</p><p>Things that reduce the cost:</p><ul><li><strong>Name blocks for intent, not markup.</strong> Testimonial rather than QuoteWithImageRight. Editors pick by meaning; developers map meaning to markup.</li><li><strong>Restrict the allowed set per page kind.</strong> A blog post does not need a pricing table. If your CMS lets you limit which schemas a reference or array field accepts, use it rather than relying on convention.</li><li><strong>Keep component field counts small.</strong> If a block has nineteen fields, most of them are styling knobs that belong in the design system, not in content.</li><li><strong>Invest in preview.</strong> Component modelling moves layout decisions to the editor, so the editor needs to see the result before publishing. A preview URL that renders draft content is not optional here; it is the thing that makes the model usable.</li><li><strong>Provide starting points.</strong> A new page that begins as a copy of a reviewed example beats a new page that begins as an empty list.</li></ul><h4>Where page types still earn their keep</h4><p>Do not convert everything. Content with a fixed, meaningful structure should stay structured: a job posting has a title, a location, a department and a description, and nothing good comes from letting someone assemble it out of blocks. The same goes for product records, events and author profiles.</p><p>The useful split is between content that <em>is</em> data and content that <em>is</em> a page. Data gets a tight schema. Pages get a block list. Often a page combines both: a structured CaseStudy entity plus an optional block list for the free-form section underneath.</p><p>A practical migration path is to leave existing page types alone and add a single blocks field to them. New sections go into the list, old fields stay until the template no longer reads them. You get the composability without a big-bang remodel.</p><p>If you are starting this now, the first step is not in the CMS at all: list the components your design system actually ships, with their props. That list is your content model, and most of the modelling work is deciding which props are content and which are design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b525c97a0b9a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/squidex/content-modelling-for-a-design-system-components-over-page-types-b525c97a0b9a">Content Modelling for a Design System: Components over Page Types</a> was originally published in <a href="https://medium.com/squidex">Squidex</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Squidex Q3 2026: Dark Theme, Content Export, Schema Migration]]></title>
            <link>https://medium.com/squidex/squidex-q3-2026-dark-theme-content-export-schema-migration-0c2477c96b46?source=rss-179bebbb4a5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c2477c96b46</guid>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Sebastian Stehle]]></dc:creator>
            <pubDate>Thu, 01 Oct 2026 07:03:36 GMT</pubDate>
            <atom:updated>2026-10-01T07:03:36.162Z</atom:updated>
            <content:encoded><![CDATA[<p>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.</p><p>Squidex 7.24.0 was released on 2026–09–28 and is the only release of the quarter. It is a large one, so this post covers the changes that are most likely to affect your daily work, and then groups the rest.</p><h4>A dark theme for the whole UI</h4><p>The management UI now has a dark theme. You select it in the profile menu, where the options are Light, Dark and System. System follows the preference reported by your operating system.</p><p>The theme is not limited to the main shell. It is also applied to the code editor, the rich text editor, GraphiQL, the API documentation and the login pages.</p><p>If you build custom editors or plugins, the editor SDK exposes two new functions so your UI can follow the same theme:</p><pre>const field = new SquidexFormField();<br><br>applyTheme(field.getTheme());<br><br>field.onThemeChanged(theme =&gt; {<br>    applyTheme(theme);<br>});</pre><p>Alongside this, all colors in the frontend are now defined as CSS variables. If you have custom styles that rely on the previous variables, they might need to be adjusted.</p><h4>Export and migrate contents as background jobs</h4><p>Two new jobs operate on all contents of a schema.</p><p>The first is an export to CSV or JSON. You can start it from the new export dialog in the content list, or through the API:</p><pre>POST /api/apps/{app}/schemas/{schema}/contents/export</pre><p>The second is a migration of all contents to the current schema definition. It removes deleted fields and components, drops values with incompatible types and moves values after partitioning changes. This is useful when a schema has evolved over time and older content items still carry data that no longer matches the definition. Start it in the schema settings or with:</p><pre>POST /api/apps/{app}/schemas/{schema}/contents/migrate</pre><p>All endpoints that start jobs now accept an optional ?reference= query parameter. The value is returned as reference in the job, so you can correlate a job you started from your own automation with the job list.</p><h4>Console logging for scripts</h4><p>Content and asset scripts now support console.log, console.info, console.warn, console.error and console.debug. The output is collected and shown in a new &quot;Script Logs&quot; settings page, and is also available through the API:</p><pre>GET /api/apps/{app}/script-logs</pre><p>Logging can be configured with the scripting:logs option.</p><p>Scripting also got faster and easier to debug. Jint was upgraded to 4.16.1, scripts are now compiled once per query instead of once per item, the error message when a function is not available in the current script is clearer, and autocompletion shows function parameters.</p><h4>New limits for GraphQL, assets and logging</h4><p>Several options were added to put a ceiling on expensive operations.</p><p>For GraphQL there are now graphql:maxDepth, which defaults to 30, and graphql:maxComplexity, which is off by default. Apollo tracing is now disabled by default and can be turned back on with graphql:enableTracing. The GraphQL schema is also no longer rebuilt for every app change.</p><p>For assets, assets:maxConcurrentResizes limits how many image resizes run in parallel, and concurrent requests for the same thumbnail are only resized once. assets:maxCacheDuration caps the cache duration that a request can ask for and defaults to 365 days.</p><p>For content queries, contents:maxFullTextResults limits the number of results returned from the full text index and defaults to 1000. For the request log, logging:maxPendingItems limits the queue when the log store is unavailable.</p><h4>Everything else</h4><p>Client secrets can be regenerated while keeping the client ID, via PUT apps/{app}/clients/{id}/secret or in the UI. Rules got a flow step for Azure Service Bus queues and topics, and the &quot;Create content&quot; flow step now supports an optional ID for upserts plus a patch option. The rich text editor gained a plainHtml node type, the content editor marks fields that are only required on publish, and uploading a duplicate file now asks whether you want to store it as a new asset anyway.</p><p>On the security side, deleting users requires the new squidex.admin.users.delete permission, SSRF protection now covers the HTTP client of the identity services, protected assets are no longer cached by public caches, and escaping of JSON paths in SQL queries was hardened.</p><p>The backend received performance work across workflows, role resolution, validation, rules and EF Core queries, size limits for several in-memory caches, source-generated log methods and dependency updates including MongoDB.Driver 3.10.0 and Magick.NET 14.16.0. MongoDB now caches total counts for unfiltered queries, skips counting when it is not needed, supports AWS IAM authentication for Atlas, retries index creation after transient errors and reads legacy GUIDs correctly. For SQL, the JSON helper functions are created by an EF Core migration instead of at startup, the OpenIddict token type column was widened for OpenIddict 7, and deleted items are now ignored in queries for references, asset folders and scheduled contents.</p><p>A number of frontend fixes are included as well, among them overflow menus, the date-time editor with seconds, saved queries, asset tags, the item count for reference and asset fields in lists, and collapse and expand of content fields. The inline filter now has search and reset buttons.</p><p>If you maintain plugins, note the breaking changes: IContentWorkflow is resolved per schema through IContentWorkflows, IJintExtension receives the Jint Engine, and Context is immutable.</p><p>The full changelog for 7.24.0 lists every entry, and the configuration options mentioned here are documented with the rest of the Squidex settings.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c2477c96b46" width="1" height="1" alt=""><hr><p><a href="https://medium.com/squidex/squidex-q3-2026-dark-theme-content-export-schema-migration-0c2477c96b46">Squidex Q3 2026: Dark Theme, Content Export, Schema Migration</a> was originally published in <a href="https://medium.com/squidex">Squidex</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GraphQL or REST: Choosing per Use Case, Not per Project]]></title>
            <link>https://medium.com/squidex/graphql-or-rest-choosing-per-use-case-not-per-project-b536bc62032a?source=rss-179bebbb4a5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b536bc62032a</guid>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Sebastian Stehle]]></dc:creator>
            <pubDate>Fri, 04 Sep 2026 11:50:46 GMT</pubDate>
            <atom:updated>2026-09-04T11:50:46.777Z</atom:updated>
            <content:encoded><![CDATA[<p>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.</p><p>Most headless content systems, Squidex included, expose the same content through more than one API. The stored documents are identical, the permission model is identical, the query capabilities overlap heavily. What differs is the shape of the contract between your application and the content.</p><p>Because the decision usually gets made once, in an architecture meeting, it tends to be framed as a project-level choice: “we’re a GraphQL shop” or “we use REST everywhere”. That framing hides the fact that the two APIs are good at different things, and that a single frontend often has both kinds of request in it.</p><h4>Payload shaping</h4><p>This is the difference everyone knows. With REST you get the representation the server decided on. With GraphQL you get the fields you asked for.</p><p>For a landing page that pulls a headline, a teaser and a hero image out of documents that also contain a full body, an SEO block and a dozen editorial fields, the difference is real. Over a mobile connection, shipping 40 KB of JSON to render 400 bytes of text is a measurable cost.</p><p>Many REST APIs offer a field projection parameter, which closes part of the gap:</p><pre>GET /content/articles?fields=title,teaser,heroImage&amp;limit=10</pre><p>That covers flat selection. What it does not cover well is <em>different</em> selection at different depths — the full body for the first item, only titles for the rest. GraphQL handles that without inventing a query-parameter dialect:</p><pre>{<br>  featured: articles(top: 1) {<br>    title<br>    body<br>    author { name avatar { url } }<br>  }<br>  recent: articles(top: 10, skip: 1) {<br>    title<br>    slug<br>  }<br>}</pre><p>If you never need that, projection parameters on REST are enough and considerably less machinery.</p><h4>Reference resolution</h4><p>This is the difference that actually decides most cases, and it gets less attention than payload size.</p><p>Content models are graphs. An article references an author, the author references an organisation, the article references a category and three related articles, each of which has a cover image asset. Rendering one page means walking that graph.</p><p>Over REST, you walk it with requests. You fetch the article, read the reference IDs, fetch the referenced items, then fetch what those reference. Three levels deep on a page with a dozen components is a waterfall, and each round trip pays the full latency between your renderer and the API. Some REST APIs let you resolve a level of references inline, which flattens the first hop but rarely the whole tree.</p><p>Over GraphQL, the traversal is expressed in the query and resolved server-side in one round trip. For page composition — one request that assembles everything a route needs — this is the strongest argument in GraphQL’s favour, stronger than payload size.</p><p>The inverse also holds. A search-as-you-type endpoint returning ten titles has no graph in it. Resolving references is not a problem you have, so the tool that solves it buys you nothing.</p><h4>Caching</h4><p>Here REST wins on infrastructure you already own.</p><p>A GET request with a stable URL is cacheable by every layer between the client and the origin: the browser cache, the service worker, a CDN, a reverse proxy. ETag and If-None-Match work. Cache-Control works. Invalidating a path prefix at the CDN works.</p><p>GraphQL is conventionally a POST to a single endpoint, which means the URL carries no information and none of that machinery applies. You can work around it — persisted queries turn a query into an ID that can travel in a GET, and client-side normalised caches like Apollo or urql cache at the entity level rather than the response level — but these are additional systems to run and reason about, not properties you get for free.</p><p>For content that is read far more often than it is written, and served to anonymous users, the boring cacheability of REST is worth a lot. For an authenticated dashboard where every response is user-specific and uncacheable anyway, you give up nothing by using GraphQL.</p><h4>Tooling and typing</h4><p>GraphQL ships a machine-readable schema as part of the protocol. That gives you introspection, editor completion, and generated TypeScript types for queries and responses without maintaining a separate contract file. When a field is removed from a content type, code generation fails at build time instead of at 2 a.m.</p><p>REST can reach a similar place through OpenAPI, but the schema is a separate artefact that has to be kept accurate. Whether it is accurate depends on how it is produced.</p><p>Against that, REST needs no client library. curl, fetch, a shell script, a webhook consumer in a language with no GraphQL tooling — all of them can talk to it today. For server-to-server integrations, build scripts and one-off data pulls, that matters more than generated types.</p><h4>Error handling</h4><p>REST puts the outcome in the status line. 404 means missing, 403 means forbidden, 429 means slow down. Every HTTP client, proxy, retry policy and monitoring dashboard already understands this.</p><p>GraphQL usually answers 200 OK and puts failures in an errors array alongside whatever data it managed to resolve. Partial success is expressible, which is genuinely useful when one component of a page fails and the rest should still render. It also means your retry logic and your alerting cannot rely on status codes; something in your stack has to inspect the body. If your observability is built on HTTP status metrics, GraphQL requests will look uniformly healthy while failing.</p><h4>Mixing them on purpose</h4><p>Once the comparison is laid out per dimension, the per-project framing stops making sense. In one application:</p><ul><li>The route-level page composition query — deep, sparse, latency-sensitive, one request per render — is a good fit for GraphQL.</li><li>The paginated article list behind a CDN, the sitemap generator, the incremental build script that pulls changed items — flat, cacheable, no graph traversal — are a good fit for REST.</li><li>The webhook receiver that fetches one item by ID after a change notification does not need a query language at all.</li></ul><p>The cost of mixing is real but bounded: two auth code paths if the APIs authenticate differently, two error-handling shapes, and a slightly larger surface for new team members to learn. Against that, you avoid pushing every request through the model that suits half of them.</p><h4>A rough decision rule</h4><p>Ask three questions about the specific request, not about the project:</p><ol><li>Does it traverse references more than one level deep? If yes, lean GraphQL.</li><li>Is the response identical for many users and read far more than written? If yes, lean REST and let a CDN serve it.</li><li>Is the consumer a browser with a typed client, or a script, a build step, another service? Typed clients benefit from the schema; scripts benefit from a URL.</li></ol><p>When the answers conflict, latency and caching usually dominate over developer convenience, because they show up in production and convenience shows up in review.</p><p>If you want to test this on your own model, take the heaviest route in your application, count the round trips it currently makes and the bytes it discards, then do the same for your simplest list endpoint. The two numbers will usually point in different directions, and that is the point.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b536bc62032a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/squidex/graphql-or-rest-choosing-per-use-case-not-per-project-b536bc62032a">GraphQL or REST: Choosing per Use Case, Not per Project</a> was originally published in <a href="https://medium.com/squidex">Squidex</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Seamlessly Integrate Squidex into Your Tech Stack Without Reinventing the Wheel!]]></title>
            <link>https://medium.com/squidex/seamlessly-integrate-squidex-into-your-tech-stack-without-reinventing-the-wheel-e65c953fb39c?source=rss-179bebbb4a5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e65c953fb39c</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[headless-cms]]></category>
            <dc:creator><![CDATA[Sebastian Stehle]]></dc:creator>
            <pubDate>Fri, 04 Sep 2026 11:16:27 GMT</pubDate>
            <atom:updated>2026-09-04T11:16:27.514Z</atom:updated>
            <content:encoded><![CDATA[<p>Integrate Squidex seamlessly to your tech stack. With its headless architecture and robust API, it provides the freedom to define your schemas, choose your tools, and deliver content across multiple platforms.</p><p>Let’s face it starting from scratch with a new CMS can be a daunting task. Migrating content, rebuilding functionality, and rewriting integrations can quickly turn into a developer’s nightmare. But what if you could leverage the power of Squidex, a headless CMS known for its flexibility and scalability, without throwing out your entire tech stack?</p><h4><strong>What exactly is a Headless CMS?</strong></h4><p>A headless CMS is a content management system that decouples the content repository (“body”) from the presentation layer (“head”). Unlike traditional CMS solutions that tightly integrate content creation and delivery, a headless CMS provides an API to deliver content to any frontend or device. This allows developers to use any technology stack to design and implement the user interface, enabling greater flexibility and scalability. Content creators can manage and update content in the backend, while developers can independently build and optimize the frontend experience for websites, mobile apps, IoT devices, and more.</p><h4><strong>Advantages of Headless CMS</strong></h4><p>A headless CMS comes with a wide range of advantages including:</p><ol><li><strong>Flexibility:</strong> Integrates with any frontend technology or framework.</li><li><strong>Scalability:</strong> Easily handles growing content and traffic demands.</li><li><strong>Performance:</strong> Optimized content delivery via APIs improves load times.</li><li><strong>Security:</strong> Separates content management from the presentation layer, enhancing security.</li><li><strong>Omnichannel Delivery:</strong> Publishes content to multiple platforms from a single source.</li><li><strong>Developer Freedom:</strong> Allows developers to choose their preferred tools and technologies.</li><li><strong>Future-Proof:</strong> Adapts to new technologies and platforms without extensive rework.</li><li><strong>Streamlined Workflows:</strong> Separates content creation from frontend development for parallel workflows.</li><li><strong>Enhanced Customization:</strong> Tailors frontend experiences without CMS constraints.</li><li><strong>Faster Development:</strong> Accelerates project timelines by decoupling frontend and backend tasks.</li></ol><p>And with so many conventional CMS solutions in the market, you don’t need to lose your head when you have Squidex as a headless CMS. We understand that developers and content creators alike seek tools and platforms that offer efficiency, flexibility, accessibility and ease of use. That is where Squidex comes in with the right set of solutions that really help taper down your project handling juggles and deployment issues, we mean it.</p><p>Let’s take a dip together and understand how you can effortlessly integrate Squidex with your existing tech stack — this is for both front-end and back-end dev projects integration, you can adapt and migrate your desired projects as needed.</p><h4><strong>Understanding Squidex</strong></h4><p>Before diving into the integration process, it’s important for you to understand what makes Squidex stand out. When you opt for a headless CMS like Squidex, you <a href="https://squidex.io/features">get access to a diverse pool of tech features and integrations</a>. But, if we talk about specific core components of integrations, it offers:</p><ul><li><strong>Self-defined Schemas:</strong> Squidex allows you to define your own content structure, giving you the flexibility to tailor the CMS to your specific needs. No more stuck-ups!</li><li><strong>Powerful API:</strong> With API endpoints, you can connect your existing content programmatically, enabling dynamic content fetching and manipulation. Our API is built on high standards as of ‘OpenAPI’ and ‘OpenId Connect’ and can easily be absorbed by all programming languages. Easy peasy, no sweat!</li></ul><p>The beauty of Squidex lies in its headless nature (imagine the legend of Sleepy Hollow). You can do a lot with Squidex such as:</p><ol><li>Content Versioning</li><li>Seamless Integrations</li><li>Workflow System</li><li>Powerful APIs</li><li>GraphQL Endpoints</li><li>Easy Hosting</li><li>Fast Processing for High-End Performance</li><li>Easy to Use Administration Tools</li><li>Integrated Backup and Recovery Solutions</li></ol><p>With these tools in hand, Squidex gives you leverage for flexibility rather than completeness, allowing you to integrate Squidex into your existing tech stack without any hiccups.</p><h4><strong>Choosing the Right Tools for Integration</strong></h4><p>Squidex offers compatibility with a wide range of modern development tools and frameworks, including HTTP. Depending on your project requirements and needs, you can easily integrate Squidex with:</p><ul><li><strong>Jamstack sites</strong>: You can use static site generators like Gatsby, 11ty, and Next.js to create fast, scalable websites. Or if you already have the built ones you can use those to connect.</li><li><strong>JavaScript frameworks</strong>: On the other hand, you can leverage the power of frontend frameworks including React, Vue.js, Svelte, and Angular by connecting them to Squidex,</li></ul><p>Hence, the ultimate key to successful integration is selecting the right tools that align with your existing tech stack and project goals.</p><h4><strong>Integrating Squidex with Jamstack Sites</strong></h4><p>Integrating Squidex with Jamstack sites can significantly enhance your site’s performance and scalability.</p><h4><strong>Example: Integrating with Gatsby</strong></h4><p>Consider Gatsby as your test case. Here’s how you can easily integrate Squidex with Gatsby:</p><ol><li><strong>Set up your Squidex account</strong>: Create your schemas and add content.</li><li><strong>Install Gatsby and necessary plugins</strong>: Then, use the command line to install Gatsby and the (gatsby-source-graphql) plugin.</li><li><strong>Configure Gatsby</strong>: In your (gatsby-config.js) file, add the Squidex GraphQL endpoint and authentication details.</li><li><strong>Fetch data</strong>: To fetch data, you can use GraphQL queries to fetch content from Squidex and use it in your Gatsby components.</li></ol><p>You can set it up in minutes and can easily pull content dynamically from Squidex.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*NRXT0DfyBJWtOi9F" /></figure><p>You can find more details and copyable code <a href="https://www.gatsbyjs.com/plugins/gatsby-source-squidex/">here</a>.</p><h4><strong>Leveraging Squidex with JavaScript Frameworks</strong></h4><p>If you’re working on a web application using a JavaScript framework, Squidex can be your best friend, helping you integrate and enhance your development process even if you mess up in between.</p><h4><strong>Example: Integrating with React</strong></h4><p>Here’s how you can integrate Squidex with a React application (without reacting much):</p><ol><li><strong>Set up your Squidex account</strong>: The first step is going to be the same, as briefed before, define your content schemas and add content.</li><li><strong>Squidex SDK</strong>: You can use Squidex SDK library to handle the API requests.</li><li><strong>Fetch data from Squidex</strong>: Using Squidex SDK you can easily send requests to the Squidex API and retrieve content in real-time.</li><li><strong>Display content</strong>: Once done, you can utilize React components to display the fetched content in your application</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*d1ke2FEIpv1B9_5j" /></figure><pre>class Foo {<br>}</pre><p>This approach would allow you to leverage React’s component-based architecture while simultaneously managing your content centrally with Squidex. Check our detailed <a href="https://docs.squidex.io/id-01-getting-started/quick-start-guides/react.js-blog-with-squidex#running-the-code-locally">documentation</a> for comprehensive details.</p><h4><strong>Optimizing for Flexibility and Scalability</strong></h4><p>Nobody vouches for rigidness! And that’s why Squidex offers flexibility. Unlike traditional CMS solutions that may lock you into specific technologies, Squidex allows you to maintain your existing tech stack and infrastructure. How does this flexibility make your life easier?</p><ul><li><strong>If you are a developer</strong>: With Squidex you can choose the best available tools and frameworks for your project without being constrained by the traditional CMS.</li><li><strong>If you are a content creator</strong>: You can manage and deliver content across multiple channels without worrying about the underlying technologies, Squidex takes care of it all.</li></ul><p>So, you’re not just optimizing for flexibility but also for scalability. As your project grows, Squidex can easily scale to meet increasing demands, ensuring consistent performance and reliability.</p><h4><strong>Conclusion: Embrace the Freedom with Squidex</strong></h4><p>Integrating Squidex into your tech stack doesn’t have to be a daunting task. With its headless architecture and robust API, it provides the freedom to define your schemas, choose your tools, and deliver content across multiple platforms. Whether you’re building a static site with Gatsby or a dynamic web app with React, Squidex seamlessly fits into your workflow, allowing you to focus on creating and delivering exceptional content without worrying about the underlying technicalities.</p><p>So, why reinvent the wheel when you can seamlessly integrate Squidex and take your digital experiences to the next level?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e65c953fb39c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/squidex/seamlessly-integrate-squidex-into-your-tech-stack-without-reinventing-the-wheel-e65c953fb39c">Seamlessly Integrate Squidex into Your Tech Stack Without Reinventing the Wheel!</a> was originally published in <a href="https://medium.com/squidex">Squidex</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Seamlessly Integrate Squidex into Your Tech Stack Without Reinventing the Wheel]]></title>
            <link>https://medium.com/squidex/seamlessly-integrate-squidex-into-your-tech-stack-without-reinventing-the-wheel-84bc667625fa?source=rss-179bebbb4a5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/84bc667625fa</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[headless-cms]]></category>
            <dc:creator><![CDATA[Sebastian Stehle]]></dc:creator>
            <pubDate>Wed, 03 Jul 2024 10:26:52 GMT</pubDate>
            <atom:updated>2024-07-03T10:26:52.057Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s face it starting from scratch with a new CMS can be a daunting task. Migrating content, rebuilding functionality, and rewriting integrations can quickly turn into a developer’s nightmare. But what if you could leverage the power of Squidex, a headless CMS known for its flexibility and scalability, without throwing out your entire tech stack?</p><h4><strong>What exactly is a Headless CMS?</strong></h4><p>A headless CMS is a content management system that decouples the content repository (“body”) from the presentation layer (“head”). Unlike traditional CMS solutions that tightly integrate content creation and delivery, a headless CMS provides an API to deliver content to any frontend or device. This allows developers to use any technology stack to design and implement the user interface, enabling greater flexibility and scalability. Content creators can manage and update content in the backend, while developers can independently build and optimize the frontend experience for websites, mobile apps, IoT devices, and more.</p><h4><strong>Advantages of Headless CMS</strong></h4><p>A headless CMS comes with a wide range of advantages including:</p><ol><li><strong>Flexibility:</strong> Integrates with any frontend technology or framework.</li><li><strong>Scalability:</strong> Easily handles growing content and traffic demands.</li><li><strong>Performance:</strong> Optimized content delivery via APIs improves load times.</li><li><strong>Security:</strong> Separates content management from the presentation layer, enhancing security.</li><li><strong>Omnichannel Delivery:</strong> Publishes content to multiple platforms from a single source.</li><li><strong>Developer Freedom:</strong> Allows developers to choose their preferred tools and technologies.</li><li><strong>Future-Proof:</strong> Adapts to new technologies and platforms without extensive rework.</li><li><strong>Streamlined Workflows:</strong> Separates content creation from frontend development for parallel workflows.</li><li><strong>Enhanced Customization:</strong> Tailors frontend experiences without CMS constraints.</li><li><strong>Faster Development:</strong> Accelerates project timelines by decoupling frontend and backend tasks.</li></ol><p>And with so many conventional CMS solutions in the market, you don’t need to lose your head when you have Squidex as a headless CMS. We understand that developers and content creators alike seek tools and platforms that offer efficiency, flexibility, accessibility and ease of use. That is where Squidex comes in with the right set of solutions that really help taper down your project handling juggles and deployment issues, we mean it.</p><p>Let’s take a dip together and understand how you can effortlessly integrate Squidex with your existing tech stack — this is for both front-end and back-end dev projects integration, you can adapt and migrate your desired projects as needed.</p><h4><strong>Understanding Squidex</strong></h4><p>Before diving into the integration process, it’s important for you to understand what makes Squidex stand out. When you opt for a headless CMS like Squidex, you <a href="https://squidex.io/features">get access to a diverse pool of tech features and integrations</a>. But, if we talk about specific core components of integrations, it offers:</p><ul><li><strong>Self-defined Schemas:</strong> Squidex allows you to define your own content structure, giving you the flexibility to tailor the CMS to your specific needs. No more stuck-ups!</li><li><strong>Powerful API:</strong> With API endpoints, you can connect your existing content programmatically, enabling dynamic content fetching and manipulation. Our API is built on high standards as of ‘OpenAPI’ and ‘OpenId Connect’ and can easily be absorbed by all programming languages. Easy peasy, no sweat!</li></ul><p>The beauty of Squidex lies in its headless nature (imagine the legend of Sleepy Hollow). You can do a lot with Squidex such as:</p><ol><li>Content Versioning</li><li>Seamless Integrations</li><li>Workflow System</li><li>Powerful APIs</li><li>GraphQL Endpoints</li><li>Easy Hosting</li><li>Fast Processing for High-End Performance</li><li>Easy to Use Administration Tools</li><li>Integrated Backup and Recovery Solutions</li></ol><p>With these tools in hand, Squidex gives you leverage for flexibility rather than completeness, allowing you to integrate Squidex into your existing tech stack without any hiccups.</p><h4><strong>Choosing the Right Tools for Integration</strong></h4><p>Squidex offers compatibility with a wide range of modern development tools and frameworks, including HTTP. Depending on your project requirements and needs, you can easily integrate Squidex with:</p><ul><li><strong>Jamstack sites</strong>: You can use static site generators like Gatsby, 11ty, and Next.js to create fast, scalable websites. Or if you already have the built ones you can use those to connect.</li><li><strong>JavaScript frameworks</strong>: On the other hand, you can leverage the power of frontend frameworks including React, Vue.js, Svelte, and Angular by connecting them to Squidex,</li></ul><p>Hence, the ultimate key to successful integration is selecting the right tools that align with your existing tech stack and project goals.</p><h4><strong>Integrating Squidex with Jamstack Sites</strong></h4><p>Integrating Squidex with Jamstack sites can significantly enhance your site’s performance and scalability.</p><h4><strong>Example: Integrating with Gatsby</strong></h4><p>Consider Gatsby as your test case. Here’s how you can easily integrate Squidex with Gatsby:</p><ol><li><strong>Set up your Squidex account</strong>: Create your schemas and add content.</li><li><strong>Install Gatsby and necessary plugins</strong>: Then, use the command line to install Gatsby and the (gatsby-source-graphql) plugin.</li><li><strong>Configure Gatsby</strong>: In your (gatsby-config.js) file, add the Squidex GraphQL endpoint and authentication details.</li><li><strong>Fetch data</strong>: To fetch data, you can use GraphQL queries to fetch content from Squidex and use it in your Gatsby components.</li></ol><p>You can set it up in minutes and can easily pull content dynamically from Squidex.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*ZAVlUfExPVtWNxT9" /></figure><p>You can find more details and copyable code <a href="https://www.gatsbyjs.com/plugins/gatsby-source-squidex/">here</a>.</p><h4><strong>Leveraging Squidex with JavaScript Frameworks</strong></h4><p>If you’re working on a web application using a JavaScript framework, Squidex can be your best friend, helping you integrate and enhance your development process even if you mess up in between.</p><h4><strong>Example: Integrating with React</strong></h4><p>Here’s how you can integrate Squidex with a React application (without reacting much):</p><ol><li><strong>Set up your Squidex account</strong>: The first step is going to be the same, as briefed before, define your content schemas and add content.</li><li><strong>Squidex SDK</strong>: You can use Squidex SDK library to handle the API requests.</li><li><strong>Fetch data from Squidex</strong>: Using Squidex SDK you can easily send requests to the Squidex API and retrieve content in real-time.</li><li><strong>Display content</strong>: Once done, you can utilize React components to display the fetched content in your application</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*iudLOL5aCnpfBhj-" /></figure><p>This approach would allow you to leverage React’s component-based architecture while simultaneously managing your content centrally with Squidex. Check our detailed <a href="https://docs.squidex.io/id-01-getting-started/quick-start-guides/react.js-blog-with-squidex#running-the-code-locally">documentation</a> for comprehensive details.</p><h4><strong>Optimizing for Flexibility and Scalability</strong></h4><p>Nobody vouches for rigidness! And that’s why Squidex offers flexibility. Unlike traditional CMS solutions that may lock you into specific technologies, Squidex allows you to maintain your existing tech stack and infrastructure. How does this flexibility make your life easier?</p><ul><li><strong>If you are a developer</strong>: With Squidex you can choose the best available tools and frameworks for your project without being constrained by the traditional CMS.</li><li><strong>If you are a content creator</strong>: You can manage and deliver content across multiple channels without worrying about the underlying technologies, Squidex takes care of it all.</li></ul><p>So, you’re not just optimizing for flexibility but also for scalability. As your project grows, Squidex can easily scale to meet increasing demands, ensuring consistent performance and reliability.</p><h4><strong>Conclusion: Embrace the Freedom with Squidex</strong></h4><p>Integrating Squidex into your tech stack doesn’t have to be a daunting task. With its headless architecture and robust API, it provides the freedom to define your schemas, choose your tools, and deliver content across multiple platforms. Whether you’re building a static site with Gatsby or a dynamic web app with React, Squidex seamlessly fits into your workflow, allowing you to focus on creating and delivering exceptional content without worrying about the underlying technicalities.</p><p>So, why reinvent the wheel when you can seamlessly integrate Squidex and take your digital experiences to the next level?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84bc667625fa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/squidex/seamlessly-integrate-squidex-into-your-tech-stack-without-reinventing-the-wheel-84bc667625fa">Seamlessly Integrate Squidex into Your Tech Stack Without Reinventing the Wheel</a> was originally published in <a href="https://medium.com/squidex">Squidex</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Markdown and Richtext Editor]]></title>
            <link>https://medium.com/squidex/new-markdown-and-richtext-editor-ce3ec994baf8?source=rss-179bebbb4a5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce3ec994baf8</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[headless-cms]]></category>
            <dc:creator><![CDATA[Sebastian Stehle]]></dc:creator>
            <pubDate>Wed, 25 Oct 2023 09:21:16 GMT</pubDate>
            <atom:updated>2023-10-25T09:21:16.220Z</atom:updated>
            <content:encoded><![CDATA[<p>New editor for markdown and rich text has been released. Sets the foundation for new collaborative features coming soon.</p><p>We are happy to announce the new content editor.</p><figure><img alt="editor" src="https://cdn-images-1.medium.com/max/1024/0*wUjXnywuCrKVCZvn.png" /></figure><p>It will replace the existing editors for markdown and rich text and is based on the amazing <a href="https://remirror.io/https://remirror.io/">remirror</a> framework to provide a customized solution. There are several reasons for this editor:</p><ol><li>The current markdown editor was great for developers, because we are used to write markdown for our documentation and readme files. But have heard many times that content editors don’t need to see the syntax and just want to have a normal editor. The current solution offers just that, but depending on your feedback we might add a developer view where you can use the normal markdown syntax.</li><li>With the previous editors it was not possible the make all requested customization and to implement your feature requests. The markdown editor was also not maintained anymore and it was difficult to build features on top of that. Therefore it was time for a new solution.</li><li>We are planning to improve the collaborative experience with Squidex. For example better comments, annotations and live collaboration where many content writes can work on the same content item. This is very complex feature and impossible to build from scratch. Therefore we need support from the editor to make this possible. The current editor provides a very good integration to YJS which be will be the foundation for these features.</li></ol><p>With every release things can go wrong and sometimes new features are not well received. Therefore the old editors are sill available as <a href="https://docs.squidex.io/02-documentation/developer-guides/editors">custom editors</a>.</p><ul><li>The old markdown editor is available here: <a href="https://github.com/Squidex/squidex-samples/tree/master/editors/markdown">Source Code</a></li><li>The old rich text editor is available here: <a href="https://github.com/Squidex/squidex-samples/tree/master/editors/richtext">Source Code</a></li></ul><p>Just follow the instructions to build the editor and upload the files to your web server. These projects can also be the foundation for your customizations. We hope that you like the new editor. Please test it out and provide your feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce3ec994baf8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/squidex/new-markdown-and-richtext-editor-ce3ec994baf8">New Markdown and Richtext Editor</a> was originally published in <a href="https://medium.com/squidex">Squidex</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking the Power of Advanced Customization and Integration with Squidex]]></title>
            <link>https://medium.com/squidex/unlocking-the-power-of-advanced-customization-and-integration-with-squidex-5603a3315827?source=rss-179bebbb4a5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/5603a3315827</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[headless-cms]]></category>
            <dc:creator><![CDATA[Sebastian Stehle]]></dc:creator>
            <pubDate>Tue, 25 Jul 2023 06:50:10 GMT</pubDate>
            <atom:updated>2023-07-25T06:50:10.377Z</atom:updated>
            <content:encoded><![CDATA[<p>Unlocking the Power of Advanced Customization and Integration with Squidex …</p><h3>Introduction</h3><p>In today’s digital context, organizations endeavor to provide audiences with engaging and customized experiences. Content is crucial to attaining this objective, and <a href="https://squidex.io/">Squidex</a>, a feature-rich headless CMS, is a game-changer in advanced customization and integration. With Squidex, businesses can take charge of their content workflows, customize their systems to meet specific needs, and easily integrate with other applications and platforms.</p><p>In this article, we will delve into the world of Squidex and its advanced customization and integration capabilities. Squidex provides many tools and features to empower organizations on their content management voyage, including the ability to customize workflows and extend functionality via plugins and APIs. By leveraging Squidex’s capabilities, businesses can elevate their content strategies, deliver personalized experiences, and remain competitive in the digital landscape. Join us as we explore the potential of Squidex’s advanced customization and integration features.</p><p><strong>Understanding Squidex: A Brief Overview</strong></p><p>Let’s begin with a concise overview of Squidex before we delve into its advanced features. Squidex is a robust, adaptable, and open-source headless content management system (CMS) that enables enterprises to create, manage, and deliver content across multiple channels and platforms. Unlike conventional CMS solutions, Squidex takes a headless approach, separating the content administration backend from the presentation layer. This decoupling enables organizations to deliver content to multiple endpoints, such as websites, mobile applications, and IoT devices, ensuring consistent experiences across channels. Squidex, at its essence, provides a robust and user-friendly interface for content creation and management. It offers a variety of content categories, such as structured data, media assets, and localization support, enabling businesses to manage diverse content needs. With Squidex, content authors and editors can seamlessly collaborate, streamline their operations, and guarantee content accuracy and consistency. In addition, Squidex offers extensive customization options to customize the CMS to the unique requirements of each business. From defining custom content schemas and fields to creating complex procedures and permissions, Squidex provides flexibility and control over content structures and processes. This enables organizations to create content models that correspond with their specific needs, ensuring efficient content creation and management. In addition, Squidex’s robust APIs and webhooks facilitate integration with various third-party systems and services. This integration capability enables companies to leverage existing tools and platforms, such as marketing automation systems, analytics solutions, and e-commerce platforms, to improve their content strategies and deliver personalized experiences.</p><p><strong>Customizing Workflows for Enhanced Efficiency</strong></p><figure><img alt="Custom Workflow" src="https://cdn-images-1.medium.com/max/479/0*mvZSlo0oOy2wo3RY.png" /></figure><p>One of Squidex’s distinct features is its ability to create workflows, which enables businesses to accelerate the procedures involved in content development, approval, and publication. Companies may build and enforce complicated content approval processes with the help of Squidex’s workflow management features, ensuring that content gets through the proper steps before publication. Teams can collaborate easily, uphold consistency, and adhere to compliance regulations because of this level of customization. Role-based permissions, status monitoring, and scripting capabilities are some of Squidex’s process customization features. Organizations can assign team members specific duties and manage their access to various content activities by establishing roles and permissions. To meet the specific needs of each company, status management enables the development of custom content lifecycles phases, such as draft, review, approval, and publication. Squidex’s scripting tools provide versatility when implementing complicated business rules and validations. Organizations can use scripts to establish conditions and actions based on particular occurrences, including creating new material or status changes. This makes it possible to apply unique restrictions and guarantees that the material complies with predetermined rules.</p><p><strong>Custom Editors: Enhancing Content Creation and Management</strong></p><figure><img alt="CustomeEditors" src="https://cdn-images-1.medium.com/max/1024/0*gpHEgrcRMtJ-IR-L.jpg" /></figure><p>Custom Editors are a robust Squidex feature that enables organizations to create customized content creation and administration experiences. With Custom Editors, organizations can design specialized interfaces and protocols corresponding to their specific content requirements and editorial procedures.</p><p>Automating Content Creation:</p><p>Custom Editors enable businesses to design user-friendly and intuitive interfaces for content authors and editors. Organizations can expedite the content creation process by customizing the content entry forms with specific fields, validations, and user interface elements and ensure that authors provide accurate and structured content.</p><p>Advanced-Data Input:</p><p>Custom Editors allow businesses to construct custom field types to accommodate complex data structures. This will enable organizations to capture and manage content elements such as maps, infographics, video embeds, and social media integrations.</p><p>Validation and Error Handling:</p><p>Custom Editors allow businesses to implement individualized validation criteria and error-handling techniques. By defining unique validation standards for fields, businesses can ensure that content creators provide valid and reliable data, thereby reducing errors and enhancing the quality of their content.</p><p>Improved User Experience:</p><p>Organizations can enhance the user experience with Custom Editors by designing interfaces that adhere to their brand guidelines and provide a seamless and intuitive content management experience. Customizing the interface’s appearance for modifying content can increase user engagement and productivity. Custom Editors in Squidex enable businesses to construct content creation and management experiences tailored to their specific requirements, resulting in increased productivity, content quality, and user satisfaction.</p><p>**Extending Functionality with Custom Sidebars **</p><p>Squidex exceeds the capabilities of standard CMSs by enabling developers to extend its functionality with custom sidebars. Sidebars are user interface (UI) extensions attached to individual content items or lists to provide additional functionality and improve the editing experience. By writing custom sidebar plugins, developers can add new UI elements, integrate third-party services, or provide specialized functionality tailored to the requirements of their organization. For instance, an Algolia-powered search feature could be integrated into a custom sidebar plugin, allowing content editors to search and link related content effortlessly. Custom sidebars in Squidex utilize sandboxed iframes and communicate with the primary application via an SDK to maintain security and ensure the separation of concerns. This extensibility enables organizations to tailor the authoring experience, enhancing productivity and simplifying content management duties.</p><p><strong>Seamless Integration with External Systems</strong></p><p>Squidex excels at providing seamless connectivity with external systems, a crucial component of any CMS. Whether it’s a marketing automation platform, an e-commerce solution, or a customer relationship management (CRM) application, Squidex’s extensive integration capabilities allow businesses to leverage their existing systems and establish a unified ecosystem. Users can synchronize data with external systems using several integration mechanisms supported by Squidex. Squidex offers connections with well-known messaging systems like Kafka, RabbitMQ, and Azure Queue. You may publish content to third-party platforms, update data in real time, or guarantee high availability by maintaining copies of your content. These connectors provide effective content transmission and enable seamless system-to-system communication, ensuring data synchronization and consistency. Powerful search engines like Algolia, Elastic Search, Open Search, and Typesense are effortlessly integrated with Squidex to improve search capabilities. You may use cutting-edge search functionality and offer users quick and precise search results by submitting your content to these search engines. Additionally, Squidex provides social media platform connections with Discourse, Medium, and Twitter. You may publish blog posts, create topics or posts, make blog articles, and share information across numerous platforms due to these integrations, which will increase your audience and simplify the process of content distribution. Custom webhooks give Squidex countless options for integrating with external systems. You can define particular endpoints to get real-time notifications for content changes or specific events, which will start bespoke workflows or actions in external systems. Thanks to its versatility, you can modify the integration to meet your specific needs. Squidex works with Prerender and Fastly, two web development tools, to improve website performance and speed up content delivery. The user experience and website visibility are improved by Squidex’s rendering of JavaScript-based webpages for search engine crawlers and maintenance of cached renderings.</p><p><strong>Conclusion</strong></p><p>Advanced customization and seamless integration are at the core of Squidex’s value proposition, allowing organizations to customize their content workflows, extend functionality, and integrate with external systems without complications. By leveraging Squidex’s customization capabilities, businesses can construct efficient and individualized content workflows that ensure content quality and consistency. The ability to write custom sidebar extensions enables developers to improve the content editing experience and implement specialized features. In addition, the seamless integration capabilities of Squidex would allow organizations to leverage their existing systems and create a unified content ecosystem. In conclusion, Squidex is a robust and adaptable headless CMS that offers advanced customization and integration options to meet the diverse requirements of contemporary businesses. By adopting Squidex and its vast array of capabilities, companies can realize the full potential of their content management strategies and deliver exceptional digital experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5603a3315827" width="1" height="1" alt=""><hr><p><a href="https://medium.com/squidex/unlocking-the-power-of-advanced-customization-and-integration-with-squidex-5603a3315827">Unlocking the Power of Advanced Customization and Integration with Squidex</a> was originally published in <a href="https://medium.com/squidex">Squidex</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking the Power of Advanced Customization and Integration with Squidex]]></title>
            <link>https://medium.com/squidex/unlocking-the-power-of-advanced-customization-and-integration-with-squidex-f2186c29f059?source=rss-179bebbb4a5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2186c29f059</guid>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Sebastian Stehle]]></dc:creator>
            <pubDate>Tue, 04 Jul 2023 12:07:48 GMT</pubDate>
            <atom:updated>2023-07-04T12:07:48.820Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction</strong></p><p>In today’s digital context, organizations endeavor to provide audiences with engaging and customized experiences. Content is crucial to attaining this objective, and <a href="https://squidex.io/">Squidex</a>, a feature-rich headless CMS, is a game-changer in advanced customization and integration. With Squidex, businesses can take charge of their content workflows, customize their systems to meet specific needs, and easily integrate with other applications and platforms. In this article, we will delve into the world of Squidex and its advanced customization and integration capabilities. Squidex provides many tools and features to empower organizations on their content management voyage, including the ability to customize workflows and extend functionality via plugins and APIs. By leveraging Squidex’s capabilities, businesses can elevate their content strategies, deliver personalized experiences, and remain competitive in the digital landscape. Join us as we explore the potential of Squidex’s advanced customization and integration features.</p><p>**Understanding Squidex: A Brief Overview **</p><p>Let’s begin with a concise overview of Squidex before we delve into its advanced features. Squidex is a robust, adaptable, and open-source headless content management system (CMS) that enables enterprises to create, manage, and deliver content across multiple channels and platforms. Unlike conventional CMS solutions, Squidex takes a headless approach, separating the content administration backend from the presentation layer. This decoupling enables organizations to deliver content to multiple endpoints, such as websites, mobile applications, and IoT devices, ensuring consistent experiences across channels. Squidex, at its essence, provides a robust and user-friendly interface for content creation and management. It offers a variety of content categories, such as structured data, media assets, and localization support, enabling businesses to manage diverse content needs. With Squidex, content authors and editors can seamlessly collaborate, streamline their operations, and guarantee content accuracy and consistency. In addition, Squidex offers extensive customization options to customize the CMS to the unique requirements of each business. From defining custom content schemas and fields to creating complex procedures and permissions, Squidex provides flexibility and control over content structures and processes. This enables organizations to create content models that correspond with their specific needs, ensuring efficient content creation and management. In addition, Squidex’s robust APIs and webhooks facilitate integration with various third-party systems and services. This integration capability enables companies to leverage existing tools and platforms, such as marketing automation systems, analytics solutions, and e-commerce platforms, to improve their content strategies and deliver personalized experiences.</p><p><strong>Customizing Workflows for Enhanced Efficiency</strong></p><figure><img alt="Custom Workflow" src="https://cdn-images-1.medium.com/max/479/0*s5XEtEu-EXoBznho.png" /></figure><p>One of Squidex’s distinct features is its ability to create workflows, which enables businesses to accelerate the procedures involved in content development, approval, and publication. Companies may build and enforce complicated content approval processes with the help of Squidex’s workflow management features, ensuring that content gets through the proper steps before publication. Teams can collaborate easily, uphold consistency, and adhere to compliance regulations because of this level of customization. Role-based permissions, status monitoring, and scripting capabilities are some of Squidex’s process customization features. Organizations can assign team members specific duties and manage their access to various content activities by establishing roles and permissions. To meet the specific needs of each company, status management enables the development of custom content lifecycles phases, such as draft, review, approval, and publication. Squidex’s scripting tools provide versatility when implementing complicated business rules and validations. Organizations can use scripts to establish conditions and actions based on particular occurrences, including creating new material or status changes. This makes it possible to apply unique restrictions and guarantees that the material complies with predetermined rules.</p><p><strong>Custom Editors: Enhancing Content Creation and Management</strong></p><figure><img alt="CustomeEditors" src="https://cdn-images-1.medium.com/max/1024/0*phPTIP2QeIlHNLJq.jpg" /></figure><p>Custom Editors are a robust Squidex feature that enables organizations to create customized content creation and administration experiences. With Custom Editors, organizations can design specialized interfaces and protocols corresponding to their specific content requirements and editorial procedures.</p><p>Automating Content Creation:</p><p>Custom Editors enable businesses to design user-friendly and intuitive interfaces for content authors and editors. Organizations can expedite the content creation process by customizing the content entry forms with specific fields, validations, and user interface elements and ensure that authors provide accurate and structured content.</p><p>Advanced-Data Input:</p><p>Custom Editors allow businesses to construct custom field types to accommodate complex data structures. This will enable organizations to capture and manage content elements such as maps, infographics, video embeds, and social media integrations.</p><p>Validation and Error Handling:</p><p>Custom Editors allow businesses to implement individualized validation criteria and error-handling techniques. By defining unique validation standards for fields, businesses can ensure that content creators provide valid and reliable data, thereby reducing errors and enhancing the quality of their content.</p><p>Improved User Experience:</p><p>Organizations can enhance the user experience with Custom Editors by designing interfaces that adhere to their brand guidelines and provide a seamless and intuitive content management experience. Customizing the interface’s appearance for modifying content can increase user engagement and productivity. Custom Editors in Squidex enable businesses to construct content creation and management experiences tailored to their specific requirements, resulting in increased productivity, content quality, and user satisfaction.</p><p>**Extending Functionality with Custom Sidebars **</p><p>Squidex exceeds the capabilities of standard CMSs by enabling developers to extend its functionality with custom sidebars. Sidebars are user interface (UI) extensions attached to individual content items or lists to provide additional functionality and improve the editing experience. By writing custom sidebar plugins, developers can add new UI elements, integrate third-party services, or provide specialized functionality tailored to the requirements of their organization. For instance, an Algolia-powered search feature could be integrated into a custom sidebar plugin, allowing content editors to search and link related content effortlessly. Custom sidebars in Squidex utilize sandboxed iframes and communicate with the primary application via an SDK to maintain security and ensure the separation of concerns. This extensibility enables organizations to tailor the authoring experience, enhancing productivity and simplifying content management duties.</p><p><strong>Seamless Integration with External Systems</strong></p><p>Squidex excels at providing seamless connectivity with external systems, a crucial component of any CMS. Whether it’s a marketing automation platform, an e-commerce solution, or a customer relationship management (CRM) application, Squidex’s extensive integration capabilities allow businesses to leverage their existing systems and establish a unified ecosystem. Users can synchronize data with external systems using several integration mechanisms supported by Squidex. Squidex offers connections with well-known messaging systems like Kafka, RabbitMQ, and Azure Queue. You may publish content to third-party platforms, update data in real time, or guarantee high availability by maintaining copies of your content. These connectors provide effective content transmission and enable seamless system-to-system communication, ensuring data synchronization and consistency. Powerful search engines like Algolia, Elastic Search, Open Search, and Typesense are effortlessly integrated with Squidex to improve search capabilities. You may use cutting-edge search functionality and offer users quick and precise search results by submitting your content to these search engines. Additionally, Squidex provides social media platform connections with Discourse, Medium, and Twitter. You may publish blog posts, create topics or posts, make blog articles, and share information across numerous platforms due to these integrations, which will increase your audience and simplify the process of content distribution. Custom webhooks give Squidex countless options for integrating with external systems. You can define particular endpoints to get real-time notifications for content changes or specific events, which will start bespoke workflows or actions in external systems. Thanks to its versatility, you can modify the integration to meet your specific needs. Squidex works with Prerender and Fastly, two web development tools, to improve website performance and speed up content delivery. The user experience and website visibility are improved by Squidex’s rendering of JavaScript-based webpages for search engine crawlers and maintenance of cached renderings.</p><p><strong>Conclusion</strong></p><p>Advanced customization and seamless integration are at the core of Squidex’s value proposition, allowing organizations to customize their content workflows, extend functionality, and integrate with external systems without complications. By leveraging Squidex’s customization capabilities, businesses can construct efficient and individualized content workflows that ensure content quality and consistency. The ability to write custom sidebar extensions enables developers to improve the content editing experience and implement specialized features. In addition, the seamless integration capabilities of Squidex would allow organizations to leverage their existing systems and create a unified content ecosystem. In conclusion, Squidex is a robust and adaptable headless CMS that offers advanced customization and integration options to meet the diverse requirements of contemporary businesses. By adopting Squidex and its vast array of capabilities, companies can realize the full potential of their content management strategies and deliver exceptional digital experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2186c29f059" width="1" height="1" alt=""><hr><p><a href="https://medium.com/squidex/unlocking-the-power-of-advanced-customization-and-integration-with-squidex-f2186c29f059">Unlocking the Power of Advanced Customization and Integration with Squidex</a> was originally published in <a href="https://medium.com/squidex">Squidex</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking the Power of Advanced Customization and Integration with Squidex]]></title>
            <link>https://medium.com/squidex/unlocking-the-power-of-advanced-customization-and-integration-with-squidex-454938f767e8?source=rss-179bebbb4a5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/454938f767e8</guid>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Sebastian Stehle]]></dc:creator>
            <pubDate>Tue, 04 Jul 2023 12:06:09 GMT</pubDate>
            <atom:updated>2023-07-04T12:06:09.104Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction</strong></p><p>In today’s digital context, organizations endeavor to provide audiences with engaging and customized experiences. Content is crucial to attaining this objective, and <a href="https://squidex.io/">Squidex</a>, a feature-rich headless CMS, is a game-changer in advanced customization and integration. With Squidex, businesses can take charge of their content workflows, customize their systems to meet specific needs, and easily integrate with other applications and platforms. In this article, we will delve into the world of Squidex and its advanced customization and integration capabilities. Squidex provides many tools and features to empower organizations on their content management voyage, including the ability to customize workflows and extend functionality via plugins and APIs. By leveraging Squidex’s capabilities, businesses can elevate their content strategies, deliver personalized experiences, and remain competitive in the digital landscape. Join us as we explore the potential of Squidex’s advanced customization and integration features.</p><p>**Understanding Squidex: A Brief Overview **</p><p>Let’s begin with a concise overview of Squidex before we delve into its advanced features. Squidex is a robust, adaptable, and open-source headless content management system (CMS) that enables enterprises to create, manage, and deliver content across multiple channels and platforms. Unlike conventional CMS solutions, Squidex takes a headless approach, separating the content administration backend from the presentation layer. This decoupling enables organizations to deliver content to multiple endpoints, such as websites, mobile applications, and IoT devices, ensuring consistent experiences across channels. Squidex, at its essence, provides a robust and user-friendly interface for content creation and management. It offers a variety of content categories, such as structured data, media assets, and localization support, enabling businesses to manage diverse content needs. With Squidex, content authors and editors can seamlessly collaborate, streamline their operations, and guarantee content accuracy and consistency. In addition, Squidex offers extensive customization options to customize the CMS to the unique requirements of each business. From defining custom content schemas and fields to creating complex procedures and permissions, Squidex provides flexibility and control over content structures and processes. This enables organizations to create content models that correspond with their specific needs, ensuring efficient content creation and management. In addition, Squidex’s robust APIs and webhooks facilitate integration with various third-party systems and services. This integration capability enables companies to leverage existing tools and platforms, such as marketing automation systems, analytics solutions, and e-commerce platforms, to improve their content strategies and deliver personalized experiences.</p><p><strong>Customizing Workflows for Enhanced Efficiency</strong></p><figure><img alt="Custom Workflow" src="https://cdn-images-1.medium.com/max/479/0*luCoRJL2NR01Pwvn.png" /></figure><p>One of Squidex’s distinct features is its ability to create workflows, which enables businesses to accelerate the procedures involved in content development, approval, and publication. Companies may build and enforce complicated content approval processes with the help of Squidex’s workflow management features, ensuring that content gets through the proper steps before publication. Teams can collaborate easily, uphold consistency, and adhere to compliance regulations because of this level of customization. Role-based permissions, status monitoring, and scripting capabilities are some of Squidex’s process customization features. Organizations can assign team members specific duties and manage their access to various content activities by establishing roles and permissions. To meet the specific needs of each company, status management enables the development of custom content lifecycles phases, such as draft, review, approval, and publication. Squidex’s scripting tools provide versatility when implementing complicated business rules and validations. Organizations can use scripts to establish conditions and actions based on particular occurrences, including creating new material or status changes. This makes it possible to apply unique restrictions and guarantees that the material complies with predetermined rules.</p><p><strong>Custom Editors: Enhancing Content Creation and Management</strong></p><figure><img alt="CustomeEditors" src="https://cdn-images-1.medium.com/max/1024/0*KDXVqTiu8753A8YV.jpg" /></figure><p>Custom Editors are a robust Squidex feature that enables organizations to create customized content creation and administration experiences. With Custom Editors, organizations can design specialized interfaces and protocols corresponding to their specific content requirements and editorial procedures.</p><p>Automating Content Creation:</p><p>Custom Editors enable businesses to design user-friendly and intuitive interfaces for content authors and editors. Organizations can expedite the content creation process by customizing the content entry forms with specific fields, validations, and user interface elements and ensure that authors provide accurate and structured content.</p><p>Advanced-Data Input:</p><p>Custom Editors allow businesses to construct custom field types to accommodate complex data structures. This will enable organizations to capture and manage content elements such as maps, infographics, video embeds, and social media integrations.</p><p>Validation and Error Handling:</p><p>Custom Editors allow businesses to implement individualized validation criteria and error-handling techniques. By defining unique validation standards for fields, businesses can ensure that content creators provide valid and reliable data, thereby reducing errors and enhancing the quality of their content.</p><p>Improved User Experience:</p><p>Organizations can enhance the user experience with Custom Editors by designing interfaces that adhere to their brand guidelines and provide a seamless and intuitive content management experience. Customizing the interface’s appearance for modifying content can increase user engagement and productivity. Custom Editors in Squidex enable businesses to construct content creation and management experiences tailored to their specific requirements, resulting in increased productivity, content quality, and user satisfaction.</p><p>**Extending Functionality with Custom Sidebars **</p><p>Squidex exceeds the capabilities of standard CMSs by enabling developers to extend its functionality with custom sidebars. Sidebars are user interface (UI) extensions attached to individual content items or lists to provide additional functionality and improve the editing experience. By writing custom sidebar plugins, developers can add new UI elements, integrate third-party services, or provide specialized functionality tailored to the requirements of their organization. For instance, an Algolia-powered search feature could be integrated into a custom sidebar plugin, allowing content editors to search and link related content effortlessly. Custom sidebars in Squidex utilize sandboxed iframes and communicate with the primary application via an SDK to maintain security and ensure the separation of concerns. This extensibility enables organizations to tailor the authoring experience, enhancing productivity and simplifying content management duties.</p><p><strong>Seamless Integration with External Systems</strong></p><p>Squidex excels at providing seamless connectivity with external systems, a crucial component of any CMS. Whether it’s a marketing automation platform, an e-commerce solution, or a customer relationship management (CRM) application, Squidex’s extensive integration capabilities allow businesses to leverage their existing systems and establish a unified ecosystem. Users can synchronize data with external systems using several integration mechanisms supported by Squidex. Squidex offers connections with well-known messaging systems like Kafka, RabbitMQ, and Azure Queue. You may publish content to third-party platforms, update data in real time, or guarantee high availability by maintaining copies of your content. These connectors provide effective content transmission and enable seamless system-to-system communication, ensuring data synchronization and consistency. Powerful search engines like Algolia, Elastic Search, Open Search, and Typesense are effortlessly integrated with Squidex to improve search capabilities. You may use cutting-edge search functionality and offer users quick and precise search results by submitting your content to these search engines. Additionally, Squidex provides social media platform connections with Discourse, Medium, and Twitter. You may publish blog posts, create topics or posts, make blog articles, and share information across numerous platforms due to these integrations, which will increase your audience and simplify the process of content distribution. Custom webhooks give Squidex countless options for integrating with external systems. You can define particular endpoints to get real-time notifications for content changes or specific events, which will start bespoke workflows or actions in external systems. Thanks to its versatility, you can modify the integration to meet your specific needs. Squidex works with Prerender and Fastly, two web development tools, to improve website performance and speed up content delivery. The user experience and website visibility are improved by Squidex’s rendering of JavaScript-based webpages for search engine crawlers and maintenance of cached renderings.</p><p><strong>Conclusion</strong></p><p>Advanced customization and seamless integration are at the core of Squidex’s value proposition, allowing organizations to customize their content workflows, extend functionality, and integrate with external systems without complications. By leveraging Squidex’s customization capabilities, businesses can construct efficient and individualized content workflows that ensure content quality and consistency. The ability to write custom sidebar extensions enables developers to improve the content editing experience and implement specialized features. In addition, the seamless integration capabilities of Squidex would allow organizations to leverage their existing systems and create a unified content ecosystem. In conclusion, Squidex is a robust and adaptable headless CMS that offers advanced customization and integration options to meet the diverse requirements of contemporary businesses. By adopting Squidex and its vast array of capabilities, companies can realize the full potential of their content management strategies and deliver exceptional digital experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=454938f767e8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/squidex/unlocking-the-power-of-advanced-customization-and-integration-with-squidex-454938f767e8">Unlocking the Power of Advanced Customization and Integration with Squidex</a> was originally published in <a href="https://medium.com/squidex">Squidex</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Squidex 7.1 Released: GraphQL Subscriptions and Translation Status]]></title>
            <link>https://medium.com/squidex/squidex-7-1-released-graphql-subscriptions-and-translation-status-e52386440a1a?source=rss-179bebbb4a5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e52386440a1a</guid>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Sebastian Stehle]]></dc:creator>
            <pubDate>Thu, 01 Sep 2022 14:26:30 GMT</pubDate>
            <atom:updated>2022-09-01T14:26:30.254Z</atom:updated>
            <content:encoded><![CDATA[<p>I am happy to share a couple of new and improved features and give you some guideline how to leverage them.</p><h3>TL;DR</h3><ul><li>GraphQL subscriptions have been made available in a first version. It is very helpful to improve the editorial experience.</li><li>To make translating content easier, the translation status of each content is now available in the Squidex content view.</li><li>As always: A few bugfixes and minor improvements.</li></ul><h3>GraphQL subscriptions</h3><p>GraphQL subscriptions are the highlight of this release and are available ina first version. Even GraphQL focused competitors do not support subscriptions yet (Yes, I am talking about you, GraphCMS / Hygraph), so I am very proud to talk about this feature today. This version has set the groundwork and technical infrastructure to improve this feature over time and I am waiting for your feedback.</p><p>With this version you can subscribe to all content changes or asset changes in a raw format, which means that you get all data at once and you cannot resolve references or assets at the moment. The focus was the technical infrastructure, which can be more complicated as you might think at the beginning.</p><h4>Technical Infrastructure</h4><p>If you have a single server it is very easy to implement subscriptions. Whenever somebody makes a change to a content you create an event (e.g. ContentUpdated) and you loop over all the open subscriptions and send the event to all matching subscriptions. But what happens when you have multiple servers? Then the change could happen on server A, but the subscription has been created on server C. So you need a way to send the event from server A to server C.</p><figure><img alt="Problem Description" src="https://cdn-images-1.medium.com/max/629/0*xPpBe07aNYPiujdh.png" /></figure><p>But how do you know, that you have to send the event to server C and not to server B? The answer is simple: Just send the event to all servers using a publish-subscribe (PubSub) implementation, for example Redis or Google PubSub. Then each server decides if the event matches to one of the subscriptions.</p><figure><img alt="PubSub Model" src="https://cdn-images-1.medium.com/max/786/0*jYkRWqIFqlj4COgJ.png" /></figure><p>This model can cause some issues. In Squidex thousands of events are created per minute and it is to be expected that only a fraction of these events is actually needed for a GraphQL subscriptions. I had a look to the most popular GraphQL implementation, Apollo, but they use a simple PubSub model as well: <a href="https://www.apollographql.com/docs/apollo-server/data/subscriptions/#the-pubsub-class.">https://www.apollographql.com/docs/apollo-server/data/subscriptions/#the-pubsub-class.</a> Usually events are not that big, so it can be acceptable to publish all events over PubSub, but if you have a lot of events you can have significant costs from the PubSub system and a CPU overhead to serialize and deserialize the events to a message that can be sent over the network. So I tried to find another solution.</p><p>The idea is to also publish subscriptions over PubSub. So when the user subscribes to server C the subscription is published to all other servers, which means that each subscription exists on all servers. Each subscription also has a unique ID. When server A creates a new event the local copy of the subscriptions are used to evaluate which subscriptions match to the event. If there is at least one subscription, the event is sent over PubSub to all events together with the IDs of the matching subscriptions. Then each servers tries to resolve the subscriptions that match to the IDs and send the event over the subscription to the user. This means that the decision, which subscriptions match to the event, is made by the server who also created the event, in our case server A. If no subscriptions is currently alive, no event is sent over PubSub and there is no costs for these events.</p><figure><img alt="Publishing Subscriptions" src="https://cdn-images-1.medium.com/max/885/0*UBQZ16tspaas80_a.png" /></figure><p>There are a few technical challenges with this model. For example it is difficult to remove subscriptions, because when server C crashes or is updated with a new version, the other servers might think that their copies of the subscriptions coming from server C are still valid. Therefore each server sends a message with a timestamp and the IDs of all local subscriptions over PubSub every 10 seconds. The other servers update all their matching copies with the received timestamp. If a subscription has not been updated for a longer time, it is considered to be dead and removed.</p><h4>Use Cases</h4><p>There are a wide range of Use Cases, but the most important one for me is to improve the editorial experience for content authors. You can subscribe to content updates in your frontend and automatically reload the page or a component, when an update has been received.</p><p>The hotels sample in React has been updated to support this use case. In this sample the graphql-ws package has been used: <a href="https://github.com/enisdenjo/graphql-ws.">https://github.com/enisdenjo/graphql-ws.</a></p><p>The following snipped shows a very simple approach. We just listen to all content changes and whenever there is a change, we reload the current page. Of course this is not the best implementation. It would make more sense to only update the components that renders at least one content item with an ID that matchs to the ID of the just received event. The hotels example provides a better solution for this problem.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/74f6d45d2ecf610e9269425b69695704/href">https://medium.com/media/74f6d45d2ecf610e9269425b69695704/href</a></iframe><h3>Translation Status</h3><p>When you have a lot of languages, usually not every content item has been translated to all languages. It is just a matter of time and priority. But very often the goal is to improve this over time. But so far it was not that easy to find the content items that need to be improved.</p><p>Therefore Squidex provides you the average translation status in the content list now and also the status of a single item in the content editor itself:</p><figure><img alt="Translation Status" src="https://cdn-images-1.medium.com/max/1024/0*5GOpRKygaLxshP9Z.png" /></figure><p>For each language we show the status in percent. 100% means that every field has been translated and 0% means, that no field has been translated so far.</p><p>You can also use the filter dialog to get content items with a low translation status:</p><figure><img alt="Filter for Translation Status" src="https://cdn-images-1.medium.com/max/1024/0*2XBSPx1YHQ_nnPN-.png" /></figure><p>This should make it much easier to work with localized content in Squidex.</p><h3>Outlook</h3><p>In the next weeks the focus will be on bugfixes and minor improvements. There are no concrete plans for bigger features yet but you can check out the trello board: <a href="https://trello.com/b/KakM4F3S/squidex-roadmap">https://trello.com/b/KakM4F3S/squidex-roadmap</a></p><p>If you want to discuss your requirements you can also schedule a call: <a href="https://calendly.com/squidex-meeting/30min?month=2022-09.">https://calendly.com/squidex-meeting/30min?month=2022-09.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e52386440a1a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/squidex/squidex-7-1-released-graphql-subscriptions-and-translation-status-e52386440a1a">Squidex 7.1 Released: GraphQL Subscriptions and Translation Status</a> was originally published in <a href="https://medium.com/squidex">Squidex</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>