[TYPO3-english] Busy Noggin framework

Jigal van Hemert jigal at xs4all.nl
Sun Jun 26 20:00:40 CEST 2011


Hi,

On 26-6-2011 17:22, Erick Paquin wrote:
> Anybody sees a disadvantage of using this framework?
>
> http://templavoila.busynoggin.com/

It has some properties which might not fit your needs or your way of 
working.

The situation where this framework excels the most is if you are a 
talented HTML/CSS builder, your site(s) are relatively simple in 
structure and if the templates it provides are enough for your needs.

The usual way of working with for example automaketemplate or 
templavoila is that you have an HTML template and map some parts to 
contain generated content (content elements in a page or Typoscript).

With this 'framework' you work the other way around. There is already a 
collection of page templates (with header, feature, fontent and footer). 
This defines the overall structure; your task is to provide the HTML 
templates for extensions, the HTML in the Typoscript content (menus, 
etc.) and the CSS to make it look like the design.

You can change the standard configuration, but this requires tinkering 
with the Typoscript of the framework. Sometimes you cannot 'wrap' parts, 
but you have to split this 'wrap' and add the first half to a 
before-property and the second half to an after-property (easy to lose 
track of the separated parts IMO).

If you are -- like Ron Hall -- more a designer / HTML / CSS person, this 
framework can help you implement a certain design very quickly. If you 
rely on your frontend designer to hand you the HTML / CSS one of the 
more traditional approacher will suite you better.
If your site has a complex structure, if you have a lot of special 
content then the time you spend with normal templating is only a small 
part of the total development time. In this case you won't have much 
benefit from this framework and it might actually work against you.

If the backend layout does not suite you (colour, behaviour, limited 
sized content elements, etc.) you would also have to spend a lot of time 
customizing the backend. With the backend layouts of the plain vanilla 
TYPO3 installation and the backend layouts of Templavoila you can 
already make the backend look a lot like the frontend.

-- 
Kind regards / met vriendelijke groet,

Jigal van Hemert.


More information about the TYPO3-english mailing list