New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Staatic - Static Site Generator | Staatic - Static Site Generator | Details |
Original current |
|||
| ↑ | Staatic lets you create and deploy a streamlined static version of your WordPress site. | Staatic stelt je in staat om een gestroomlijnde statische versie van je WordPress site te maken en te implementeren. | Details |
Original current
Staatic lets you create and deploy a streamlined static version of your WordPress site.
CommentShort description. You have to log in to edit this translation. |
|||
| Staatic offers broad compatibility, only requiring the permissions to write to the working directory and to initiate an HTTP connection with your dynamic WordPress installation. | Staatic biedt brede compatibiliteit en vereist enkel rechten om naar de werkmap te schrijven en om een HTTP verbinding te initiëren met je dynamische WordPress installatie. | Details | |
Original current
Staatic offers broad compatibility, only requiring the permissions to write to the working directory and to initiate an HTTP connection with your dynamic WordPress installation.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Staatic lets you create and deploy a streamlined static version of your WordPress site, enhancing performance, SEO, and security simultaneously. | Staatic stelt je in staat om een gestroomlijnde statische versie van je WordPress site te maken en te implementeren, waardoor de prestaties, SEO en beveiliging tegelijkertijd worden verbeterd. | Details | |
Original current
Staatic lets you create and deploy a streamlined static version of your WordPress site, enhancing performance, SEO, and security simultaneously.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Staatic transforms your dynamic WordPress site into a streamlined static site. Starting at the homepage or a designated URL, Staatic uses a web crawler to methodically navigate through every link, post, and page. As it moves through the site, dynamically generated content is captured and converted into static HTML files, while simultaneously fetching related assets like images and scripts. | Staatic transformeert je dynamische WordPress site in een gestroomlijnde statische site. Beginnend bij de homepage of een aangewezen URL gebruikt Staatic een web crawler om methodisch door elke link, elk bericht en elke pagina te navigeren. Terwijl het door de site beweegt, wordt dynamisch gegenereerde inhoud vastgelegd en omgezet in statische HTML bestanden, terwijl tegelijkertijd gerelateerde bestanden zoals afbeeldingen en scripts worden opgehaald. | Details | |
Original current
Staatic transforms your dynamic WordPress site into a streamlined static site. Starting at the homepage or a designated URL, Staatic uses a web crawler to methodically navigate through every link, post, and page. As it moves through the site, dynamically generated content is captured and converted into static HTML files, while simultaneously fetching related assets like images and scripts.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Not entirely. When your site undergoes conversion to a static format, dynamic server-side functionalities become unavailable. As a result, plugins relying on these features – such as those processing forms or fetching external data – might not function immediately or might be unsupported altogether. | Niet volledig. Wanneer je site wordt omgezet naar een statisch format, worden dynamische server-side functionaliteiten onbeschikbaar. Als gevolg hiervan kunnen plugins die op deze functies vertrouwen – zoals die voor het verwerken van formulieren of het ophalen van externe gegevens – mogelijk niet direct functioneren of helemaal niet ondersteund worden. | Details | |
Original current
Not entirely. When your site undergoes conversion to a static format, dynamic server-side functionalities become unavailable. As a result, plugins relying on these features – such as those processing forms or fetching external data – might not function immediately or might be unsupported altogether.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Caching plugins boost site performance by storing data for quicker access, yet they don’t fully bypass WordPress, introducing some latency. Additionally, after every update, these plugins need cache prewarming to serve the first requests quickly. In contrast, static sites are always ‘warmed up’, ensuring consistently rapid load times. | Caching plugins verbeteren de prestaties van de site door gegevens op te slaan voor snellere toegang, maar ze omzeilen WordPress niet volledig, wat enige vertraging introduceert. Bovendien hebben deze plugins na elke update cache 'warm up' nodig om de eerste aanvragen snel te kunnen verwerken. Daarentegen zijn statische sites altijd 'voorverwarmd', wat zorgt voor consistent snelle laadtijden. | Details | |
Original current
Caching plugins boost site performance by storing data for quicker access, yet they don’t fully bypass WordPress, introducing some latency. Additionally, after every update, these plugins need cache prewarming to serve the first requests quickly. In contrast, static sites are always ‘warmed up’, ensuring consistently rapid load times.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| By converting your site into static HTML pages, you substantially minimize the potential attack surface. This strengthens your website’s security and reduces the ongoing need to update WordPress, its plugins, and themes constantly. As a result, you can enjoy greater peace of mind, knowing your site is resilient to most threats. | Door je site om te zetten in statische HTML pagina's verklein je het potentiële aanvalsoppervlak aanzienlijk. Dit versterkt de beveiliging van je site en vermindert de voortdurende noodzaak om WordPress, zijn plugins en thema's constant te updaten. Hierdoor kun je genieten van meer gemoedsrust, wetende dat je site bestand is tegen de meeste bedreigingen. | Details | |
Original current
By converting your site into static HTML pages, you substantially minimize the potential attack surface. This strengthens your website’s security and reduces the ongoing need to update WordPress, its plugins, and themes constantly. As a result, you can enjoy greater peace of mind, knowing your site is resilient to most threats.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Furthermore, with Staatic, you gain the flexibility to host your site on any platform of your choice. This means you could opt for an ultra-fast cloud provider or a robust content delivery network, further amplifying your site’s performance and ensuring optimal user experience. | Bovendien krijg je met Staatic de flexibiliteit om je site op elk platform van je keuze te hosten. Dit betekent dat je kunt kiezen voor een ultrasnelle cloud provider of een robuust content delivery network, wat de prestaties van je site verder versterkt en een optimale gebruikerservaring garandeert. | Details | |
Original current
Furthermore, with Staatic, you gain the flexibility to host your site on any platform of your choice. This means you could opt for an ultra-fast cloud provider or a robust content delivery network, further amplifying your site’s performance and ensuring optimal user experience.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| No, it shouldn’t. However, if there is a difference in the static version of your site, it might be due to invalid HTML in your original WordPress site that couldn’t be accurately converted. In such instances, consider checking your HTML’s validity using services like the <a href="https://validator.w3.org/">W3C Markup Validation Service</a>. | Nee, dat zou niet moeten. Als er echter een verschil is in de statische versie van je site, kan dat komen door ongeldige HTML in je originele WordPress site die niet nauwkeurig kon worden geconverteerd. Overweeg in dergelijke gevallen om de geldigheid van je HTML te controleren met behulp van hulpmiddelen zoals de <a href="https://validator.w3.org/">W3C mark-up validatie dienst</a>. | Details | |
Original current
No, it shouldn’t. However, if there is a difference in the static version of your site, it might be due to invalid HTML in your original WordPress site that couldn’t be accurately converted. In such instances, consider checking your HTML’s validity using services like the <a href="https://validator.w3.org/">W3C Markup Validation Service</a>.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| By eliminating both WordPress and PHP from the delivery process, pages from your site are served instantly, bypassing the delay of on-the-fly generation. This guarantees the quickest possible load times and significantly reduces the time to first byte (TTFB), offering an unparalleled browsing experience for your visitors and enhancing your site’s SEO positioning. | Door zowel WordPress als PHP uit het verwerkingsproces te elimineren, worden pagina's van je site direct geserveerd, waarbij de vertraging van het ter plekke genereren wordt omzeild. Dit garandeert de snelst mogelijke laadtijden en vermindert de tijd tot de eerste byte (TTFB) aanzienlijk, wat een ongeëvenaarde surfervaring biedt voor je bezoekers en de SEO positionering van je site verbetert. | Details | |
Original current
By eliminating both WordPress and PHP from the delivery process, pages from your site are served instantly, bypassing the delay of on-the-fly generation. This guarantees the quickest possible load times and significantly reduces the time to first byte (TTFB), offering an unparalleled browsing experience for your visitors and enhancing your site’s SEO positioning.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Supports HTTP (301, 302, 307, 308) redirects, custom “404 not found” page and other HTTP headers. | Ondersteunt HTTP (301, 302, 307, 308) omleidingen, aangepaste “404 niet gevonden” pagina en andere HTTP headers. | Details | |
Original current
Supports HTTP (301, 302, 307, 308) redirects, custom “404 not found” page and other HTTP headers.
CommentFound in description list item. You have to log in to edit this translation. |
|||
| Supports multiple deployment methods, e.g. GitHub, Netlify, AWS (Amazon Web Services) S3 or S3-compatible providers + CloudFront integration, or even your local server (dedicated or shared hosting). | Ondersteunt meerdere implementatiemethoden, bijvoorbeeld GitHub, Netlify, AWS (Amazon Web Diensten) S3 of S3 compatibele providers + CloudFront integratie, of zelfs je lokale server (dedicated of gedeelde hosting). | Details | |
Original current
Supports multiple deployment methods, e.g. GitHub, Netlify, AWS (Amazon Web Services) S3 or S3-compatible providers + CloudFront integration, or even your local server (dedicated or shared hosting).
CommentFound in description list item. You have to log in to edit this translation. |
|||
| Various integrations to improve compatibility with popular WordPress plugins. | Verschillende integraties om de compatibiliteit met populaire WordPress plugins te verbeteren. | Details | |
Original current
Various integrations to improve compatibility with popular WordPress plugins.
CommentFound in description list item. You have to log in to edit this translation. |
|||
| On the settings page, provide the relevant Build & Deployment settings; | Geef de relevante bouw & implementatie instellingen op vanuit de instellingenpagina; | Details | |
Original current
On the settings page, provide the relevant Build & Deployment settings;
CommentFound in installation list item. You have to log in to edit this translation. |
|||
Export as
Comment
Plugin name.