Publishing, Staging, and Go-Live

Publishing

Publishing an individual page or the entire site will process and include all necessary styles, scripts, integrations and feeds into each individual page and then minify that code and markup. Minifying the code helps reduce the size of your pages so they use less bandwidth and load faster.

All publishes go to the staging site

The staging site enables you to have a publicly available staging site so that you and your clients can verify the entire site in it's published state before going live on your domain.

Go Live

When you "Go Live" you are copying all of the files in the staging site to the live site in one fast action.

Differences between staging and live site

The major difference between the staging site and the live site is the domain that the site is available on. There are no differences in the actual page markup and the sites will be identical. The staging site's robots.txt file disables any indexing and the live site uses the real robots.txt file that allows all indexing and conforms to any settings related to that file.


Absolute vs Relative URL:

An absolute URL includes the protocol (http:// or https://) and the domain name and a relative URL does not.


An example absolute URL: https://www.blux.com/support

An example relative URL: /support


For the most part, Blux uses relative url's and your staging and live site will operate as indented. There may be some scenarios where 3rd party integrations, feed automation or user defined links and url's use the absolute URL. In this scenario the staging site may have links that point to the live site. If this happens you can simply change the domain from the live domain to the staging domain in your browser to validate that page on the staging site.

STILL HAVE QUESTIONS?

Let's Chat