• Templating and Integration Guide
  • Part 1: Concepts
    • The "Everything is Content" Paradigm
      • Content items are objects with properties that correspond to a type
      • Nodes are stored in workspaces, organized in trees
    • The rendering flow
      • To render a node, you need a view
      • To render a page, you need a template
    • Modules are packages used to deploy “code” into Jahia
    • The Jahia actors
      • Content flow
  • Part 2: Modules
    • What is a module?
    • Module type
    • Module creation
    • Anatomy of a module
    • Adding classes and Jars in modules
    • Spring files
  • Part 3: Templates and Studio
    • Introduction to templates
    • Studio
      • Studio overview
    • Creating a template-set
      • Using the Maven archetype
      • Using Eclipse
      • Using Jahia Studio
      • Update the Maven project when templates are modified in the Studio
    • Building templates
      • There are 3 different kind of templates
      • Main Resource and template resolution
      • Areas in detail
      • Content templates in details
      • Bound Components
    • CSS style sheets and design
      • Preparing your stylesheet
      • Including stylesheets in templates
      • Managing different stylesheets depending on the context
      • Print friendly CSS
      • CSS frameworks and handmade XHTML
    • Themes
      • How it works
    • Skins
      • Creating skins
      • Skin rendering
  • Part 4: Content Definitions and Views
    • Definitons
      • NodeType
      • Namespaces
      • Supertypes
      • Options
      • Node Type properties
      • Input masks
      • Default values
      • Initializers
      • Validators
      • Abstract types
      • In practice: create the node type definition for dogs
    • Views
      • NodeType folders
      • Output formats
      • Default view
      • Other views
      • Modules versus Components
      • Module packaging and deployement
    • Managing URLs in scripts
    • Managing lists
      • Summary for a simple list
      • Using list views
    • Managing and customizing navigation menus
      • Menu Rendering
      • Customization
  • Part 5: Advanced Techniques
    • Search and queries
      • Full text queries using search tag libraries
      • Queries
      • In practice: creating a custom search component
    • Forms
      • Principles
      • Form data parameters
      • In practice: Transform a custom HTML form into a Jahia valid form step by step
    • Macros
      • Macro implementation languages
      • Typical usage
    • Caches
  • Part 6: Setting up an integration environment
    • Software Requirements
    • Maven configuration for Eclipse IDE
    • Maven External Configuration
    • Creating a template set
  • Part 7: Step by step integration
    • Cutting of the mockup
    • Integration of the Base
    • CSS / Javascript integration
    • Creating the content zones
  • Further reading and resources

Form data parameters

The data submitted in the form uses reserved parameter names to perform their magic. We list here the most important parameters, but please refer to the REST API reference documentation (http://www.jahia.com/community/documentation/jahiapedia/jahia-modules/rest.html) for an exhaustive list.

The parameters are:

• jcrNodeType : type of node to be created
• jcrNodeName : name of node to be created
• jcrNodeNameProperty : by default, if JCRnodeName is not set we use jcr:title to define the node name. This parameter allows changing the property used to define the node name.
• jcrNewNodeOutputFormat : Output format consequent to form post (html, etc ..)
• jcrRedirectTo : URL to be redirected to after the form post 
• jcrRedirectResponseCode: response code to be redirected after form post (useful for json for instance)
• jcrMethodToCall : method to use (post,put,delete) 
• jcrAutoCheckin: forces a new version of the created content
• jcrCaptcha: <input type="text" name="captcha"/> name of the captcha field
• jcrTargetDirectory: for a file upload, this is the target directory
• jcrTargetName : name of the uploaded file
• jcrNormalizeNodeName: (boolean) uses the normalization method for node name creation
• jcrVersion: (boolean) if true creates a new file version, if not replaces the current file
• jcrSubmit:reserved
• jcrAutoAssignRole: name of the role associated to created node
• jcrAlias: reserved
• jcrParentType: type of created parent nodes if they do not exist (by default jnt:contentList)
• jcrReturnContentType: Set to “json” if you want the Content-Type header to be set to application/json otherwise it will default to the default response content-type (usually text/html)
• jcrResourceID: specify the identifier of the currently displayed node to allow the cache system to correctly redisplay the form in case of errors
• jcr:mixinTypes : allows to specify mixins to add to the node being created (must be passed as a multi-valued form data parameter)
• jcrRemoveMixin: removes the specified “mixin” on a node 
• jcrCookieName: name of the cookie for this form, set by the server when the form has been successfully submitted (only when using PUT)
• jcrCookieValue: value of the cookie for this form, set by the server
• jcrCookiePath : path of the cookie for this form, set by the server