GeezerVison is showing github.com — State of the project · Issue #429 · contentlayerdev/contentlayer
State of the project #429DescriptionHello Contentlayer community,
I wanted to share an update regarding the ongoing maintenance of Contentlayer. I am committed to the project and will continue to work on it, aiming for monthly releases (for as long as there is sustainable financial backing). These updates will prioritize fixing pressing bugs and, when possible, introducing new features. I appreciate all the support and feedback from the community and am glad to see developers finding value in Contentlayer.
I'd like to thank Stackbit for their generous, continuous sponsorship of Contentlayer, making the initial development possible. However, (at least for now) they have had to scale down their level of sponsorship, and as a result, I can currently allocate one day a month to the project. I kindly ask for your understanding and patience, given these time constraints, as I continue my efforts to work on Contentlayer.
Thanks again your ongoing support and helpful feedback. Your input contributes significantly to the development and improvement of Contentlayer.
💜 Reacted by Michael Hays, Yony, Juliovaz, Nelson and Prince Gupta Reacted by Ashish Yadav, Josep Vidal, Jamie Barton, Jason Gerbes, Maximilian Kaske, Sean C Davis, suntudo, Akhila Ariyachandra, Ross Zurowski, Daniel Castillejo and 59 more Reacted by Atahan Yorgancı, Petr Cibulka, loczek, Yangshun Tay, Prince Gupta, Yony, Juliovaz, Matthew Wong and Nelson Activityashiishme commented on Apr 24, 2023 Reacted by Lukas von Dollen, jua and Dominic Fournier jasongerbes commented on Apr 24, 2023 Thank you for the update, @schickling. It's unfortunate to hear that Stackbit has had to scale back their sponsorship.
Are there any opportunities for community funding or contributions that could help Contentlayer reach V1? Reacted by Lukas von Dollen, Alexander Hofmeister, Dominic Fournier and LockScript seancdavis commented on Apr 26, 2023 Thanks for the update, @schickling!
My Involvement
I will also continue to be involved. My efforts will largely be focused on docs and will equate to about 1-2 days per month. I plan to spend a few hours each week improving the documentation so that we can all continue to have a good experience working with Contentlayer.
Docs Improvements
If you find gaps or errors, or have ideas for the site or documentation, please create an issue on the website repo.
Project Contributions
@jasongerbes (and others who may have the same question): The most valuable forms of contribution today are list on this page.
Given @schickling's reduced time, the most valuable of this list are in providing support to the community, in the form of:
- Triaging issues: Verifying that reported issues are reproducible and asking for more information when the reported issue is not clear.
- Responding in Discord: Many folks report issues in Discord before creating GitHub issues. Most of these are questions that can be answered without creating an issue. Some should be logged in GitHub. Helping users get to the right path is valuable to the project.
Feel free to jump right in. Or, if you'd like help forming more of a process, or would like to contribute in other ways, feel free to reach out directly to me (Discord is best) and we'll work together on it. Reacted by Johannes Schickling, Anton Kouliavtsev, Guide Fari, Yangshun Tay, jua, Morgan Feeney and Prince Gupta LunaticMuch commented on Jun 12, 2023 Any help I can give here? Reacted by Johannes Schickling, jua, Prince Gupta and sakibarifin schickling commented on Jun 28, 2023 CollaboratorAuthor More actions
Any help I can give here?
Thanks a lot for your offer. A great way to help out right now, is to reproduce and to help investigate open issues to understand the underlaying problems so they can be fixed more quickly.
Another great way to help out, is to help others with their questions e.g. in the Contentlayer Discord. Reacted by jua, Morgan Feeney and Prince Gupta schickling commented on Sep 22, 2023 CollaboratorAuthor More actions Hey folks! Just wanted to provide a little in-between update:
As you might have seen, Stackbit recently got acquired by Netlify which (at least for now) means that the sponsorship of Contentlayer has been paused. I'm hoping to hear back from Netlify soon on the continued sponsoring & development of Contentlayer as there is a lot more work to be done! 💪 Reacted by Dan Stroot, Siro Díaz Palazón, Nas, Brock Petrie, Prerak Jain, Jahir Fiquitiva ☻, Frankie and Mark Waterous Reacted by Daniel Norman, Alex Pavlov , Marco Franssen, oxomoto, Lukas, Jakob Heyder, Torleif Berger, warjiang, Ibrahim Osman and Jahir Fiquitiva ☻ schardev commented on Nov 21, 2023 hey there @schickling. Is the project still maintained? Would like to help out with pending stuff.
Thanks for the awesome work :) Reacted by Lucas de França, MengXi, Sebastian Sebald, Danny, Petr Cibulka, David Tucker, Nas, Nat Welch, Jacobus Geluk, Valerius Mattfeld and 3 more Reacted by David Hirsch and Mahmoud Abdel Mohsen TheMikeyRoss commented on Jan 13, 2024 Netlify is kinda runining the open-source CMS eco-system. Reacted by TheMikeyRoss, Valerius Mattfeld, Tifan Dwi Avianto, Lubomir Georgiev (Любомир Георгиев), Paul Stamatiou, Timmy O'Mahony, Samy Rahmani, Joe Clack, gd996 and dgknca Reacted by Jacobus Geluk and Saurabh Charde jgeluk commented on Jan 16, 2024 Reacted by Elie Steinbock, Ian, Patrick and melodyclue elie222 commented on Jan 17, 2024 Reacted by Wei Chun, KeisukeYamashita, Prince Gupta, cryptod0c, Dan Stroot, Trevor Pfizenmaier, Valerius Mattfeld, ninohx96OvO, Rodrigo Trigosso, Rafaell Lycan and 3 more airtonix commented on Jan 24, 2024 airtonix commented on Jan 24, 2024 zce commented on Jan 26, 2024 Reacted by TheMikeyRoss, helywin, Trevor Pfizenmaier, Agustinus Nathaniel, Tifan Dwi Avianto, Miracle Friday, James Shopland and Josh Andromidas johanguse commented on Mar 11, 2024 Reacted by Parth Kabra Reacted by Malik Piara, Zeno Jiricek, Nik, Alexandre, enguerran, Jani, Francis Thibault and Parth Kabra alexerhardt commented on Mar 12, 2024
I'm currently looking at either Sveltekit + mdsvex or Astro. Both provide really good .md and .mdx support. Astro basically has .md support out the box and can add mdx with a simple "pnpm astro add mdx"... Super easy... Assuming no one wants to really take on a full rewrite of their app though. But for new projects, Astro or Sveltekit might be an option? Disappointed in how bad md and mdx support is for Next Js. Contentlayer was really good and was so nice to use, but in the same boat as above, cannot rely on a dep that isnt being maintained and cannot wait forever to see what contentlayer's future is. its a shame...
My brother from another mother. Thanks for the inspiration. I had no clue Astro had such strong MD/MDX support, and I wouldn't mind rewriting my site. All I ever wanted was the local-markdown-CMS experience, it's cool to see there's a front-end framework with first-class support for it! goustaff commented on Mar 20, 2024
While I haven't heard yet from Netlify about this, I've heard from some folks in the Effect community that they seem interested in potentially getting involved as core maintainers. No timeline on this yet but a glimmer of hope. ✨
I have a lot of hope concerning Contentlayer. I truly believe it's an excellent solution.
I wish all the best, and I hope that these good news will materialize into reality... Reacted by Petr Cibulka, Morgan Feeney, Karol Majewski and Patrick Hladun timlrx commented on Apr 1, 2024 Hi Contentlayer community, I have setup a separate fork available at https://github.com/timlrx/contentlayer2 to keep the torch going! It fixes many of the outstanding dependency and compatibility issues. Feel free to update your dependencies and happy to get more maintainers on board. Reacted by cryptod0c, Asta Bankauske, Karol Majewski, Sebastian Sebald, Yufan Sheng, Brendan Strong, Andreas Petersen (Guldberg), Steven Tey, Zachary Zajdel, Tuan Nguyen and 2 more Reacted by Zeno Jiricek, Steven Tey and Andres Gonzalez Reacted by cryptod0c, Karol Majewski, Andreas Petersen (Guldberg), Steven Tey, Andres Gonzalez and Cameron Smith Reacted by cryptod0c, Karol Majewski, Andreas Petersen (Guldberg) and Steven Tey seancdavis commented on Apr 1, 2024 Hey folks: cross-posting this most recent update:
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.
Reacted by Johan Guse, Timmy O'Mahony, Lloyd Richards, Richard Davies, Asta Bankauske, Michael Hays, cocdeshijie, Tifan Dwi Avianto, Jamie Rolfs, yikZero and 4 more goustaff commented on May 22, 2024 TheMikeyRoss commented on Jul 23, 2024 Reacted by Jani, Lubomir Georgiev (Любомир Георгиев), enguerran, Ru Chern Chong, kitze 🚀, Pablo Hdez and melodyclue timlrx commented on Jul 23, 2024 Reacted by Lloyd Richards, Cameron Smith, Saurabh Charde, Karol Majewski, Johan Guse, Rafaell Lycan, Natik Gadzhi, Morgan Feeney and drericfm dstroot commented on Jul 23, 2024 I migrated to Velite some time ago when ContentLayer was no longer maintained. For me "it just works". There may be risk because I think it's a one developer project but I needed something that worked. Cheers. cameronraysmith commented on Jul 24, 2024 rufuspollock commented on Jul 27, 2024 Firevvork commented on Aug 23, 2024
I've been investigating alternatives for the last week for my own nextjs projects and not finding anything I really trust. Maybe it will help someone else what i summarized:
package maintained typed data frontmatter rehype comment
@next/mdx ✅ ⛔️ ✅ ✅ mdx has to be part of router
next-mdx-remote ✅ ✅ ✅ ✅ can't import components in mdx file 1 ⛔️
mdxts ✅ ✅ ⛔️ ⛔️ very light feature set
velite ✅ ✅ ✅ ✅ very early beta and not widely adopted (yet?)
None of these feel like a long term solution that could replace Contentlayer so am planning to stick to what I've setup so far and keep my fingers crossed that something doesn't update and break my content generation.
Hopefully some good news comes from the Effect community and this can be maintained again. Would be super sad to see such a great library disappear.
Now @next/mdx has supported using imports. goustaff commented on Sep 29, 2024 Reacted by Lukas von Dollen gianpaj commented on Jan 29, 2026 What library are people using now in 2026?
EDIT:
I'm having issues with ContentLayer and code formatting. I can't get it to work with various Rehype plugins I've tried - namely
fixed:
import { makeSource } from 'contentlayer2/source-files';
import remarkGfm from 'remark-gfm';
import rehypeHighlightLines from "rehype-highlight-code-lines";
import rehypeHighlight from 'rehype-highlight'
export default makeSource({
contentDirPath: '.',
mdx: {
remarkPlugins: [remarkGfm],
rehypePlugins: [rehypeHighlight, rehypeHighlightLines],
},
});lloydrichards commented on Jan 29, 2026 Reacted by Karol Majewski and Morgan Feeney
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|