Visualforce Developer Guide
jNewer Version Available
Creating an Empty HTML5 “Container” Page
You use Remote Objects, JavaScript remoting, or other Lightning Platform APIs to make service requests and then render the results with JavaScript.
1<apex:page docType="html-5.0" applyHtmlTag="false" applyBodyTag="false"
2 showHeader="false" sidebar="false" standardStylesheets="false"
3 title="Unused Title">
4<html>
5
6 <head>
7 <title>HTML5 Container Page</title>
8 </head>
9
10 <body>
11 <h1>An Almost Empty Page</h1>
12
13 <p>This is a very simple page.</p>
14 </body>
15
16</html>
17</apex:page>- docType="html-5.0" sets the page to use the modern HTML5 docType.
- applyHtmlTag="false" and applyBodyTag="false" tell Visualforce that your markup supplies the <html> and <body> tags so that it doesn’t generate its own.
- The showHeader="false", sidebar="false", and standardStylesheets="false" attributes suppress the standard header, sidebar, and style sheets that add the Salesforce user interface and visual design to Visualforce pages. It also suppresses JavaScript resources, like scripts that aid with redirects on session timeout.
The <head> tag isn’t required in a container page, but it’s a good idea to include it. If you must add values to the <head> element, you must add the <head> tag yourself. In that case, Visualforce adds any of its required values to your <head>. Otherwise, Visualforce renders its own <head> to add any necessary values.
You can use Visualforce components, such as <apex:includeScript>, <apex:stylesheet>, and <apex:image>, to reference static resources on the page. The output of <apex:includeScript> and <apex:stylesheet> is added to the <head> element. If you didn’t include one, Visualforce adds its own. The <apex:image> output is rendered wherever you place it on the page.