Description
Hi! I've spoken with schickling late last year about continuing to support Contentlayer. Initially I suggested forking the project and there was some interest amongst the community on Discord. Schickling later suggested to create an issue offering my help on the main project instead. So that's what I'm doing :)
A little about me:
I'm a software developer working in the games industry but have been poking around in web for the last few years. I've been using Contentlayer for about a year in a number of different websites. I'm active on Discord and often try helping people who encounter issues there. I created a plugin for managing Contentlayer images. More recently I have rehosted the Contentlayer docs since the main website is down.
I'm not promising to bring Contentlayer up to date overnight nor very quickly either. I am, however, committed to keeping it maintained and used by the over 20,000 projects using it today.
My priorities would be to bring Contentlayer up to date with current NextJS versions, review and manage currently open pull requests, and work through the decent number of open issues.
Contentlayer is a brilliant tool that does what I want exactly how I want it. Maybe it's my stubbornness but I am not looking to use other content managers, so regardless if we can continue maintaining this project, I'll still keep using it and maintaining it for myself. So let's keep it going!