No news plugin?

Hi there, I’m a bit confused by not finding a news package/plugin under I thought this is the place for official plugins. Can it be that no news plugin is available for neos right at the moment or am I just searching in the wrong place?
Best regards

The reason is that it’s fairly easy to do this with custom Node Types. You usually don’t need an extra news package.
I don’t have the time for it right now but for inspiration you can check Robert’s Blog package.
The idea is to have on Document (which is a Node Type as well) that is used to create news and another Node Type that displays all Node Types that are of this type. This is exactly what we do on our own page (not a complex News “system” but it works that way):

Hi David, thanks a lot for your answer.

Of course I understand that it’s easy to do such things with custom types. However I thought that there are packages for the most common functions. It seems that this is not the case.

I quite have skills in developing websites but I am rather new to NEOS. So the principles of news, blog or whatever lists are common and I could do these things straight forward within a few hours in other CMS systems. But at the moment it would take me a few whole days in NEOS and as my project is no business purpose I just don’t have that time left right now.
This is just for explaining the big mountain that is between the general simplicity of a news list and the actual implementation by development. So even such a simple package would help beginners like me to get into it easier.

So if someone could provide a package to install I would be happy. Of course not to do my work but helping me understand those things immediately by doing/changing and not from the scratch.

Best regards

Hi @Martelinho,
maybe you could check this package: as a base or to use it right away (I believe it was not ported to the latest Neos 3.x unfortunately).


Hi @Martelinho

You can find this plugin

even though it’s outdated and depends on the typo3/neos package, it’s a great place to start. Perhaps @stolle can tell if he will update the requirements or if it’s working (dunno about composer being able to resolve typo3/neos to the renamed neos package)

1 Like

Already had it updated at some point. I’ll check and push it later!

1 Like

Thanks for your links @david.sporer, @ilCerchiari, @sorenmalling.

Got a first look into all plugins on github and the code from @stolle looks most understandable to me. Maybe that’s because it is based on another package (flowpack/listable) or it is just beacuse of its functionality. It seems reasonnable to wait for Johannes push on github and then try to integrate and learn from this implementation. I already found flowpack/listable while my search yesterday and it seems to be good idea to get to know this package by the way.

Thanx and best regards

1 Like

You don’t have to wait for @stolle to push a new version - you can easily copy/paste the NodeTypes to your own package and start experimenting.

I’ve heard @dimaip saying nothing but nice things about the Listable package (IIRC he’s the maintainer/author aswell :stuck_out_tongue: ) and it seems to be awesome tool for listing all sorts of nodetypes.

So indeed a great way to start getting to know for Neos and Fusion work togehter.

I’m refactoring Listable now, will merge soonish the new version:

For beginners, I’d recommend exploring how Listable works and roll your own custom solution.
Unnecessary abstractions cause pain if you can go without it, do it!
Over the years I found Neos.Fusion:Collection to often be the best abstraction for my data listing needs…

Thanks @sorenmalling and @dimaip for the additional infos.

Already “inspected” the code of both plugins. Very very very much things to discover which I’m not able to put into the right context with my current knowledge gap. But of course this is the usual initial learning process I have to go through.

I think I got all required information for this task.

Thanx to all helpers

If you’re interested in an example of how to use the Listable package for articles, has a implementation for the blog and it’s available in a public repository.

Be aware that it’s using the version prior to the refactoring @dimaip mentioned.

Of course I am.:grinning:

Will have a look at it next days. And thanks for the version hint.

Hey @Martelinho, I tried to confirm what @david.sporer had said with a video on the subject


Hi @dimaip , thank you so much for the tutorial. Great guy, doing such things btw.

I didn’t have that FusionBP project installed so I first tried to make the extensions within the official demo project. That didn’t work and after reading some docs and watching another tutorial from you I know why. So I downloaded the FusionBP project from Github and installed the package into my NEOS installation.

I can understand everything you show. But one thing just doesn’t work. In News.LatestList.fusion you inherit from Neos.Fusion.Collection which doesn’t exist even after installing the FusionBP project. As it is called collection I tried to inherit from Neos.Neos:ContentCollection which also doesn’t work (Exception “No content collection of type Neos.Neos:ContentCollection could be found in the current node…”).
Do you have a hint what is missing or going wrong?

And just a small other question. You mention that the official demo project will come soon with changes resulting from the FusionBP project. Is there a rough estimation when this new demo project will be released?

Hey, it should be Neos.Fusion:Collection. It’s a native Fusion object.

The new demo site is here:

FusionBP is just an example project, you don’t need to install it as a whole, just learn some ideas for organizing your code and write your own site package from scratch.

1 Like

:angry: F…antastic.
Ran into this problem couple of times since I’m not used to this notation for objects. Caused me some problems and took me some hours but in every other cases I found the problem after some concentrated checks. Sorry for that question.
Thanx. I will also have a look at this new demo site.

1 Like

Ok, time to say thank you to all supporters in this thread.

Special thanks to @dimaip for your tutorial which guided me through important steps of my very beginning. I absolutely agree to you that the invested time will pay off. I partially disagree about the opinion that universal packages are not gainful. I think kind of such packages could upgrade the whole Neos system to a more powerful tool even for experienced users. This would cost some time but could also pay off in the long run. Can’t explain this shortly here but plan to write a thread which describes in detail what I mean.