Adding configuration fields to a typo3 page with fluid / flux

Question

I have setup a site to use flux / FLUIDCONTENT for templates and have it working using the tutorial here: http://thomas.deuling.org/2011/06/create-base-html-fluid-templates-for-

Answer 1

I am afraid, you mix things up a bit.

flux, fluidcontent and (especially important for you) fluidpages play together to extend the default capabilities of creating fluid templates for TYPO3.

• flux Is the base technology for parsing and reconstituting TYPO3 form fields.
• fluidcontent utilizes flux to allow Flexible Content Elements
• fluidpages utilizes flux to allow Page Layouts in pure fluid with custom fields

To summarize: You have read a tutorial concerning basic fluid page templating, but not fluidpages templating. To get you started quickly, there are some examples and documentation resources available:

• The quickstart from the documentation repository
• The speciality provider extension from the bootstrap package (please use with caution-this is an example, not your next project template)
• the extensions fluidcontent_bootstrap and fluidpages_bootstrap

When you are through those resources, you know how to register a provider extension, so that you can select it in the page properties in the backend.

Your template might look something like this (it's actually taken from the aforementioned speciality extension):

 
{namespace v=Tx_Vhs_ViewHelpers}
{namespace flux=FluidTYPO3\Flux\ViewHelpers}



    

        

            
            
            
            
            

            
            
                
                    
                
            
        
    

    
        

            

                
                
                    
                
            
        
    

Most flux templates (regardless wether fluidpages or fluidcontent) are split up into (at least) 3 f:section fluid sections:

• Configuration takes your form fields
• Preview influences how your template is being previewed in the backend
• Usually Content or Main (you can influence the naming, in your Layout files but should stick to the conventions we spread accross the example extensions) renders your FCE/Page template

The field items are usable by accessing them via their name attribute as getter. To illustrate this, you could access {settings.carousel.caption} from inside the page template above.