New to Translating WordPress? Read through our Translator Handbook to get started. Hide

Translation of Development Readme (trunk): Dutch

1 2
Prio Original string Translation
WordPress feature plugin to bring Progressive Web App (PWA) capabilities to Core
Priority: high
WordPress functionaliteit plugin om Progressive Web App (PWA) mogelijkheden naar Core te brengen Details
WordPress feature plugin to bring Progressive Web App (PWA) capabilities to Core
Comment

Short description.

You have to log in to edit this translation.

PWA
Priority: high
PWA Details
PWA
Comment

Plugin name.

You have to log in to edit this translation.

This plugin serves as a place to implement support for these in WordPress with the intention of being proposed for core merge, piece by piece. Case in point, the HTTPS functionality from this plugin has largely been made part of Core: <a href="https://make.wordpress.org/core/2021/02/22/improved-https-detection-and-migration-in-wordpress-5-7/">Improved HTTPS detection and migration in WordPress 5.7</a>. Deze plugin dient als een plek om ondersteuning voor deze functies in WordPress te implementeren met de intentie om stuk voor stuk voorgesteld te worden voor samenvoeging met de core. Zo is de HTTPS functionaliteit van deze plugin grotendeels onderdeel geworden van de Core: <a href="https://make.wordpress.org/core/2021/02/22/improved-https-detection-and-migration-in-wordpress-5-7/">Verbeterde HTTPS detectie en migratie in WordPress 5.7</a>. Details
This plugin serves as a place to implement support for these in WordPress with the intention of being proposed for core merge, piece by piece. Case in point, the HTTPS functionality from this plugin has largely been made part of Core: <a href="https://make.wordpress.org/core/2021/02/22/improved-https-detection-and-migration-in-wordpress-5-7/">Improved HTTPS detection and migration in WordPress 5.7</a>.
Comment

Found in description paragraph.

You have to log in to edit this translation.

In versions prior to 0.6, no caching strategies were added by default. The only service worker behavior was to serve an offline template when the client's connection is down or the site is down, and also to serve an error page when the server returns with 500 Internal Server Error. As of 0.6, there is a new “Offline browsingtoggle on the Reading Settings screen in the admin. It is disabled by default, but when enabled a <a href="https://web.dev/offline-cookbook/#network-falling-back-to-cache">network-first</a> caching strategy is registered for navigations so that the offline page won't be shown when accessing previously-accessed pages. The network-first strategy is also used for assets from themes, plugins, and WordPress core. In addition, uploaded images get served with a <a href="https://web.dev/offline-cookbook/#stale-while-revalidate">stale-while-revalidate</a> strategy. For all the details on these changes, see the <a href="https://github.com/GoogleChromeLabs/pwa-wp/pull/338">pull request</a>. In versies vóór 0.6 werden standaard geen cachingstrategieën toegevoegd. Het enige gedrag van de service worker was het aanbieden van een offline template wanneer de verbinding van de client niet werkte of de site niet werkte, en ook om een ​​foutpagina weer te geven wanneer de server terugkeert met 500 Internal Server Error. Vanaf 0.6 is er een nieuwe schakelaar voor "Offline browsen" op het scherm met leesinstellingen in de beheerder. Het is standaard uitgeschakeld, maar indien ingeschakeld wordt een <a href="https://web.dev/offline-cookbook/#network-falling-back-to-cache">network-first</a> cachingstrategie geregistreerd voor navigatie, zodat de offline pagina niet wordt weergegeven bij het openen van eerder geopende pagina's. De netwerk-first-strategie wordt ook gebruikt voor items uit thema's, plugins en WordPress core. Bovendien worden geüploade afbeeldingen geserveerd met een <a href="https://web.dev/offline-cookbook/#stale-while-revalidate">stale-while-revalidate</a> strategie. Zie het <a href="https://github.com/GoogleChromeLabs/pwa-wp/pull/338">pull-verzoek</a> voor alle details over deze wijzigingen. Details
In versions prior to 0.6, no caching strategies were added by default. The only service worker behavior was to serve an offline template when the client's connection is down or the site is down, and also to serve an error page when the server returns with 500 Internal Server Error. As of 0.6, there is a new “Offline browsingtoggle on the Reading Settings screen in the admin. It is disabled by default, but when enabled a <a href="https://web.dev/offline-cookbook/#network-falling-back-to-cache">network-first</a> caching strategy is registered for navigations so that the offline page won't be shown when accessing previously-accessed pages. The network-first strategy is also used for assets from themes, plugins, and WordPress core. In addition, uploaded images get served with a <a href="https://web.dev/offline-cookbook/#stale-while-revalidate">stale-while-revalidate</a> strategy. For all the details on these changes, see the <a href="https://github.com/GoogleChromeLabs/pwa-wp/pull/338">pull request</a>.
Comment

Found in description paragraph.

You have to log in to edit this translation.

Please see the <a href="https://github.com/GoogleChromeLabs/pwa-wp/wiki/FAQ">frequently asked questions</a> on the GitHub project wiki. Don't see an answer to your question? Please <a href="https://wordpress.org/support/plugin/pwa/">search the support forum</a> to see if someone has asked your question. Otherwise, please <a href="https://wordpress.org/support/plugin/pwa/#new-post">open a new support topic</a>. Raadpleeg de <a href="https://github.com/GoogleChromeLabs/pwa-wp/wiki/FAQ">veelgestelde vragen</a> op de GitHub project wiki. Zie je geen antwoord op je vraag? <a href="https://wordpress.org/support/plugin/pwa/">zoek het ondersteuningsforum</a> om te zien of iemand je vraag heeft gesteld. Anders, <a href="https://wordpress.org/support/plugin/pwa/#new-post">open een nieuw ondersteuningsonderwerp</a>. Details
Please see the <a href="https://github.com/GoogleChromeLabs/pwa-wp/wiki/FAQ">frequently asked questions</a> on the GitHub project wiki. Don't see an answer to your question? Please <a href="https://wordpress.org/support/plugin/pwa/">search the support forum</a> to see if someone has asked your question. Otherwise, please <a href="https://wordpress.org/support/plugin/pwa/#new-post">open a new support topic</a>.
Comment

Found in faq paragraph.

You have to log in to edit this translation.

Documentation for the plugin can be found on the <a href="https://github.com/GoogleChromeLabs/pwa-wp/wiki">GitHub project Wiki</a>. Documentatie voor de plugin is te vinden op de <a href="https://github.com/GoogleChromeLabs/pwa-wp/wiki">GitHub project Wiki</a>. Details
Documentation for the plugin can be found on the <a href="https://github.com/GoogleChromeLabs/pwa-wp/wiki">GitHub project Wiki</a>.
Comment

Found in description paragraph.

You have to log in to edit this translation.

<a href="https://en.wikipedia.org/wiki/HTTPS">HTTPS</a> <a href="https://en.wikipedia.org/wiki/HTTPS">HTTPS</a> Details
<a href="https://en.wikipedia.org/wiki/HTTPS">HTTPS</a>
Comment

Found in description list item.

You have to log in to edit this translation.

This feature plugin is <em>not</em> intended to obsolete the other plugins and themes which turn WordPress sites into PWAs. Rather, this plugin is intended to provide the PWA building blocks and coordination mechanism for these themes and plugins to not reinvent the wheel and also to not conflict with each other. For example, a theme that implements the app shell model should be able to extend the core service worker while a plugin that provides push notifications should be able to do the same. Themes and plugins no longer should have to each create a service worker on their own, something which is inherently problematic because only one service worker can be active at a time: only one service worker can win. If you are developing a plugin or theme that includes a service worker, consider relying on this PWA plugin, or at least only use the built-in implementation as a fallback for when the PWA plugin is not available. Deze functie plugin is <em>niet</em> bedoeld om de andere plugins en thema's die WordPress-sites in PWA's veranderen, te verouderen. Deze plugin is eerder bedoeld om de PWA-bouwstenen en het coördinatiemechanisme voor deze thema's en plugins te bieden om het wiel niet opnieuw uit te vinden en ook om niet met elkaar in conflict te komen. Een thema dat het app shellmodel implementeert, zou bijvoorbeeld de kernservicewerker moeten kunnen uitbreiden, terwijl een plugin die pushmeldingen biedt hetzelfde zou moeten kunnen doen. Thema's en plugins zouden niet langer elk een eigen service worker moeten creëren, iets wat inherent problematisch is omdat er slechts één service worker tegelijk actief kan zijn: er kan slechts één service worker winnen. Als je een plugin of thema ontwikkelt met een servicemedewerker, overweeg dan om op deze PWA plugin te vertrouwen, of gebruik in ieder geval alleen de ingebouwde implementatie als een uitwijkmogelijkheid voor wanneer de PWA plugin niet beschikbaar is. Details
This feature plugin is <em>not</em> intended to obsolete the other plugins and themes which turn WordPress sites into PWAs. Rather, this plugin is intended to provide the PWA building blocks and coordination mechanism for these themes and plugins to not reinvent the wheel and also to not conflict with each other. For example, a theme that implements the app shell model should be able to extend the core service worker while a plugin that provides push notifications should be able to do the same. Themes and plugins no longer should have to each create a service worker on their own, something which is inherently problematic because only one service worker can be active at a time: only one service worker can win. If you are developing a plugin or theme that includes a service worker, consider relying on this PWA plugin, or at least only use the built-in implementation as a fallback for when the PWA plugin is not available.
Comment

Found in description paragraph.

You have to log in to edit this translation.

<strong>Development of this plugin is done <a href="https://github.com/GoogleChromeLabs/pwa-wp">on GitHub</a>. Pull requests welcome. Please see <a href="https://github.com/GoogleChromeLabs/pwa-wp/issues">issues</a> reported there before going to the <a href="https://wordpress.org/support/plugin/pwa">plugin forum</a>.</strong> <strong>De ontwikkeling van deze plugin gebeurt <a href="https://github.com/GoogleChromeLabs/pwa-wp">op GitHub</a>. Pull-verzoeken welkom. Bekijk de <a href="https://github.com/GoogleChromeLabs/pwa-wp/issues">problemen</a> die daar zijn gemeld voordat je naar het <a href="https://wordpress.org/support/plugin/pwa">pluginforum</a> gaat.</strong> Details
<strong>Development of this plugin is done <a href="https://github.com/GoogleChromeLabs/pwa-wp">on GitHub</a>. Pull requests welcome. Please see <a href="https://github.com/GoogleChromeLabs/pwa-wp/issues">issues</a> reported there before going to the <a href="https://wordpress.org/support/plugin/pwa">plugin forum</a>.</strong>
Comment

Found in description paragraph.

You have to log in to edit this translation.

In general a PWA depends on the following technologies to be available: Over het algemeen is een PWA afhankelijk van de beschikbaarheid van de volgende technologieën: Details
In general a PWA depends on the following technologies to be available:
Comment

Found in description paragraph.

You have to log in to edit this translation.

Continue reading more about <a href="https://web.dev/progressive-web-apps/">Progressive Web Apps</a> (PWA) from Google. Lees meer over <a href="https://web.dev/progressive-web-apps/">Progressive Web Apps</a> (PWA) van Google. Details
Continue reading more about <a href="https://web.dev/progressive-web-apps/">Progressive Web Apps</a> (PWA) from Google.
Comment

Found in description paragraph.

You have to log in to edit this translation.

<a href="https://developer.mozilla.org/en-US/docs/Web/Manifest">Web App Manifest</a> <a href="https://developer.mozilla.org/en-US/docs/Web/Manifest">Web App Manifest</a> Details
<a href="https://developer.mozilla.org/en-US/docs/Web/Manifest">Web App Manifest</a>
Comment

Found in description list item.

You have to log in to edit this translation.

<a href="https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API">Service Workers</a> <a href="https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API">Service Workers</a> Details
<a href="https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API">Service Workers</a>
Comment

Found in description list item.

You have to log in to edit this translation.

<a href="https://developers.google.com/web/progressive-web-apps/#engaging">Engaging</a> - Feel like a natural app on the device, with an immersive user experience. <a href="https://developers.google.com/web/progressive-web-apps/#engaging">Boeiend</a> - Voelt als een normale app op het apparaat, met een meeslepende gebruikerservaring. Details
<a href="https://developers.google.com/web/progressive-web-apps/#engaging">Engaging</a> - Feel like a natural app on the device, with an immersive user experience.
Comment

Found in description list item.

You have to log in to edit this translation.

<a href="https://developers.google.com/web/progressive-web-apps/#fast">Fast</a> - Respond quickly to user interactions with silky smooth animations and no janky scrolling. <a href="https://developers.google.com/web/progressive-web-apps/#fast">Snel</a> - Reageer snel op gebruikersinteracties met zijdezachte animaties en zonder janky scrollen. Details
<a href="https://developers.google.com/web/progressive-web-apps/#fast">Fast</a> - Respond quickly to user interactions with silky smooth animations and no janky scrolling.
Comment

Found in description list item.

You have to log in to edit this translation.

Legend:
Current
Waiting
Rejected
Fuzzy
Old
Changes requested
With warnings
1 2

Export as