[Neos] Re: TYPO3.Boilerplate and FluidBuilder naming (domain stuff)

Jacob Floyd cognifloyd at gmail.com
Wed May 29 17:44:53 CEST 2013

After chatting with Sebastian, we came up with these naming things.

Quote: Jacob Floyd (techgurufloyd) wrote on Wed, 29 May 2013 03:17
> These three terms are described in my blog post[1]:
> Boilerplate Packages
> Derivative Packages

We both like this, and think it works well.

> Naked Boilerplates

This name is inconsistent. We need a new name for this concept. RawTemplate? NakedTemplate? ...?

> I'm also not set on the name "FluidBuilder". Would TemplateBuilder be a better name?

TYPO3.TemplateBuilder is a better name.

> Some of my thoughts in general naming conventions are in [2]. That's where I came up with the idea of a general purpose TYPO3.Boilerplate package. What do you think about these naming conventions:
> FooKickstarter
> FooBuilder

Yah. This is how Kickstarter and Builder are used.
Builders will depend on TYPO3.Boilerplate, but Boilerplate packages will depend on the Builders, not on TYPO3.Boilerplate. So, we need a new name for TYPO3.Boilerplate that suggests that Boilerplate is more closely related to Builders than to Boilerplate packages.

Also, within the YAML files, we'll use presets like the FormBuilder uses. But, in the TemplateBuilder UI, we'll call these presets a "Theme" because the word theme makes a lot of sense with Templates, but doesn't make sense in the context of other Builders.

> 1) http://cognifloyd.blogspot.com/2013/05/basic-designs-for-typo3boilerplate.html
> 2) http://cognifloyd.blogspot.com/2013/05/flow-package-types-boilerplate-thoughts.html

More information about the Neos mailing list