Pantheon supports two of the largest open source content management systems (CMS) on the web, WordPress and Drupal. Occasionally, when customers move their portfolio of sites over to Pantheon, some sites are static and do not need a full CMS, and this is where empty Upstreams come in.
The usual Scope of Support applies: Pantheon Support will help diagnose and remedy platform-related issues, but cannot resolve code-related issues.
This process assumes you already have a static site developed and that you have access to the files. For more information about dependencies and which files to upload, consult the documentation for the static site generator you use.
Commonly, an empty Upstream is used as part of a Build Tools setup. In this doc, we use it to host static HTML or PHP sites.
Via the Pantheon Dashboard:
- Use the Empty Site Upstream
terminus site:create my-new-site "My New Site" empty
Once the files have been added to the Site, commit the code, and deploy the changes through Test to Live.
Yes! You can start a new static site using an empty Upstream.
Yes, you can commit any static HTML file to your site that is unrelated to the CMS.
If you would like the path to have a clean URL (for example,
example.com/page-name.html), the HTML file should be an
index.html file in a directory of the desired path name.
This example directory structure shows a WordPress site that contains a static landing page located at
│ ├── index.php
│ ├── mu-plugins/
│ ├── plugins/
│ ├── themes/
│ └── uploads/
└── landing-page ├── index.html ├── assets/ ├── css/ └── js/
An empty Upstream, behind the scenes, is essentially an empty Drupal environment. All of the tools available to the Site Plan will be available. But, if you are only using static HTML, tools like Redis and New Relic are not utilized as no requests are being processed by PHP.
Yes, traffic will be counted the same way. Refer to our Traffic Metrics documentation for more information.
Yes, compiled static sites that don't require a Drupal or WordPress CMS backend can be hosted on Pantheon using this method.
Some customers utilize a two-site approach on Pantheon where one site is the CMS backend (headless WordPress or Drupal), and the other site is the decoupled frontend (Frontity, Gatsby, etc.). Of course, you will likely have different deployment workflows for updating each site, and you would need to determine the best workflow for you and your team.
For other Decoupled configurations, please refer to our Decoupled Sites documentation.