T3B013: TYPO3 Neos (Part II)

Contributors:
avatar Sebastian Michaelsen Amazon Wishlist Icon Paypal Icon
avatar Sebastian Kurfürst
avatar Robert Lemke Amazon Wishlist Icon

Introduction

What has happened in the last year?

Release of Neos 1.0 in December 2013, New Neos Website (based on Neos), Release of Neos 1.1 in June 2014, Multilanguage support is considered in the architecture since quite some time but is not finished, Neos Content Dimensions, Release Party

How does Neos gain acceptance?

There were TYPO3 conferences in North America and Asia, TYPO3 CMS is trying to gain ground outside of central europe since a long time, Flow attracts new people from the PHP community, there is lack of marketing, most TYPO3 agencies still work with TYPO3 CMS, TYPO3 CMS was improved by backporting ideas and concepts from Neos/Flow

More about Neos

Typoscript2 is glue, out-of-band rendering, Inside Typoscript, Flow has great caching features and is quite fast, release planing, either multi language or user rights management could be the big feature of 1.2, Neos’ release planing differs from TYPO3CMS because it’s in a different situation, JIRA for Neos, Neos follows semantic versioning

The team and its value

The team values: Humility, Respect, Responsibility, Trust. Get support at neos@typo3.org, there’s a helpdesk solution behind it, there’s 1 team for Neos and Flow

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax