Buy Neo and make it core

[angrybrad]

Created by: Anonymous (alan@theskyfloor.com) on 2015/03/10 17:00:50 +0000
Votes at time of UserVoice import: 109

---

Y'all should buy Neo by Ben Fleming and make it the way Matrix works in core... 'nough said it works well and does everything I wish Matrix would do already.

https://github.com/benjamminf/craft-neo

[angrybrad]

Posted by Daryl (craft@codeknight.co.uk) on 2015/03/12 09:36:29 +0000

---

I know I'm in a minority, but I'd rather not have this. It feels like Matrix is absolutely fine 90% of the time, and if you're a fan of Neo, you can install it.

[angrybrad]

Posted by Clive Portman (clive@webandpen.uk) on 2016/07/05 09:10:54 +0000

---

Matrix fields on steroids! I can definitely see why this is a popular request. Re-using custom fields within Matrix? Organising blocks with tabs? Grouping block buttons? Oh, yes please!

But, yeah, don't really want to have to install this as a plugin.

[angrybrad]

Posted by Florian (fw@demodern.de) on 2015/03/13 06:38:29 +0000

---

Yea I guess this is most requested feature in craft ^^

[angrybrad]

Posted by Benjamin Fleming (benjfleming21@gmail.com) on 2015/12/06 01:09:14 +0000

---

In response to the previous comment by anon, this is a common concern about Neo. I'm attempting to address this, which you can read about here: https://github.com/benjamminf/craft-neo/wiki/6.-FAQ#why-should-i-trust-a-third-party-plugin-to-handle-my-content

[angrybrad]

Posted by Anonymous (javanwyhe@gmail.com) on 2016/05/19 19:04:04 +0000

---

Every Craft site I've built so far has left me in a position where I wished that the matrix block could be a little more powerful and flexible, so I was crazy excited when I found this. It solves basically all the problems I've run into over and over again. Creating this sites as part of my job means that relying on an external plugin for what turns out to be about 90% of the page content is seen as risky, so adding this to the core would make it so much easier and add assurances for my boss and clients that their sites will continue being awesome and not break somewhere down the line.

Please. Please, please, pleasepleasepleaseplease...

[angrybrad]

Posted by Alan (alan@rosewoodat5th.com) on 2015/10/13 22:07:44 +0000

---

I only have to add that I feel as though Neo adds in many functions that are almost more Craft like than the Matrix even is... in fact I feel like it reduces complexity not adds to it. For instance: reusable fields are a staple of the Craft design philosophy and fields that you can use anywhere. I guess I don't understand the difference between building a Neo block and a Matrix block - to me there is no inherit difference or advantage in any situation to the Matrix block type definition when compared to Neo. That is why I made this feature request... to me, for most of my purposes, this is how the Matrix should work by default. Also quick field in conjunction with Neo is clearly how building something like a complex Matrix with reusable fields should be from the get go. Anyway just my two sense : )

[angrybrad]

Posted by Benjamin Fleming (benjfleming21@gmail.com) on 2015/12/06 01:09:14 +0000

---

This is a nice surprise haha.

While I'd love for Neo to make it to core, I don't think it needs to be in there. Neo is not meant to be a replacement for Matrix, and my main concern releasing Neo is that it might be seen as a plugin aiming to replace core functionality. Configuring a Neo field is fundamentally different than Matrix fields, because fields are reused rather than created in block types. This is why I consider Neo to not be a replacement, as each have their pros and cons.

Based on this, if Neo were to be in core, it would exist alongside the Matrix field type. In my opinion this would be especially confusing to newer developers of Craft. It is a complex field type that solves some hard-to-explain problems if you haven't been using Craft for very long. It's clear the developers at P&T value clarity and simplicity in their UI and Neo might be detrimental to that.

However, I do think some of the feature requests I've implemented in Neo can and should be implemented into Matrix, like max blocks by type.

[angrybrad]

Posted by Anonymous (alan@theskyfloor.com) on 2015/03/10 17:00:50 +0000

---

For the record these are the feature requests I could quickly find that the Neo filetype addresses in one way or another.

• Matrix field within a Matrix field #812
• Custom matrix block settings #865
• Hierarchical Matrix fields #827
• Limit Matrix Blocks Per Block Type #826
• Use fields accross multiple Matrix blocks #823
• Permit fields within matrix blocks to be collapsed #1274
• Conditionals in field layouts #805

[angrybrad]

Posted by Jake Dohm (jake@steadfastdesignfirm.com) on 2016/05/16 15:03:54 +0000

---

Please, please do this...

[davidhellmann]

Do this or make the Matrix Field with a more Modular Approach :)
Neo + SuperTable is really awesome

[msimpson]

We always utilize Neo with Craft to create configurable Web components. If this was added to core, we could leverage the plugin API to make reusable Web components across multiple instances of Craft. Please add this to core or implement something similar.

[benjamminf]

@msimpson For the Craft 3 rebuild of Neo I'm going all out with making Neo very friendly to plugins. You can leverage the current API of Neo to create reusable components (we're currently doing it at our agency) but it's not the easiest thing right now.

For those interested here is a description of what I want to accomplish with Neo for Craft 3: spicywebau/craft-neo#100 (comment)

I still feel that this plugin is not suited for Craft's core, but Matrix definitely needs an update. For now I'll continue working on Neo and make it as stable as possible.

[msimpson]

@benjamminf
I'll certainly take a look at that. Anything to make things more reusable is welcome.

[brandonkelly]

There are aspects of Neo that will have some crossover with future plans (#1524, etc.), but I agree with @benjamminf that Neo is better suited as a plugin than core features. Like Alfred vs. Spotlight.