To make Top Bar component more easy to use, by default it could have set values:

• Top Bar Title: Home
• Top Bar section align: right
• checked Contain to grid

Top Bar should support dropdown_autoclose and is_hover options - see http://foundation.zurb.com/docs/components/topbar.html

Image NodeType is already defined in Neos - we need to make sure all util/helper classes are applied to image where necessary.

• implement .th class for thumbnails
  In Foundation, there's extra class .th for images to make them look like thumbnail.

http://foundation.zurb.com/docs/components/thumbnails.html

We should make it available from Neos.

Currently Orbit Slider doesn't work at all, throwing an exception.

Attributes set by user in the inspector (ie. custom css class, custom id, inline styles) are not applied to some components. This is caused by re-factoring, when we started rendering them using TYPO3.TypoScript:Tag instead of TYPO3.Neos:Content where these attributes are defined.

Idea: expose it as a static/dummy element. Useful only for visualisation / prototyping purposes.

http://foundation.zurb.com/docs/components/offcanvas.html

Idea: can be exposed as a Node Type and/or configurable plugin

Add contextual help messages for new content dialogue window and Inspector (feature available likely in Neos 2.1).

BlockGrid currently works fine, but we should get rid of these nasty hacks with condition/iterators as we did in Tabs/Orbit.

PS. We need to make sure we won't hit the issue described in #23 - I think this is why initially we used these hacks. Currently, with these hacks it works fine.

Each Neos node can be changed/migrated into another type. Currently we do not set the baseNodeType option for that _nodeType property (which has NodeTypeEditor). As an effect, each node can be migrated to any content node...

To make it more intuitive, we could set baseNodeType to some parent abstract node type, so the list is shorter and more sensible.

Top Bar could be build as a Content Collection with SubNav inside (by default).

That would allow inserting extra things into Top Bar, ie. dividers, more sections, form components. As presented in the doc.

We could simply parse FontAwesome _variables.scss which contains lists of available icons and show them in select box to choose.

When you change referenced node(s), content rendered by Content References is not updated.

TYPO3.Neos.NodeTypes:ContentReferences does NOT have any @cache entry… But I guess it would have to have it, moreover, with some rules to invalidate it when referenced nodes have changed (i.e. nodes listed in TYPO3.Neos.NodeTypes:ContentReferences.properties)?

While in CC in Tabs, you can add 1st content (when the handle has default position inside).
Then try to add another content (now the position will be after) and you'll get
Uncaught TypeError: Cannot read property 'options' of undefined InsertNodePanel.js:48

Note: adding it via structure tree panel works.

See the screenshots for details

It seems to be possible now, with this change: https://review.typo3.org/#/c/31244/

For example, instead of having a M12.Foundation:GridRow, which contains M12.Foundation:Column (with column settings, e.g. column width, etc), which then contains ContentCollection with column conent, it would be better to have ContentCollection with column settings directly under M12.Foundation:GridRow.

See http://foundation.zurb.com/docs/components/forms.html
Pre/Postfix Labels & Actions section.

Classes prefix-radius or prefix-round has to be applied to Grid Row to have pre/postfix labels with radius/rounded.

For each item in accordion template we should check if item property 'isAccordionItemActive' is set to TRUE, and if yes <li class="accordion-navigation"> element should get class 'active'.

The error:

Element dl is missing a required child element.
Content model for element dl:
Zero or more groups each consisting of one or more dt elements followed by one or more dd elements, optionally intermixed with script-supporting elements.

Via Inspector user can provide custom inline CSS for majority of M12.Foundation components.

When in raw edit mode, these styles should be ignored / not set.

Currently we only have .text-[align] classes in M12.Foundation:AbstractGenericHelpers for classTextAlign property.

This property should be made an array type with ability to select couple of values here.

We need to extend this list with all responsive class names, ie. .small-only-text-left, .small-text-left, .medium-text-left etc, as listed on http://foundation.zurb.com/docs/utility-classes.html

Normally CC overlay disappears when when some content is inserted into it. But not in tabs... ;) See the screenshot.

I think we introduced it when we refactored it in 69c6e09 change.

https://www.dropbox.com/s/rg6t4dhtcnfwnr5/Screenshot%202015-07-20%2023.04.31.png?dl=0

asdfas dfasdfa

There should be Upgrade section in README.md file with detailed description how to upgrade to latest version from older one. For example upgrade from 0.2 => 1.x.

Such upgrade instruction should contain command that will change package version in composer.json, command to update composer packages, command to flush cache (for Development and Production context), command to run node migration as it is required.

As a user, I want to add grid with X column
and have default column width set.

For example. adding 2-col grid, I'd expect to have column sizes set to 6/12 on these 2 columns, so they are rendered correctly right after being added.

Home link in TopBar NodeType always links to default dimension because href attribute is hardcoded to '/'. We should use neos viehelper to link to root node in current dimensions. There are 2 options:

<neos:link.node node="~">text</neos:link.node>
or
<neos:link.node node="{site}">text</neos:link.node>

TopBar NodeType can be used in various ways. When inserted into ContentCollection we can set (or not) home link text through inspector. When this value is empty than link is not generated and this is fine.

Problem is when we define TopBar as a childNode. For example:

'TYPO3.Neos.NodeTypes:Page':
  childNodes:
    navigation:
      type: 'M12.Foundation:TopBar'

now the Home link is always generated because of this condition in TypoScript (Resources/Private/TypoScript/Prototypes/Navigation.ts2):

topBarTitle = ${isDocumentContext ? q(site).property('title') : q(node).property('topBarTitle')}

(page title is always set and we are in Document context).

Maybe some checkbox in element inspector would be a better option do define if we want or not Home link in TopBar?

We need to do complete revision of all components and make them working with content cache in Neos.

http://foundation.zurb.com/docs/components/inline_lists.html

The topic extendable-contentcollections has been merged and M12.Foundation needs to be adjusted to that, esp. for missing content-collection CSS class in ContentElementWrappingService.

http://foundation.zurb.com/docs/components/labels.html

Continuation of #27, where dropdowns were left not fixed.

The main purpose of using accordion is to hide each item content. At the moment if we add new item it's property "Make the accordion item active" is checked by default and it forces us to click on it each time we want to disable it.

I think in most cases only one item will be active so it would be much better to make the mentioned option disabled by default. Thanks! :)

When you insert Block Grid, then inside Container, and then inside Headline, something is going wrong.

The Headline disappear after Neos interface is fully initialised and it's not editable.

Same issue as #23

http://foundation.zurb.com/docs/components/switch.html

Problem: currently all Utility Classes and Show/Hide Classes are attached to TS attributes and therefore they are applied to INPUT element.

We need to change it and they should be inserted into extraAttributes obj and applied to parent LABEL.