[Neos] Request for qotation : "Porting Custom Content Elements to TYPO3 CMS"

[Jigal van Hemert]

Hi,

On 26-6-2013 7:07, Kay Strobach wrote:
> Sadly all this approaches are unsafe investments regarding NEOS. Lateron
> i found, that NEOS will ship sth. similar called CCE:
>
> http://docs.typo3.org/neos/TYPO3NeosDocumentation/IntegratorGuide/CustomContentElements.html

This looks really interesting! Definitely something TYPO3 CMS could use.

> Would someone of you the NEOS developer port these 2 features + the Yaml
> parser back to TYPO3 CMS?

I agree with Robert in the Google+ discussion that it's probably less 
useful to backport all these features which are still maturing.

We could focus on having a form of Custom Content Elements which is 
technically more compatible with the way TYPO3 CMS stores content 
elements than TemplaVoilà does with Flexible Content Elements (FCEs).
Gridelements doesn't feature FCEs, it brings layouts to content 
elements; CCE/FCEs go a step further.

> I just assume, that the following stuff would work then:
> 	- Workspaces / Versions
>   	- Translations

I wouldn't assume that these will work with backports. IMO it would be 
better to make a TYPO3 CMS native implementation and keep an eye on how 
the CCEs are stored in Neos. That way we have a feature that works with 
CMS and the data can be migrated to Neos in the future.

> I think even if its work in TYPO3 CMS it's a huge investment in the
> future of NEOS, as it's a signal that we care about migration, and it
> also would give all those content integrators a nice tool, which can to
> most of the things TV can do.

We all care about migration, but at the moment Neos is still a moving 
target. Robert also mentions that implementation in Neos might change 
once it's used in real-life situations. As seen in Extbase we will end 
up with an implementation that is not the same as the original anymore.

Keeping both products in sync would be wonderful, but it takes too much 
resources.

Anyway, if we can create CCEs that can also be used with the generic 
mapper that is being created we would have a great feature.

-- 
Jigal van Hemert
TYPO3 CMS Active Contributor

TYPO3 .... inspiring people to share!
Get involved: typo3.org