#If anyone currently uses Sanity to host a Markd...
1 messages · Page 1 of 1 (latest)
Hi ! Why is motivating you for migrating to ContentLayer ? Just trying out or what ? I am using Sanity and loving it so far. Interested in what's motivating you.. Cheers
(@jaunty river Yep, sorry, haven't noticed the thread 🙂 )
Mostly it was just incredibly slow using the app router. I had previous experience on another app using contentlayer and it was quite fast.
The second and just as important reason is you can't make markdown interactive. So having popups/server actions, etc. But you can do that in MDX. I have a video on it.
I am trying to grow as an educator so I want to have things to more interactive experiences and mdx affords that
Sounds interesting !
Yes App router is slow on development. But when bundled and deployed I don't notice any difference. Regarding the CMS, so for a large content, quering ContentLayer would be faster than Sanity ?
I have experience with a small amount of data in Sanity, so for me it does the job well. But I agree that text blocks are quiet impossible to manage when you add style to block of text in Sanity Studio.
With 13.5 my app router development has sped up a decent amount. And I think Sanity would be fine to continue using if I didn't want to add interactivity to my markdown which Contentlayer allows for. I don't really use text blocks/portable text blocks. In my opinion, they do not scale and are quite nightmarish to work with at scale. We have them in our work production code base and they are fine but as things grow you have to think about a lot more code.
Sanity has a markdown plugin that you can use to write blogs and stuff and then just have some way of parsing that markdown on the frontend with react-markdown or something similar. But again, for me I didn't have a need for sanity anymore because of this desire to add interactivity to my markdown pages with mdx which Sanity doesn't allow for.
Nice, thx for the feedback. Will definitely check for ContentLayer for those purposes