Composer or Git Submodule

I’m starting a new Kirby project, but I don’t want to download plainkit and work from there. I want to use either Composer or Git to manage the Kirby core.

Is there a method that’s better? What is the Kirby way doing things?

1 Like

I personally use git submodules, but I know devs that use composer.
AFAIK it’s a developer preference and Kirby supports both. Use whatever works for you :+1:

1 Like

Personally i prefer the composer method, which also allows you to install plugins and easily upgrade them. The downside is that requires the plugin author to properly set it up for composer. Most of the them are now, but you might hit the odd one that you either have to manually install the plugin or do it as a sub module.

1 Like

I ended up going with submodules. I’ve been using submodules since K2, so why change what already works.

1 Like

Great to see this conversation here.


I think I’m going to skip composer, as the client doesn’t understand the need.