Proposal to become a maintainer for Contentlayer

[aelliixx]

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!

[thisislvca]

I'd love that!

[trebeljahr]

same here, please maintain this awesome project :)

[icco]

Yes! This would be great!

[herbievine]

Please!

[TheMikeyRoss]

we got your back 👍 once everyone realizes that PR's and Issues will actually be looked at then the repo will be active with PR's and Issues.

[TheMikeyRoss]

@schickling

[aelliixx]

we got your back 👍 once everyone realizes that PR's and Issues will actually be looked at then the repo will be active with PR's and Issues.

That's the hope. I'm keen on investigating some open issues even right now, but I realise that whatever PRs one might make to resolve them wouldn't be merged in either.

And thank you and the rest of youse who've shown support on this issue and on Discord. It's clear that people are keen to use Contentlayer and keep it alive. Hopefully we see some movement on that end soon!

[TheMikeyRoss]

It's clear that people are keen to use Contentlayer and keep it alive.

Absolutely! One of the most popular projects of 2023/2024 is using it! shadn/ui And many people (including myself) have used that docs as the foundation for our projects docs and now we're kinda stuck 😅

[jmatthewpryor]

any progress here?

[aelliixx]

any progress here?

Nothing on my end yet but I'm hopeful.

[timlrx]

@aelliixx I spoke with Schickling as well and he gave me the go ahead to maintain an updated fork of it. It's now available at Contentlayer2 and I have patched it based on my open pull request. Happy to get a few maintainers on board to restore other functionalities e.g. the website and chart a new roadmap.

[aelliixx]

That's fantastic, I'd be happy to help any way I can. First and foremost I'd be interested in bringing the main website up and running because that's what people have most issues with. I'm happy to host it at my expense, I just need the domain :)

[timlrx]

That's fantastic, I'd be happy to help any way I can. First and foremost I'd be interested in bringing the main website up and running because that's what people have most issues with. I'm happy to host it at my expense, I just need the domain :)

This is going to be extremely difficult since it was bought over by Netlify. I can try asking the folks at Netlify nicely :) But, we should have a contingency plan.

[aelliixx]

Well I guess the first question would be if you're keen on continuing with the contentlayer branding (or if the licensing even allows for that). Also, do you have a discord or someplace else we should continue these discussions as suspect we'll have smaller details to work out and this issue isn't the best place for it.

[Gerald-ux-ux]

Great idea man, this is definitely gonna help the community

[seancdavis]

Hey @aelliixx @timlrx and others: Thanks for starting this discussion!

I worked on Contentlayer with @schickling while at Stackbit, and I'm now over at Netlify.

I'd love to see this project continue. We're currently in discussions about the most effective path forward. There's much to coordinate. It'll take some time, but we're making good progress.

In the meantime:

• Use the Contentlayer2 fork.
• The website is back up. As the fork gets updated, feel free to open PRs on the website repo and DM me on Discord (seancdavis29) for a review.

[Virous77]

Kudos to you man.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[TheMikeyRoss]

no :(

[sidwebworks]

If you use pnpm then you can do this using aliases

pnpm add contentlayer@npm:contentlayer2 next-contentlayer@npm:next-contentlayer2