Honestly I don’t have a deep knowledge about atomic, but reading above reply I can imagine myself using Editable and Content. But as said, I’m not hindered by deep knowledge of the package
By skimming the blog post about Atomic I can not see myself using that same structure. But that’s probably because we work with a CMS-agnostic set of components, and for such usecases I’m reluctant about adding code to the core that might not be used, or is really opinionated. I think such code would belong to a separate package, and not in Neos.Neos.
In my perfect world Neos.Neos would only be domain logic linking the CR, Fusion and some really CMS-y domain logic with a connector for a UI or something like that. It is already more than that, and that hinders me if I try to work with CR and Fusion rendering in a standalone matter without Neos for example. So I hope you see the point why I’d vote against adding more to the core, as I’d rather see a slimmer core.
btw… I’d be all in for making the package “official” and putting it in the main dev repo and so on, but just in a completely removable package as I don’t like code lingering around if not used