Story #8787

As Klaus I want to add new content elements to a website

Added by Daniel Poetzinger over 9 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

25%


Description

Drag and Drop from the view area to the page


Subtasks

TYPO3.Neos - Task #12104: Create Photoshop design for add-new-content elementClosed

TYPO3.Neos - Task #11200: Auto-create text element after creating new pageResolved

TYPO3.Neos - Task #12366: Make content type names localizableResolvedRens Admiraal

TYPO3.Neos - Task #11327: Disabled Aloha on the actual website (outside the UI) even when a user is logged inResolved

TYPO3.Neos - Task #11990: Make it possible to render a given node on its ownResolvedSebastian Kurfuerst

TYPO3.Neos - Task #11156: Create technical concept for content element handlingResolvedRobert Lemke

TYPO3.Neos - Task #12370: Create placeholders if contenteditable is emptyResolvedSebastian Kurfuerst

TYPO3.Neos - Task #12368: Implement moving of nodesResolvedChristian Müller

TYPO3.Neos - Task #12696: Style content placeholdersResolvedSebastian Kurfuerst

TYPO3.Neos - Task #12363: Aloha should have buttons to insert new content elementsResolvedSebastian Kurfuerst

TYPO3.Neos - Task #11220: Explore technical possibilities for add-new-content-element in AlohaResolvedChristian Müller

TYPO3.Neos - Task #11176: Implement content type registration mechanism (e.g. ContentTypes.yaml)Closed

History

#1 Updated by Sebastian Kurfuerst about 9 years ago

  • Project changed from 1204 to Core Team

#2 Updated by Daniel Poetzinger about 9 years ago

  • translation missing: en.field_position deleted (9436)
  • translation missing: en.field_position set to 5440

#3 Updated by Robert Lemke almost 9 years ago

  • Target version set to 732
  • translation missing: en.field_position deleted (5446)
  • translation missing: en.field_position set to 5

#4 Updated by Sebastian Kurfuerst almost 9 years ago

  • Target version changed from 732 to 788
  • translation missing: en.field_position deleted (15)
  • translation missing: en.field_position set to 2

#5 Updated by Sebastian Kurfuerst almost 9 years ago

  • translation missing: en.field_position deleted (2)
  • translation missing: en.field_position set to 9

#6 Updated by Robert Lemke almost 9 years ago

  • translation missing: en.field_position deleted (12)
  • translation missing: en.field_position set to 14

#7 Updated by Sebastian Kurfuerst almost 9 years ago

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

#10 Updated by Robert Lemke over 8 years ago

  • Project changed from Core Team to Base Distribution
  • Target version deleted (788)

#11 Updated by Robert Lemke over 8 years ago

  • Target version set to Sprint 7
  • translation missing: en.field_position deleted (17924)
  • translation missing: en.field_position set to 5

#12 Updated by Sebastian Kurfuerst about 8 years ago

  • Status changed from New to Closed

Bulk-closing issues because they are

  • not relevant anymore due to the sproutcore based backend
  • or already implemented in the meantime.

Regards, Sebastian

Also available in: Atom PDF