Story #44921
Decide TypoScript and TYPO3CR Naming
Status: | Accepted | Start date: | 2012-10-20 | ||
---|---|---|---|---|---|
Priority: | Should have | Due date: | |||
Assigned To: | Sebastian Kurfuerst | % Done: | 33% |
||
Category: | Content Rendering | Spent time: | - | ||
Target version: | Sprint February 2013 | ||||
Story points | - | ||||
Velocity based estimate | - |
Description
As Site Integrator, I want to use consistent TypoScript and TYPO3CR Content Types.
As part of this, the names of content type schema, and the TypoScript properties should be gone through.
List of TODOs:
- https://review.typo3.org/#/c/17510/ (grep for "TODO")
Subtasks
Related issues
History
#1 Updated by Sebastian Kurfuerst over 2 years ago
- Category set to Content Rendering
- Target version set to Sprint February 2013
#2 Updated by Sebastian Kurfuerst over 2 years ago
.. TODO: remove <typo3:aloha.* VHs; and also *.notEditable VHs; as they are not needed anymore .. TODO: introduce PrimaryContentCollection to make hooking into the main content area of a page easier for plugins? {namespace ts=\TYPO3\TypoScript\ViewHelpers} <div class="menu"> <ts:renderTypoScript path="parts/menu" /> </div> <h1>{title}</h1> <ts:renderTypoScript path="sections/main" /> .. TODO: rename "renderTypoScript" VH to "render" .. TODO: should the "renderTypoScript" VH convert the path "." to "/"? .. TODO: explain the (somewhat arbitrary) distinction between parts and sections. .. is that even best practice? In this case, we changed the template paths for *all menus* which do not override the `templatePath` explicitely. Everytime `prototype(...)` is used, this can be understood as: "For all objects of type ..., I want to define *something*" The only thing to be aware of inside the Fluid templates is the proper wrapping of the whole content element with the `<neos:contentElement>` ViewHelper, which is needed to make the content element selectable inside the Neos backend. .. TODO: we could use a processor instead of <neos:contentElement>. Is that better or not? .. TODO: processor ordering: maybe we can also use @position syntax here?? Is it consistent with ordering in TypoScript Collections? .. TODO: naming of the above neos:contentElement viewhelper. ContentElement vs ContentObject (in TYPO3CR Content Type definition) <-- naming .. TODO: how can we add constraints on what types of contents are allowed inside sections? .. TODO: shouldn't the "Image" TypoScript object have an additional property "maxWidth" and/or "maxHeight" .. such that we can adjust the max width/height inside a given context directly? .. TODO: is @override final in regard to the naming? Processors ---------- .. TODO: Processors and eel should be able to work together .. TODO: processor ordering should adhere to @override notation .. TODO: Eel Standard Library - fizzle (TODO: check if syntax is final) (low prio) .. TODO: check how we can transform one content type into another (f.e. 2col .. into 3col) What happens with superfluous structure etc then?
#3 Updated by Sebastian Kurfuerst over 2 years ago
- Status changed from New to Accepted
#4 Updated by Sebastian Kurfuerst over 2 years ago
- Assigned To set to Sebastian Kurfuerst