Separate Package for common functionalities: Which composer package type to use?

Using Neos & Flow Neos Plugin Development
1

Hi Neos friends!

I would like to share common content elements (NodeTypes, Fusion files) across different projects. What is the current recommended approach to achieve this? I thought to create some separate Composer package, but I was not sure which Composer type should be used? I have seen “neos-plugin” and also “neos-package”. What is the difference?

Thanks for clarification!

2

There is no technical difference between neos-plugins and neos-package, only neos-site packages are handled differently.

Mostly neos-package is used while neos-plugin generally is for stuff that adds larger isolated functions but there are no strict rules. You may even use “neos-unicorn” as package-type which is fine aswell and will lead to a folder named “Unicorn” containing all packages of this type.

2 Likes
3

Or neos-mycompanyname resulting in those packages being installed to Packages/mycompanyname/The.Package

4

But unicorn is so much nicer :unicorn: also it actually supports unicode. So neos-:duck:terprise would be a valid package type aswell. Might be a bit hard to navigate via shell but why not.

2 Likes
5

So true!

6

thanks @mficzel and @christianm for your explanations!
I will go the unicorn way :slight_smile: