Transcript
I got the jacket on, and I want to show you this. Sanity Pioneer 2026. Very happy about that. Thanks everybody at Sanity, really appreciate it. Great event.
Everything NYC, first of all. Wild landing page. I don't know if you've played around with it, but it actually has a full AI agent for this. The conference is at Pioneer Works, which is wild. I don't know if anybody's ever been there, but it's a really cool place. There's also an amazing light show or live art installation that was really cool. I've noticed that Sanity's design game has been going real high. It's looking really cool.
Let's talk about the landing page. If you haven't seen it, there's an Everything 2026 recap. I'm going to tell you exactly what I think of everything on here.
Knowledge bases is an interesting one. I didn't initially know what this was going to be, but effectively if you've used the Sanity context thing, it's kind of similar, but this is far better at creating a giant pool of information and being able to get that information and find out where the content gaps are. You can also find out what people are looking for depending on the level of security, and most importantly, you can find inconsistencies.
Pretty much everybody has tried creating a company portal in a multitude of different ways. We've tried it. We're actually in the process of building a Turboar brain. This was before knowledge base came out, but knowledge base actually makes it better. As soon as you build one of these, it works the exact same way as development. When somebody says as soon as you build a line of development, it's development debt because it's just a matter of time before systems upgrade, code changes, things get deleted.
Knowledge base is interesting because it has this self-sustaining element of it where you can effectively say on your website that your pricing is a tenner to do this, but on your database it actually says that your pricing is 15 quid. Or on documentation it says your returns are 30 days but on the actual product page it says 15 days. Which one's the right one? That's one thing that knowledge base can do very well.
The other thing it can do very well is basically set up an MCP endpoint and then you can have people hit that MCP endpoint and find out exactly what people are searching for. This is really cool for two reasons. One because people are looking for things on your website and you've given them basically a way to interact with that, whether it be by chatbot or search or something else. You can basically hit that endpoint.
But the more interesting thing is that you can use this knowledge base for finding out what your LLMs are looking for if you use it in a certain way. You can feed the LLMs and say here's an endpoint that we're basically putting out there publicly, and then the LLMs can go hit that endpoint and you can serve that information back. But the cool thing is that you can actually find out where those knowledge gaps are. So if all the LLMs are trying to work out what we do for WordPress, I can have a heart attack and say there's no way I'm going to build that crap and then eventually have to be forced down to building WordPress because so many LLMs are going out to basically find that information.
It's really cool. It works with existing Sanity. What was most interesting is it also exists with websites that aren't on Sanity or systems that aren't on Sanity that are able to be scraped, and it also works with PDFs which is pretty wild. Definitely worth looking into. For forward thinking companies, I absolutely think this is going to be the big kicker thing for 2027.
And talking of 2027, 2026 is the year of workflows. Everybody's releasing workflows. There was AI SDK and the workflow SDK and now Eve from Vercel. This is kind of more of a curated workflow system where you can essentially set the steps up.
Where I can see this working, if you haven't done this already, it's really cool, is that you could have somebody on the team, and realistically we should run a lawyer before we actually say anything on our blogs. So we might have multiple steps. We might have first version, AI slop version. The first version basically puts a whole bunch of AI content. We look for a bunch of competitors and say I want to have a blog that outranks A, B, and C. Cool, here's that slop 30,000 character article. Nobody wants to read this crap.
Step two is a human comes in and goes, I don't want to read that. Let me cut it down a little bit. Maybe cut it down to 1,500 characters. Maybe throw a couple of colloquialisms in there. Eventually you're at the point where you think, oh, step two, that's great. There's a human in the loop. I've proof read it. It looks good. Cool, let me move it on to step three.
Step three is your legal team that goes, oh my god, you can't say that. You can't say that. And we'll probably get sued if you say that. So we can go back to step two again. Human comes in the loop. Okay, let me fix this and then push it back to legal until it's completely milquetoast and it says nothing offensive about anybody and we can push it out to the live website. That's realistically one of the use cases of workflows.
But it doesn't have to be just three steps. It could be 20 steps. It could be two steps. It could be an entire AI workflow that goes for 10 steps and then there's only a human at the 10th step. The limit is your imagination. I could see this being super useful, especially with teams that are going for internationalized content. Workflows is going to be huge.
There's also videos on here. These videos weren't here originally, but they're definitely worth a watch.
Content variants is one I'm not sure how much I'm allowed to say about. It looks like some variation of content that you're writing. From what I can see, read this bit here. I'll say no more.
Durable functions is this one I'm arguably the most excited for because I'm a big fan of AB testing and personalization and a lot of other stuff. Durable functions is great because you're actually getting these things inside of Sanity. Everything is very native to Sanity.
I can see that the way that this is going is that for example, you have development environments. You probably want to have Next.js and Vercel and that whole thing feels seamless. You can also use Eve and that's like the AI side of things from a development perspective. And then there's a content platform which is Sanity where you have Sanity's durable functions, Sanity's AI actions, Sanity's workflows, and Sanity's knowledge bases, all of these things coming together.
I think there's never been a better time to build like your website, your company support pages, your company AI bot, the processes, the way that if you have a whole returns process, you can basically give that knowledge base and you can give every answer and every question possible that comes from your entire surface of your website, support pages, PDFs, everything. It's a really good time to basically silo the two of those things only when they need to be siloed and basically build two totally separate systems. One that's more focused around the development side, one that's more focused around the content side and marry the two of them up in perfect harmony for headless stuff. It is a very cool time.
Sanity blueprints is neat as well. This one's coming soon, not even a beta. A Sanity blueprint is basically a speed running a function. One of the ones that we've used before was a Sanity blueprint to do redirects. So for example, if you change a page URL, the Sanity function immediately fires off and puts a redirect from page A, which it used to be, to page B. So you don't lose any of the SEO from people that would go to the old page that might be indexed in a whole host of different places. It just redirects to the next one without you even having to think. The beauty of blueprints is it just comes in, it knows how your setup is and it builds it.
This is especially interesting to us because we've had this long-term question about Turboar of should we make this kind of a piecemeal offering or should we have very distinctive repos that people can take from and build.
Project Horizon looks wild is all I'm going to say. There's a lot of very cool things on the horizon that are coming from Sanity. It looks like it's very agentic. Agents use tools, delegate tasks, and move projects through to completion with your team in the loop the whole way. This bit is very cool, and I would be very curious as to how this looks in the future.
Resonance I remember was really cool. Basically resonance is a way of testing content. We saw this when we were looking at it on here with the MGH life sciences folks. It's a great way of being able to get that same sort of committee. If you're going to push something out there and you have a whole bunch of personas that are specific for your market. For us, we might have tech-conscious CTOs that are looking into content work or somebody from marketing that wants to make their entire marketing pipeline faster. Write a whole persona about it and then basically test the blog based on that persona. Does it score well? What do they think it's missing? Where are the content gaps?
Resonance is really good. I could see it being a pharmaceutical company's best friend because you have to do so much work to make sure that you aren't essentially alienating specific folks. You also have to talk in such a language that basically you have to have a computer decode it to be able to figure out what the hell's being talked about. Resonance is a really good one if you're in one of those specific niches that has to make sure that their content lands no matter what.
There's so much to unpack from the event. If anybody has any questions or if anybody was at the event and didn't get a chance to meet up, I'm more than happy to jump on a call or chat. Everything was an absolute blast. Thanks for inviting us.
