Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove FES banner #9360

Merged
merged 1 commit into from
Dec 30, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 0 additions & 8 deletions source/content/static-site-empty-upstream.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,14 +14,6 @@ integration: [upstreams]
---


<Alert title="Better solution available: Front-End Sites" type="danger">

This documentation page describes how to host a static site using Pantheon's infrastructure that was designed for CMS sites. Since this page was written, Pantheon has developed a new offering called [Front-End Sites](/guides/decoupled) that is specifically designed for running sites with static site generators (and server-side rendered front-end frameworks).

We keep this page of documentation present for customers who had already set up a static site on Pantheon using the method described here. However, we recommend that new customers use Front-End Sites for hosting static sites on Pantheon.

</Alert>

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](/guides/support/) applies: Pantheon Support will help diagnose and remedy platform-related issues, but cannot resolve code-related issues.
Expand Down
Loading