Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Neos... WTF?

Neos... WTF?

Vorstellung von Neos CMS auf dem TYPO3Camp Mitteldeutschland: Was hat sich die letzten vier Jahre getan? Wie hat sich Neos weiterentwickelt? In welcher Art von Projekten wird es eingesetzt?

Sebastian Kurfürst

January 25, 2019
Tweet

More Decks by Sebastian Kurfürst

Other Decks in Technology

Transcript

  1. What is your background? Experience with TYPO3 / Neos /

    ... Experience with Symfony / ... *you?
  2. CMS

  3. main (ContentCollection) support (Page) SignUp (Form) KiteSupport (Text) sidebar (ContentCollection)

    FindSerialNumbers (Image) WinAKite (Text) completely customizable node types start with sane default types, or roll your own
  4. 'CoreKites:Kite': superTypes: 'Neos.Neos:Document': true childNodes: 'features': type: 'Neos.Neos:ContentCollection' constraints: nodeTypes:

    '*': false 'CoreKites:KiteFeature': true ui: group: 'products' label: 'Kite Product' properties: 'teaserImage': type: 'Neos\Media\Domain\Model\ImageInterface' ui: label: 'Produktbild' reloadIfChanged: true inspector: group: 'kiteProperties'
  5. Performante Auslieferung Two Stack CMS Neos CMS Content Authoring Content

    Delivery Delivery Layer Delivery Layer ... Content Store (Redis, Replicated)
  6. Delivery Layer Neos CMS further APIs Content Proxy further APIs

    Content Store Content Renderer Performante Auslieferung Two Stack CMS
  7. Flow Framework Content Repository Custom Packages Fusion Neos Media (Images,

    ...) MVC HTTP Object Management / Dependency Injection / Aspect Oriented Programming Neos UI Fluid Persistence
  8. custom node types nested content
 (with constraints) preview modes (f.e.

    mobile, desktop) custom inspector editors arbitrary frontend rendering
 (through Fluid and Fusion) extensibility everywhere
 (planned and unplanned) DDD Application Framework
 (through Flow)