Frequently Asked Questions
Learn about frequently asked questions for Pantheon's decoupled architecture using Front-End Sites.Discuss in our Forum Discuss in Slack
Frequently Asked Questions
Can I use any CMS with Pantheon architecture for Front-End Sites?
WordPress and Drupal are currently the only CMSs supported by Pantheon Decoupled.
What dependency versions are supported with Front-End Sites?
Pantheon Front-End Sites currently supports:
- Gatsby v4
- Next.js v12
- Drupal 9 or higher
- WordPress 5.9
Is Decoupled Site Preview available for all instances on Front-End Sites?
Decoupled Site Preview is only available for sites using Next.js as a front-end framework.
Can I Use Cloudflare with Front-End Sites?
Yes. You can configure Cloudflare's CDN as an additional layer on Pantheon's Global CDN service. You must follow the Option 2 instructions outlined in the Cloudflare Domain Configuration documentation.
Is Multi-Region Failover available with Front-End Sites?
Multi-Region Failover and Pantheon's Multizone Failover are only available for General Availability.
A repository can only be associated with one Front-End Site
A repository can only be associated with one Front-End Site at a time. You will receive an error message if you attempt to connect a repository to two or more sites.
Builds are only available for Gatsby and Next.js
Builds will only complete for repositories that are detected as Gatsby or Next.js repositories. Builds for all other frameworks will fail.
Gatsby does not support SSR and DSG
Server-side Rendering and Deferred Static Generation (DSG) for Gatsby v4 are currently not supported.
Manual support is required
Manual support is required for domain and DNS setup.
Preview functionality is not supported for Gatsby
Preview functionality is not currently supported for Gatsby. Currently, it is only available for Drupal sites.
Renaming a linked repository in GitHub will cause a break in your decoupled experience.
Renaming a linked repository in GitHub is not recommended, as it will cause a break in your decoupled experience. In the event a user renames an attached Git repository on GitHub and disconnects the Git repository and attaches the renamed site, this will trigger a false live-build and the Decoupled site will be in a persistent build log state that cannot be canceled. To fix this issue, disconnect the renamed Git repository and revert to the original name. This action will instantly restore all data. Renaming the Git repository on GitHub to the original name should fix the build process.
Select files can cause build errors
Select files, such as `.dockerignore` and `.gcloudignore` files can cause build errors or failed builds. Removing these files from source and adding them to `.gitignore` solves the issue.
Users must have permissions to enable decoupled for GitHub organization accounts.
Users must have permissions to enable Front-End Sites for GitHub organization accounts. The user should be the Owner of the account. GitHub organization owners can allow other users to manage the Pantheon GitHub application on their behalf.
You must remove a VCS user record to uninstall a Front-End Site
Uninstalling a Pantheon Front-End Site using GitHub settings requires manual removal of a VCS user record.