Though we have not released it to the TER, we do have TVFW version 2 available.
It does work with TYPO3 6.2. We have used it on our customer sites.

Here is the extension manual which has a link to the GIT repo with the code for version 2.
You should use the develop branch.

You can use version 1 skins with version 2, but will need to add one constant to the skin (detailed in manual).



You will never be able to design sites quickly and with consistent quality unless you standardize your approach and your code (HTML, CSS, JavaScript, TypoScript, data structures, and template objects).

However, standardization does not have to mean bland, limited visual design. Two websites can have radically different visual designs and yet be based on standardized code. See CSS Zen Garden as an example of what can be done visually to identical HTML code with just CSS.

Easier Maintenance

Standardizing code and approach also means that you know exactly where to go when enhancing a site that you completed long ago.

Mapping Blocks vs. Elements  >>


Standardization: A Journey, Not a Destination

The code standardization in this framework includes consistency in:

  • HTML structure.
  • Naming (id's, CSS classes, field names, etc.)
  • Template datastructure construction

Although not technically code standardization, consistency is also found in the use of Utility FCEs to handle common layout needs from site to site.

Is the code perfectly consistent? No.

For instance, I prefer to use camel case when formatting my Typoscript objects, CSS, JavaScript, etc. However, I found that Safari returns class names to the RTE as all lowercase, so in the RTE stylesheet I make CSS classes lowercase

The bottom line is that, within this framework, standardization is seen as a journey not a destination. Code and approach will be refined and become more consistent over time, but will never be perfect.