-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Status of Next Drupal #520
Comments
Would be great to know - @shadcn looks to have joined Vercel. Is someone carrying the torch at chapter-three or should we start forking? |
@dottodot @MartinDavi yes, we are planning to continue development of Next Drupal. @shadcn worked full-time on Next Drupal. While his departure felt somewhat inevitable, we don't currently have another developer that we can put solely on Next Drupal. Instead, a few of us will be working on bugs and new features as time permits. This provides an opportunity for the community. Instead of this project being almost exclusively worked on by Chapter Three, we would like to get more involvement from others. We will be providing a roadmap in the near future, and would welcome your thoughts and ideas. Beyond that, PRs to fix bugs and to add features/etc will also be encouraged. |
@robdecker thanks for the update will definitely try and help out as and when I get the time |
See #692 |
Hello just wondering what the status of this project is as it seems to have gone a bit quite recently, there as some issues such #488 which prevent updating Nextjs, so this is really just to get a gauge on when and if they might be fixed, or if I should start to look at finding a fix myself, just don't want to waste time working on it if something is in the pipeline.
The text was updated successfully, but these errors were encountered: