ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
ProcessWire models all content as Pages with reusable Fields, making relationships first-class and editable in the admin without custom tables. Selectors provide a readable query language that returns Page objects, trading raw SQL control for template readability and rapid iteration.
Decide when to use Sanity Portable Text instead of a plain string field for rich content, with schema, query, and rendering guidance.
Portable Text is structured data, not HTML. Learn how to define custom annotations in the Sanity schema and build a shared serializer library so every frontend renders internal links, embeds, and custom marks consistently — without silent data loss.
Learn how Sanity’s hotspot‑enabled image pipeline lets you shift cropping and responsive design decisions from code to content. A step‑by‑step guide covers schema setup, GROQ querying, and client‑side URL building, plus trade‑offs to watch out for.
Blog listings that fetch whole Sanity documents waste bandwidth and couple UI to unused fields. Use precise GROQ projections and parameterized named queries so pages fetch only what they render.
A decision guide for Jekyll content architecture comparing static pages, YAML data files, and collections, with trade-offs and implementation checks.
Decide between Sanity document references and Portable Text embeds for content relationships: a comparison table, trade-offs, schema code, and GROQ validation.
Portable Text lets you model rich content as typed blocks and transform it per channel with GROQ instead of rendering HTML everywhere. Use schema-defined custom blocks and serializer maps for portable, safe content.
GROQ projections let you shape Sanity query results server-side — flattening references, generating excerpts, and matching your component props exactly. Here's a worked example plus the trade-offs.
processwire
sanity
jekyll