pixelbrackets

<f:if condition="{node.context.workspace.name} == 'live'">
	Only visible in live frontend
</f:if>

<f:security.ifAccess privilegeTarget="TYPO3.Neos:Backend.GeneralAccess">
	<f:if condition="{node.context.workspace.name} != 'live'">
		Only visible in backend workspace
	</f:if>
</f:security.ifAccess>

dimaip

<?php
namespace Sfi\Migration\Command;

/*                                                                        *
 * This script belongs to the TYPO3 Flow package "Sfi.Migration".         *
 *                                                                        *
 *                                                                        */

use TYPO3\Flow\Annotations as Flow;
use TYPO3\Flow\Cli\CommandController;

plentz

# to generate your dhparam.pem file, run in the terminal
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048

bwaidelich

<?php
namespace My\Package\Service;

use TYPO3\Flow\Annotations as Flow;

/**
 * @Flow\Scope("singleton")
 */
class EmailService {

manuelmitasch

Context

In the Google Summer of Code Project "TYPO3 Flow meets Ember.js" we are trying to make the server-side framework TYPO3 Flow and the client-side framework Ember.js (using Ember Data as the persistence layer) work together easily through conventions and a powerful scaffolding mechanism. You can visit our website to see a more detailed concept.

Please refer to the overview gist that gives a brief overview of how things should work together.

Feedback wanted: Automagical controller vs. generated controllers