Implementing Portable Text Fields in Sanity and Rendering Them in React
Define a Portable Text field in your Sanity schema, then render it safely in React with custom block serializers for text, marks, and images.
Loading…
ReadMeFeed / Community knowledge
#schema
Real questions. Useful conversations. Find the people who know your stack.
reactUsing XML Namespaces to Prevent Element Name Collisions
Learn how XML namespaces prevent element name collisions when combining vocabularies, with a concrete example, validation steps, and practical limitations.
Using SpiceDB Schema‑Defined Computed Permissions to Build Role‑Like Groupings
SpiceDB lets you build role‑like groupings with computed permissions—unions, intersections, and exclusions—directly in the schema. This article shows a working example, how to test it, and common pitfalls to avoid.
spicedbArchitecture Note: Using Sanity Portable Text as a Rich‑Text Field
Guide to defining, validating, and operating Portable Text in Sanity, covering requirements, minimal schema, trust boundaries, checks, failure modes and when to redesign.
sanityUsing Sanity Portable Text for Rich-Text Fields
Learn how to define a Portable Text field in Sanity, see a schema and JSON example, render it with a React serializer, and avoid common pitfalls.
AdonisJS v5 Validator: Declarative Request Validation with Schema and Custom Rules
Learn how to use AdonisJS v5's built-in Validator to define schemas, validate incoming requests, handle errors, and avoid common pitfalls.
adonisjsClojureScript schema evolution and LocalStorage rollback safety
ClojureScript applications often persist state via LocalStorage or IndexedDB using native maps or vectors. When a new deployment introduces a schema change to this persisted data and is subsequently rolled back to a previous build, the older code may encounter data structures with unexpected keys or modified nested types. While ClojureScript's dynamic nature
clojurescriptData file cache limits: schema changes ignored
Goal Understand how Hugo’s data file cache behaves when the schema of a data file changes without a file-modification timestamp change, and whether this limitation can be addressed. Constraints Hugo caches parsed YAML, JSON, and TOML files in resources/_gen . The cache key is built from the file path and its last-modified timestamp. If the internal structure
hugoGlobal vs. Per‑Route Serialization in Fastify: Which Approach Yields Better Performance for High‑Throughput APIs?
Goal We want to deliver a high‑throughput, read‑only API where the JSON response shape is stable across many requests. Constraints Minimize per‑request CPU spent on serialization. Keep startup time acceptable for rapid deployment cycles. Maintain flexibility to change response schemas without a full rebuild. Ensure that error responses and non‑JSON payloads
fastify