New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Use WordPress as your CMS, then publish a fast, lower-exposure static version of your site. | You have to log in to add a translation. | Details |
Original untranslated
Use WordPress as your CMS, then publish a fast, lower-exposure static version of your site.
You have to log in to edit this translation. |
|||
| ↑ | Staatic - Static Site Generator for WordPress | You have to log in to add a translation. | Details |
Original untranslated
Staatic - Static Site Generator for WordPress
CommentPlugin name. You have to log in to edit this translation. |
|||
| For commercial support, Staatic Premium, or Staatic Cloud questions, you can also <a href="proxy.php?url=https%3A%2F%2Fstaatic.com%2Fwordpress%2Fcontact%2F">contact us</a>. | You have to log in to add a translation. | Details | |
Original untranslated
For commercial support, Staatic Premium, or Staatic Cloud questions, you can also <a href="proxy.php?url=https%3A%2F%2Fstaatic.com%2Fwordpress%2Fcontact%2F">contact us</a>.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Large sites, slow origins, strict firewalls, disabled loopback requests, or very limited PHP execution time can require tuning. The Site Health checks, publication logs, and advanced settings are the best starting points if a publication does not start or takes too long. | You have to log in to add a translation. | Details | |
Original untranslated
Large sites, slow origins, strict firewalls, disabled loopback requests, or very limited PHP execution time can require tuning. The Site Health checks, publication logs, and advanced settings are the best starting points if a publication does not start or takes too long.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Staatic is designed to work on typical WordPress hosting, including many shared hosting environments. The server must be able to write to the configured work directory and make HTTP requests to the WordPress site being published. | You have to log in to add a translation. | Details | |
Original untranslated
Staatic is designed to work on typical WordPress hosting, including many shared hosting environments. The server must be able to write to the configured work directory and make HTTP requests to the WordPress site being published.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| For forms and search, Staatic Premium provides ready-made integrations. For other dynamic features, use a static-compatible service, client-side integration, or a hybrid architecture where needed. | You have to log in to add a translation. | Details | |
Original untranslated
For forms and search, Staatic Premium provides ready-made integrations. For other dynamic features, use a static-compatible service, client-side integration, or a hybrid architecture where needed.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Common examples include native comments, some search implementations, forms that post back to WordPress, eCommerce flows, membership areas, and plugins that fetch personalized server-side data. | You have to log in to add a translation. | Details | |
Original untranslated
Common examples include native comments, some search implementations, forms that post back to WordPress, eCommerce flows, membership areas, and plugins that fetch personalized server-side data.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Not entirely. Static sites do not run WordPress, PHP, or database queries for each visitor request. Plugins that depend on server-side processing on the public site may need changes or alternatives. | You have to log in to add a translation. | Details | |
Original untranslated
Not entirely. Static sites do not run WordPress, PHP, or database queries for each visitor request. Plugins that depend on server-side processing on the public site may need changes or alternatives.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| You still need to maintain your WordPress origin, themes, plugins, accounts, and deployment credentials. The main security benefit is architectural: fewer dynamic systems are involved in serving anonymous public traffic. | You have to log in to add a translation. | Details | |
Original untranslated
You still need to maintain your WordPress origin, themes, plugins, accounts, and deployment credentials. The main security benefit is architectural: fewer dynamic systems are involved in serving anonymous public traffic.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| In a private-origin, public-static setup, visitors do not hit <code>wp-login.php</code>, plugin PHP code, or database-backed page generation on the public site. This reduces the blast radius of many common WordPress risks, including plugin runtime vulnerabilities, automated login probing, and server-side behavior that only exists while WordPress is serving each request. | You have to log in to add a translation. | Details | |
Original untranslated
In a private-origin, public-static setup, visitors do not hit <code>wp-login.php</code>, plugin PHP code, or database-backed page generation on the public site. This reduces the blast radius of many common WordPress risks, including plugin runtime vulnerabilities, automated login probing, and server-side behavior that only exists while WordPress is serving each request.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Static delivery reduces the amount of WordPress infrastructure exposed to public visitors. Your public site can be served as files, while WordPress remains the authoring environment behind the publication workflow. | You have to log in to add a translation. | Details | |
Original untranslated
Static delivery reduces the amount of WordPress infrastructure exposed to public visitors. Your public site can be served as files, while WordPress remains the authoring environment behind the publication workflow.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If the static version differs, the cause is usually frontend behavior that depends on server-side requests, invalid HTML, blocked assets, authentication, or plugin/theme output that behaves differently while being crawled. The publication resources and logs can help identify what was captured and what failed. | You have to log in to add a translation. | Details | |
Original untranslated
If the static version differs, the cause is usually frontend behavior that depends on server-side requests, invalid HTML, blocked assets, authentication, or plugin/theme output that behaves differently while being crawled. The publication resources and logs can help identify what was captured and what failed.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| No, it should not. Staatic publishes the output that WordPress already renders for visitors. | You have to log in to add a translation. | Details | |
Original untranslated
No, it should not. Staatic publishes the output that WordPress already renders for visitors.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Staatic changes the architecture: the public site is a deployed set of static files. You can host those files on your own server, object storage, a static hosting provider, or a CDN-backed setup, depending on the deployment method you choose. | You have to log in to add a translation. | Details | |
Original untranslated
Staatic changes the architecture: the public site is a deployed set of static files. You can host those files on your own server, object storage, a static hosting provider, or a CDN-backed setup, depending on the deployment method you choose.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Caching plugins can be useful, but the public request still usually reaches WordPress infrastructure. Cache misses, cache purges, plugin behavior, and origin capacity can still affect visitors. | You have to log in to add a translation. | Details | |
Original untranslated
Caching plugins can be useful, but the public request still usually reaches WordPress infrastructure. Cache misses, cache purges, plugin behavior, and origin capacity can still affect visitors.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.