+1 👍

Srsly, please make it happen!

Is there a rough ETA? Now that Craft3 is in RC

I think his goal is Craft 3 launch

Have you heard when the Craft 3 might be moving from RC to final version? I couldn't find any roadmap on their website.

April 4th

Wow thats close innit. Thanks for the info maxwellhibbert!

Is there anything that we can do to help with this development? Only 2 months away from a GA.

Any idea on an ETA? Would be ace to use this on a new project we're doing on Craft 3. Would happily pay for this plugin on Craft 3!

I already did the work and transferred my Neo fields to Super Table fields. Not as nice as Neo, but maybe an option for someone who doesn't like waiting.

Looks like there are a couple of branches on the go, but no activity since January :-(

@nickdunn that's good to know. I don't think Super Table is going to work in this case so Neo on Craft 3 would be good.

Craft 3 has been released today :) Any news yet?

Ben updated the README on the dev-3-port branch. He is hoping to get Neo updated this week for Craft 3. 29f7b13

Also waiting for "The One" :)
I don't think the update has happened yet but hopefully soon.

Would love to see this one now that Craft CMS has been rolled out properly. It's the only thing stopping me from fully upgrading.

Any information when the port is done on this brilliant plugin?

Has anyone tried the dev-3-port branch yet? Does it already work?

THE ONE for CRAFT 3!

I have tried the dev-3-port branch and although you can build fields with it, it still isn't in a state where you can save content in entries.

Last update that mentioned it would be done within the week was more than 2 weeks ago now, any update from @benjamminf ? 😄 Waiting on Neo to migrate my website to Craft 3.

Has the craft 3 port stalled completely? Have a project that has been put on hold until neo for craft 3 is ready, so i would really like to see this in production soon.

Please release Neo for Craft 3!
I have 2 projects with are waiting for Neo

Doh! I thought this would have been one of the first to be ported. Need Neo. 😞

Newest commit message on the dev-3-port from last night: Block structure is next, then almost ready

@benjamminf NEOO!

I love your Plugin!

dev 3 port branch is looking good! can't wait for this to be released.

Is it ready to use?

@waswebb I've been playing with it but it def isn't ready. I do find it usable enough to do some development though.

Just a heads up for everyone else waiting, I reached out to Benjammin about the progress, and here's his reply (I hope he won't mind me posting!):

Development is definitely still going for my plugins, just obviously a bit slowly. Unfortunately I can't give a definite timeline for Craft 3 support on my plugins, but I can tell you I'm about 75% done with Neo, so I'm predicting it'll be a week or two away if all goes to plan.

I feel your pain as we're currently starting the move to Craft 3, but Neo is the only thing holding us back. So it's quite important for us to have it completed in the coming weeks. Embedded Assets and No-Cache are the other plugins we use on every project, so they also need to be ported very soon as well (though they should be quick compared to Neo).

In case you're interested where Neo is currently is at, configuring Neo fields is complete, so pulling down a copy from dev-3-port will let you start architecting your sites. Saving fields is a work in progress, but is close to complete. After that the plugin will technically be usable, but I will need to create migrations from Craft 2 before it's officially released.

Sadly I can't guarantee a deadline for the ports, but they will be completed at some point in the near future. Thanks the kind words and patience.

tl;dr: It's definitely coming soon, we just have to be a little more patient!

Live preview isn't working yet. I had a conversation with Ben a couple months ago and he said the structure is in place so as updates come they won't break the overall structure, but "bells and whistles" like live preview aren't set up yet.

Thanks for the info @gregorydavidjenkins

I have more than 10 projects waiting for NEO Craft 3. Please, make it happen and for your sake, don't make it for free this time! I think we all want to contribute. :)

Any news on this?

In the early phases of a project where Neo would be a great addition, but if it's abandoned or is going to be awhile I will move in another direction. A progress update would be very helpful.

Looks like Ben has moved to Facebook (according to Spicy Web) and the repo has been moved to their organisation account - anyone there looking to maintain/release this?

I've recently made contact with Tony Sambell, Director of Spicy Web, querying about whether Neo will still get Craft 3 support now that @benjamminf has left the company.

Thankfully, the news sounds promising:

We have taken over NEO and will have it Craft 3 ready asap.
We use NEO on all our websites and now that we have ownership we are making it a high priority to get it C3 ready.

Hi everyone,

I'm Thomas, I'm a developer for Spicy Web, and I'll be involved in completing the Craft 3 version of Neo. I've just updated the readme with a public message from Tony Sambell, the Director of Spicy Web, stating that Spicy Web will be supporting Neo from now on and intends to have the Craft 3 version completed and released by October 30. We will, of course, endeavour to complete it sooner if possible, but October 30 is our absolute, must-have-it-done date. I'll make sure to keep you all updated. Thank you for your patience so far.

Hey @ttempleton, I didn't want to open a whole new "issue" for a brief question;

Have you guys started looking into the new Project Config functionality in Craft 3.1, outlined here?

I'm sure it's on your radar, just curious—it seems like an amazing functionality that seems so logical it's crazy it wasn't built in into Craft 2. Anyway, looking forward to the release of Neo for Craft 3. Is the dev port still safe to use for testing purposes?

Cheers!

Hi @23d1

We've not yet looked into Project Config in detail, but we definitely agree, it's a fantastic new feature that will make life much easier.

Neo for Craft 3 is coming along well, it's still on track to be released by October 30, and I would say, for those who have been using it for testing purposes, that it's still safe to do so. All of the structural work was completed by Ben before we took over, so nothing will change in that regard to make it less safe to use, and our work from here will involve implementation of necessary features and bugfixes. I have live preview in a mostly-working state -- albeit still with a few issues that I hope to sort out early next week -- and then we'll move on to migrations from Craft 2.

As a side note: after we release the Craft 3 version, we do plan to return to the Craft 2 version and fix issues with the v1.5.0 release.

@ttempleton great news... and exactly what i was hoping to hear as far as migrations go. are you going to make neo paid? i hope so, i want to be sure we can rely on it going forward :)

Hi @theskyfloor -- at this stage I can say it's likely that the Craft 3 version of Neo will be a paid plugin. I can't yet confirm pricing, but will update with that information as soon as possible next week.

@ttempleton awesome, that is fantastic news in my opinion!

Just don't make it too expensive for us small fries out here. ;)

Hi @ttempleton is there a way to install the dev-3 for previewing/testing ? Composer ?

@H-i-red something like this in your composer.json will do the trick:

{
  "require": {
    "craftcms/cms": "^3.0.1",
    "spicywebau/craft-neo": "dev-dev-3-port as 2.0.0",
  },
  "repositories": [
    {
      "type": "vcs",
      "url": "https://github.com/spicywebau/craft-neo"
    }
  ]
}

Hi @timkelty , thanks but it´s not working "Your requirements could not be resolved to an installable set of packages", I have set "minimum-stability": "dev", "prefer-stable": true... ?!

Hi @H-i-red

What @timkelty posted should work with one small change: Despite the changeover to Spicy Web, at this time the entry in the Composer project requirements should still be benjamminf/craft-neo (this will be updated in the near future and I will notify when it has been updated).

On another topic, regarding Neo pricing: My understanding is that the initial purchase price of Neo for Craft 3 will be very low, and the annual renewal will be a standard price.

Woohooo 🤘 NEO is back 💪 !! Thanks @ttempleton

I see the duplicate button is replaced by a copy. Here comes a future request.. 😬

1. Be able to copy multiple selected blocks (Now I can only copy one at a time ?)
2. Bring back the duplicate button. For quick one copy use the duplicate button, for multiple, select your blocks and use the copybutton. So you have two buttons one for copy & one for duplicate.

Found a 🐛 . Upon save the preview for the blocks is lost, returning undefined in .preview-section. When I expand/collapse the block it´s shown..

I know this probably isn't the place for it, but I was thinking about making Neo a paid plugin... Being somewhat of an idealist in terms of open source and free software, I would urge that if there's a pricing model invoked—would it make sense to use a similar approach as ACF, where you essentially license the software, but can use it across many/all your projects?...

@23d1 that's an interesting idea. Would love to hear SpicyWeb's thoughts on that... we do use Neo on a lot of projects and pricing like that would be beneficial to us - we would gladly pay a decent fee for it let's say 99 to 199 a year but be able to use it on any site we want.

Interesting idea. If you go this route, Is it possible for two pricing levels? Single site and agency? Can’t forget about the little guys.

@luke-nehemedia would you be able to pay for it if it was 30 - 50 a project? because it seems like that is the other option. i feel like 99 - 199 a year for unlimited would actually be affordable.

Of course Spicy hasn't said anything so all just random conjecture!

Ideally it just remains free. I don't want the projects with micro budgets to have to use SuperTable or the likes. What was Ben's plans and wishes for this? Anyway, if it's not a huge fee I'd be fine with it, or developer licensing (one-time with a low yearly cost for updates or something).

Hello All, Neo will indeed be becoming a paid plugin. However, we have given this much thought and the way we have decided to price it will allow us to prove it's worth to developers. From my current understanding, we cannot charge unlimited agency pricing via the Craft Plugin Store. But once you see how we have decided to price Neo this shouldn't be as much of a concern. I know we can never make everyone 100% happy but I am confident most of you will appreciate the method in our madness once we launch Neo.

Totally get the choice of going toward a paid model. Personally, I'm super disappointed by it, however—as the ideal for me, and many I know, would be an agency pricing model. I guess it's time to look elsewhere for a lot of smaller projects. Keep up the good work, and hopefully in the future there's room to have a couple of different licensing models.

Cheers! ✌🏻

Hello All, NEO is now officially in the Craft 3 plug-in store. We are very proud to see it finally Craft 3 ready.
Yes, it is now a paid plug-in but Spicy Web as an agency will be giving NEO prompt and ongoing support.