next-drupal VS drupal-project

Shadcn UI is not actually a component library or UI framework. Instead, according to the documentation, it is “a collection of reusable components that we can copy and paste into our apps.” This reusable component collection was created by Shadcn, who has also created great open source projects like Taxonomy, Next.js for Drupal, and Reflexjs.

Hi! I think next-drupal (https://next-drupal.org/) at the moment looks like the most promising unifying way of getting a headless drupal site up in a short time.

Check out https://next-drupal.org

I started from this guide: https://next-drupal.org/

Here is the project home page, https://next-drupal.org

Also based on React, Drupal Next uses Next.js, as the name implies.

The future of Drupal is headless

You should have a look at https://next-drupal.org/ - good starting point for going headless. Related to drupal core you'll also find some initiatives for decoupling "stuff" ;), e.g. https://www.drupal.org/project/decoupled\_menus\_initiative

1) increasing timeout to 6000 as per https://github.com/drupal-composer/drupal-project/issues/197

Check out typical .gitignore files for Drupal. Like https://github.com/drupal-composer/drupal-project/blob/9.x/.gitignore

IF, you are using composer on your deployment targets… The only thing you need to store in git is your composer.json and composer.lock files, AND the /modules/custom/ directory and /themes/custom/ directory. (There’s some other tangentel files, like .gitignore and some other stuff you want in GIT, but it’s a MUCH smaller repository, since you don’t need to move around ALL of the files. Are you using something like this : https://github.com/drupal-composer/drupal-project ?

To update the Drupal core, it is slightly different than the Composer template for Drupal projects way to go, if you are used to it.