@codestirring I think a hosted Phoenix Storybook is great for sharing components✨. Phx storybook displays visual examples, docs and the module code. For example https://t.co/p5OlQNtJBD
@Jamiewarb@sanity_io@mawla_io I don't have access to this anymore, but it comes down to wrapping that block array with a React component that listens for a window.postmessage from the iframe and changes the open state of the matching item.
Thrilled to announce that I've joined the incredible team at https://t.co/Ps15JZvbLw, a social impact organisation that is changing the game in leveraging technology for positive change. 🚀 @turn_io
@tbassetto@jh3yy@sanity_io something like this should do the trick ✨
{
...,
"matchedTags": coalesce(count(tags[@._ref in ^.^.tags[]._ref]), 0)
} | order(matchedTags desc, publishedAt desc, _createdAt desc) [0...5]
groq-cli by @sanity_io makes interacting with JSON from APIs very simple 💪 https://t.co/HUvgMyLEWl
It's one of the tools we use in our shell scripts to rapidly kick off new Vercel/Sanity projects @mawla_io ✨
@joelhooks@sanity_io@kmelve I always enable it in production, just to be able to quickly tackle any content questions or issues. Most CMS users will never use it, but it's good to have handy in case you need it.