Using Instant Websites
Enabling Instant Websites for a Confluence Space
Space Administrators can access 'Instant Websites' via Space Tools -> Integrations:
Enable Instant Websites for a Space
Space Administrators can enable Instant Websites for their space. You will be asked for the URL of the publicly accessible address, for example docs.glintech.com.
Point the public domain to Instant Websites
Once Instant Websites is enabled for a space we provide a domain name where the static content is stored, for example docs.glintech.com.s3-website-us-east-1.amazonaws.com.
To host this website on your own domain (e.g. docs.glintech.com), you'll need to update or create a CNAME with your DNS provider and point that to the Instant Websites hostname.
A CNAME is an alias from one domain name to another. It allows us to host your website on Amazon S3 (super fast), and have it load from on domain name. You can read more here. Since the sites are hosted on AWS S3, your hostname should be the DNS compliant hostname that you eventually want to be able to access your site from. To understand more about the technical behaviour of this, take a look at Amazon's S3 documentation.
Configuring the Instant Website
Upload the logo of your choice. By default the logo will be displayed at 40 pixels high on a white background. You can change the header background colour to match the logo background colour with Custom CSS (below). It is recommended you resize your logo to be 80 pixels high to render well on retina screens, and ensure the logo is less than 40KB.
You've got complete control of how the Instant Website looks via Custom CSS. See Customer Examples for inspiration.
Add additional analytics codes or your own actions and behaviour using Custom JS.
Add a Google Analytics site ID to the Instant Website to track usage, popular pages and referrals.
You can work on drafts privately by restricting permissions to a group, for instance 'employees'. The Instant Websites service account will not be able to see the page and as such won't publish it to the website.
The behavior is the same with regular per-user drafts - as they are not published on Confluence they are not visible on the website. Although in this scenario you can not collaborate with others as the drafts are private to one user.