Base Distribution

Phoenix new Content Brainstorm

 * There will be simple and compound content types
   * simple type -> image, text, object resource? (no children)
   * compound type -> (has children) container, based on container and a combination of other types (nesting possible)
 * We need a "Parent" content type to distinugish which content types are available for aloha
   * -> all elements which are NOT of type TYPO3:Folder should be insertable
   * -> needs to be refined later via constraints (f.e. "Text+Image" contains 1Text and >=1 image (local constraints) -> can be resolved automatically
   * -> and later on a constraint system to define which content elements can be used in which node (on which page, in which section) (global constraints)

 * Instead of local constraints: for now, we take a factory to create all needed nodes for a combined type at once
 * adjust service to get single rendered content nodes for (parts of a page)
   * needs probably modification of NodeObjectConverter
 * On the client side, we will add the placeholder content (depending on the Types, which are inside the registry as schema)

http://phoenix.demo.typo3.org/homepage/anotherpage.html

http://phoenix.demo.typo3.org/homepage/anotherpage.html?filter=...

http://typo3v5.local/typo3/service/rest/v1/node/live/sites/phoenixdemotypo3org/homepage/main/text1.html
-> er soll das Template, was bspw. an "text1" hängt, nehmen
site
    homepage (page)
    ->TS template A
        main (section)
            text1 (text)
            ->TS template B

Bei Rendering von http://typo3v5.local/typo3/service/rest/v1/node/live/sites/phoenixdemotypo3org/homepage.html -> TS Template A wird verwendet

http://typo3v5.local/typo3/service/rest/v1/node/live/sites/phoenixdemotypo3org/homepage/main/text1.html -> TS Template A+B wird verwendet
-> ist das ein relevanter use-case?
-> Explizite Limitierung: Templates nur bis FOLDER-Level?!

Alternative:
site
    homepage (page)
    ->TS template A
        main (section)
            text1 (text)

TS Template A:

page = Page
page.body = Template
page.body.source = ...
page.body.sectionName = "body" 
page.parts.XY
page.body.content.sidebar.prototype<Image>.width = "100px" 
# in content sidebar Bilder maximal 100px breit (by default)
page.body.content.sidebar.prototype<TYPO3:Text>.properties.text.value << 1.uppercase()

# Static Template
prototype<TYPO3:Text> = Node
prototype<TYPO3:Page> = Page

# in sidebar den Text "uppercase" machen
http://typo3v5.local/typo3/service/rest/v1/node/live/sites/phoenixdemotypo3org/homepage.html?typoscriptNode=page.body.content.sidebar[text1]
Alternativ (besser):
http://typo3v5.local/typo3/service/rest/v1/node/live/sites/phoenixdemotypo3org/homepage/main/text1.html?typoscriptNode=page.body.content.sidebar

http://typo3v5.local/typo3/service/rest/v1/node/live/sites/phoenixdemotypo3org/homepage/main/text1.html?typoscriptNode=mySpecialTextElementForStandaloneText
# macht Zeile 34-36 obsolet

http://typo3.ietherpad.com/21

• Developing at https://github.com/skurfuerst/TYPO3