Flownative Blog

The Neos Conference 2018 is over, and it was a blast! Following a sprint and a workshop it was two days packed with great talks, an awesome community and great spirit.

But to be honest: The Neos Conference is not about the talks (which were excellent), the location (which is hard to beat) or the organisation (which was awesome). It is about the experience of a common understanding and a spirit that is rare.

Neos has some powerful features under the hood which makes management of media files and documents easy. This post is the first part of a series about asset management in Neos CMS and Flow and explains the base layer of it all, the Flow Resource Management.

The Neos Conference 2018 in Hamburg is just two weeks away, as is the workshop we are giving on the day before. And tickets are still available!

On April 13th the Neos Conference 2018 starts and will bring you two days of Neos talks, networking and an all-around great experience. And on the day before, April 12th, we will hold a pre-conference workshop.

Last week all Flownatives – finally – attended a Neos sprint again… As was to be expected, meeting the Neos community was great, the location was awesome and we covered quite some ground together.

The Neos Team meets regularly online, in various groups and smaller teams. But nothing beats being in the same place for real, to discuss, work and have fun together. This time we met in Vienna, hosted by web&co and Code Q.

When working on the fulltext indexing for the Elasticsearch integration for Neos I recently needed a way to debug what was going on inside a Groovy script we use. It's relatively simple, if you know how…

As soon as such a need arises, finding the solution with a quick internet search yields a quick result along these lines:

import  org.elasticsearch.common.logging.*;
ESLogger logger=ESLoggerFactory.getLogger('some.identifier'); 
logger.info('Ah, a log message!');