links to different areas/functionalities of the site. • a footer with generic informations like web master’s email, the company address, etc… • a content area which usually contains the functional part of inheritance also to HTML markup making layout management much easier and less error-prone. Defining a master template page to use as base class for the other pages is a great way to build a consistent layout discussed in paragraph 12.6). In this chapter we will continue to explore Wicket forms learning how to master them and how to build effective and user-proof forms for our web applications. 12.1. Default form

links to different areas/functionalities of the site. • a footer with generic informations like web master’s email, the company address, etc… • a content area which usually contains the functional part of inheritance also to HTML markup making layout management much easier and less error-prone. Defining a master template page to use as base class for the other pages is a great way to build a consistent layout discussed in paragraph 12.6). In this chapter we will continue to explore Wicket forms learning how to master them and how to build effective and user-proof forms for our web applications. 12.1. Default form

links to different areas/functionalities of the site. • a footer with generic informations like web master’s email, the company address, etc… • a content area which usually contains the functional part of inheritance also to HTML markup making layout management much easier and less error-prone. Defining a master template page to use as base class for the other pages is a great way to build a consistent layout discussed in paragraph 12.6). In this chapter we will continue to explore Wicket forms learning how to master them and how to build effective and user-proof forms for our web applications. 12.1. Default form

links to different areas/functionalities of the site. • a footer with generic informations like web master’s email, the company address, etc… • a content area which usually contains the functional part of inheritance also to HTML markup making layout management much easier and less error-prone. Defining a master template page to use as base class for the other pages is a great way to build a consistent layout discussed in paragraph 12.6). In this chapter we will continue to explore Wicket forms learning how to master them and how to build effective and user-proof forms for our web applications. 12.1. Default form