Edition: Futurama Website

Module: Futurama Web

User: Developer


- Futurama version 5.3+



The webpages that are created with Futurama consists of two parts: a section and a section. The design of those web applications, which are created with the Futurama Editor, are rendered within the of a webpage. Within the section of a HTML page objects Metatags, Doctype and Scripts files can be defined. From Futurama version 5.3.0 there is a possibility to edit/add these objects. At this page is explained how these headers could be added/adjusted using the FICO functionality. 


Within this example a step by step guide is given on how header objects (Scripts, Metatags, Doctype) could be added/adjusted. The first two steps, explained below, are the basic setup steps to use the FICO functionality.

Configuration – STEP 1

Before adding and/or adjusting HTML headers, a configuration within the web.config is needed.  The following settings must be added to the web.config:


Within the element the next code has to be included:


Next to this code, also within the element the following code should be included:


For a more detailed explanation about these configurations see page: Configuration – Rendering.

Configuration – STEP 2

Creating an extension XSL file

First an empty extension XSLT file should be created. For a detailed explanation on how this should be implemented see paragraph ‘Creating customized XSLT’ at the FICO support page.

Configuration – STEP 3

The last step is actually change or add new HTML header objects. A division is been made into three subparts where each parts is explained individually.

The modifications should be done within the following section:


A more detailed explanation of the "RenderInput" section can be found in the paragraph ‘Structure FICO XML’ at the FICO support page.

IMPORTANT: It is important to note that each adjustment within this RenderInput on node level, should be added in alphabetical order (e.q. root level -> Doctype before Metatags || MetaTag level -> Content before HttpEquiv etc.).


It is possible to add new Metatags. To add new Metatags the following code should be added to the RenderOutput of the extension file:


There are also metatags available which contains a name instead of a HttpEquiv. For example the viewport metatag. Which is a commonly used metatag for optimize a website for mobile devices. From Futurama version 17.2 it is possible to configure these metatags within the extension XSLT:

    width=device-width, initial-scale=1.0    

HTML Result

When adding the above XML example to the extension file the output within the HTML website will be:

As explained earlier, it is important to note that when defining the above XML the alphabetical order is important. Therefore, the "content" node should be defined before the "httpequiv" or the "name" node. In addition, a XSL copy statement is needed otherwise all the other metatags are not rendered.

An implementation example

Adding a new metatag without changing other parts of the RenderOuput should be implemented like this:

					<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "">									  
    						width=device-width, initial-scale=1.0    

Please keep in mind that the metatags containing the name attribute are only available from Futurama version 17.2 and higher


It is possible to add or edit Script files which are rendered within the header of a HTML page. To add a new Script file the following code should be added to the RenderOutput:

Add Script files

Within the "Scripts" RenderOutput a new script could be added by adding a Script node:


To ensure that all the other scripts (that Futurama automatically generates) are loaded the last line of the above XML code should be added. With this setting all the standard Javascript files (as FuturamaScripts.js etc.) are loaded.

Edit Script files

To modify an existing Script as, for example: jQuery, a filter could be added to replace the current script:


Important to note is that whenever the jQuery version is changed, the new version should be placed within the folder that the XML is pointing to. In the above example, within the Scripts map of the Futurama application there must be a jQuery version 1.8.1.min.js available to use.

HTML Result

Using these modifications will result in the following HTML:


As explained earlier, it is important to note that when defining the above XML the alphabetical order is important. Therefore, the "file" node should be defined before the "type" node.


The DocType of the application can also be adjusted within the RenderOutput. To adjust the standard DocType, to for example a new HTML5 doctype, the following adjustment is needed:

					<!DOCTYPE html>

This modification make it possible to change the DocType to a HTML5 DocType. Within the newest version of Futurama (17.2 + ) HTML5 is fully supported. NOTE: To setup an application which should be within a HTML5 format please have a look at the following support page on how to set it up: HTML5 Template

HTML Result

When the Doctype is adjusted the following HTML is visible within the source of the page:


As explained earlier, it is important to note that when defining the above XML the alphabetical order is important. Therefore, the "doctype" node should be defined before the "metatags" and the "metatags" node should be defined before the "scripts" node.

Final code

If all the adjustments, described above, are executed then the extension file will contain the following sections:



											<!DOCTYPE html>

In this segment, it can be seen that this template can be targeted in two modes. One mode where the variable retrievalmode is set to 'html' (this is the default value). The other mode is 'headers', which produces the RenderOutput element, containing the Scripts, MetaTags and DocType information that is included in the headers of a Futurama webpage.

Load external CSS files

From Futurama version 17.2 and higher it is possible to include CSS files within the extension file. A new section within the RenderInput can be created in order to state a reference towards a CSS file:


As stated earlier within this support page, the alphabetic order is very important. As a result, the CSS section should be created before the DocType section:



          <!DOCTYPE html>

Related Topics

- WebAPI Overview: This document explains the WebAPI architecture.


If you have any questions about this subject or if you want to provide us feedback please send us an e-mail.

Updated: 2017-02-06