New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| Additional case studies | Extra case studies | Details | |
Original current
Additional case studies
You have to log in to edit this translation. |
|||
| BuddyPress ↗ | BuddyPress ↗ | Details | |
Original current |
|||
| bbPress ↗ | bbPress ↗ | Details | |
Original current |
|||
| WordPress.com ↗ | WordPress.com ↗ | Details | |
Original current |
|||
| Matt ↗ | Matt ↗ | Details | |
Original current |
|||
| In 2020, the <a href="%s">WordPress 5.6 “Simone”</a> release came from the first all-women and non-binary identifying release squad. WordPress 5.6 brought countless ways to set ideas free and bring them to life. | In 2020 kwam de <a href="%s">WordPress 5.6 Simone</a> release van de eerste volledig vrouwelijke en non-binary identificerende release ploeg. WordPress 5.6 bracht talloze manieren om ideeën vrij te maken en tot leven te brengen. | Details | |
Original current
In 2020, the <a href="%s">WordPress 5.6 “Simone”</a> release came from the first all-women and non-binary identifying release squad. WordPress 5.6 brought countless ways to set ideas free and bring them to life.
You have to log in to edit this translation. |
|||
| With a brand-new default theme as a canvas, and support for an ever-growing collection of blocks as brushes, it became possible to paint with words, pictures, sound, or rich embedded media. | Met een gloednieuw standaardthema als canvas en ondersteuning voor een steeds groter wordende verzameling blokken als penselen, werd het mogelijk om te schilderen met woorden, afbeeldingen, geluid of rich ingesloten media. | Details | |
Original current
With a brand-new default theme as a canvas, and support for an ever-growing collection of blocks as brushes, it became possible to paint with words, pictures, sound, or rich embedded media.
You have to log in to edit this translation. |
|||
| With <a href="%s">WordPress v5.5 “Eckstine”</a> in 2020, it became easier than ever to find the block you need. The new block directory was now built right into the block editor, making it possible to install new block types without ever leaving the editor. | Met <a href="%s">WordPress v5.5 “Eckstine”</a> in 2020 werd het gemakkelijker dan ooit om het blok te vinden dat je nodig hebt. De nieuwe blok directory is nu rechtstreeks in de blok-editor ingebouwd, waardoor het mogelijk is nieuwe bloktypes te installeren zonder de editor te verlaten. | Details | |
Original current
With <a href="%s">WordPress v5.5 “Eckstine”</a> in 2020, it became easier than ever to find the block you need. The new block directory was now built right into the block editor, making it possible to install new block types without ever leaving the editor.
You have to log in to edit this translation. |
|||
| In 2019, Matt Mullenweg held a moment of silence for long-time community member <a href="%s">Alex Mills (viper007bond)</a> who passed away after a long-fought battle with leukemia. Alex was a very kind, creative, and prolific WordPress contributor. | In 2019 hield Matt Mullenweg een moment van stilte voor oud community lid <a href="%s">Alex Mills (viper007bond)</a> die stierf na een lang bevochten strijd tegen leukemie. Alex was een erg aardige, creatieve en productieve WordPress bijdrager. | Details | |
Original current
In 2019, Matt Mullenweg held a moment of silence for long-time community member <a href="%s">Alex Mills (viper007bond)</a> who passed away after a long-fought battle with leukemia. Alex was a very kind, creative, and prolific WordPress contributor.
You have to log in to edit this translation. |
|||
| For developers building client sites, you could now create reusable blocks, letting your clients add new content anytime, while still maintaining a consistent look and feel. A wide collection of APIs and interface components made it easy to create blocks with intuitive controls. Utilizing these components not only sped up development work but also provided a more consistent, usable, and accessible interface. | Voor ontwikkelaars die websites voor klanten bouwen, kun je nu herbruikbare blokken maken, zodat je klanten op elk moment nieuwe inhoud kunnen toevoegen, terwijl ze toch een consistente look en feel behouden. Een brede verzameling API's en interfacecomponenten maakte het gemakkelijk om blokken te maken met intuïtieve bedieningselementen. Het gebruik van deze componenten versnelde niet alleen het ontwikkelingswerk, maar leverde ook een meer consistente, bruikbare en toegankelijke interface op. | Details | |
Original current
For developers building client sites, you could now create reusable blocks, letting your clients add new content anytime, while still maintaining a consistent look and feel. A wide collection of APIs and interface components made it easy to create blocks with intuitive controls. Utilizing these components not only sped up development work but also provided a more consistent, usable, and accessible interface.
You have to log in to edit this translation. |
|||
| Big upgrades to the editor. With the release of <a href="%s">WordPress v5.0 “Bebo”</a> in 2018, Gutenberg became the default editing experience. The new block-based editor was the first step toward an exciting new future. Whether you were building your first site, revamping your blog, or writing code for a living; Gutenberg offered more content flexibility. | Grote upgrades voor de editor. Met de release van <a href="%s">WordPress v5.0 Bebo</a> in 2018 werd Gutenberg de standaard bewerkingservaring. De nieuwe blokgebaseerde editor was de eerste stap naar een opwindende nieuwe toekomst. Of je nu je eerste website bouwt, je blog vernieuwt of code schrijft voor de kost; Gutenberg bood meer inhoud flexibiliteit. | Details | |
Original current
Big upgrades to the editor. With the release of <a href="%s">WordPress v5.0 “Bebo”</a> in 2018, Gutenberg became the default editing experience. The new block-based editor was the first step toward an exciting new future. Whether you were building your first site, revamping your blog, or writing code for a living; Gutenberg offered more content flexibility.
You have to log in to edit this translation. |
|||
| WordCamp Europe, in 2013, was the first large-scale WordCamp to be held in Europe. By large-scale, we mean big. And by big, we mean awesome. This was a chance for the European WordPress community to gather together in the idyllic town of Leiden to geek-out, share experiences, do business, and most of all, talk WordPress. | WordCamp Europe was in 2013 de eerste grootschalige WordCamp die in Europa werd gehouden. Met grootschaligheid bedoelen we groot. En met groot bedoelen we geweldig. Dit was een kans voor de Europese WordPress community om samen te komen in het idyllische stadje Leiden om te geek-out, ervaringen te delen, zaken te doen en vooral te praten over WordPress. | Details | |
Original current
WordCamp Europe, in 2013, was the first large-scale WordCamp to be held in Europe. By large-scale, we mean big. And by big, we mean awesome. This was a chance for the European WordPress community to gather together in the idyllic town of Leiden to geek-out, share experiences, do business, and most of all, talk WordPress.
You have to log in to edit this translation. |
|||
| The first en-masse, invitation-only WordPress community get-together — <a href="%s">The Community Summit</a> — took place in 2012. The Community Summit focused on issues facing WordPress software development and the wider WordPress community. Community members nominated themselves and others to receive an invitation; a team of 18 people reviewed and voted on who would be invited. The attendees — active contributors, bloggers, plugin and theme developers, and business owners from across the WordPress community — came to Tybee Island, Georgia, to talk about WordPress. | De eerste massale bijeenkomst van de WordPress community op uitnodiging - <a href="%s">The Community Summit</a> - vond plaats in 2012. De Community Summit richtte zich op problemen waarmee de ontwikkeling van WordPress software en de bredere WordPress community te maken heeft. Leden van de community hebben zichzelf en anderen voorgedragen om een uitnodiging te ontvangen; een team van 18 mensen beoordeelde en stemde op wie zou worden uitgenodigd. De aanwezigen - actieve bijdragers, bloggers, plugins en thema-ontwikkelaars en bedrijfseigenaren uit de hele WordPress community - kwamen naar Tybee Island, Georgia, om over WordPress te praten. | Details | |
Original current
The first en-masse, invitation-only WordPress community get-together — <a href="%s">The Community Summit</a> — took place in 2012. The Community Summit focused on issues facing WordPress software development and the wider WordPress community. Community members nominated themselves and others to receive an invitation; a team of 18 people reviewed and voted on who would be invited. The attendees — active contributors, bloggers, plugin and theme developers, and business owners from across the WordPress community — came to Tybee Island, Georgia, to talk about WordPress.
You have to log in to edit this translation. |
|||
| The <a href="%s">community was pleased</a> with decoupling WordPress the project from Automattic the company. It gave people more confidence that Automattic was not out to dominate the WordPress commercial ecosystem. | De <a href="%s">community was tevreden</a> met het loskoppelen van WordPress het project van Automattic het bedrijf. Het gaf mensen meer vertrouwen dat Automattic er niet op uit was om het commerciële ecosysteem van WordPress te domineren. | Details | |
Original current
The <a href="%s">community was pleased</a> with decoupling WordPress the project from Automattic the company. It gave people more confidence that Automattic was not out to dominate the WordPress commercial ecosystem.
You have to log in to edit this translation. |
|||
| The WordPress Foundation was launched in January 2010. Automattic transferred <a href="%s">the trademarks</a> later that year in September. As part of the transfer, Automattic was granted use of WordPress for WordPress.com, but not for any future domains. Matt was granted a license for WordPress.org and WordPress.net. As well as transferring the trademarks for WordPress itself, the company also transferred the WordCamp name. As with WordPress itself, this protects WordCamps as non-profit, educational events in perpetuity. | De WordPress Foundation werd gelanceerd in januari 2010. Automattic heeft <a href="%s">de handelsmerken</a> later dat jaar, in september, overgedragen. Als onderdeel van de overdracht kreeg Automattic het gebruik van WordPress voor WordPress.com, maar niet voor toekomstige domeinen. Matt kreeg een licentie voor WordPress.org en WordPress.net. Naast het overdragen van de handelsmerken voor WordPress zelf, heeft het bedrijf ook de naam WordCamp overgedragen. Net als bij WordPress zelf, beschermt dit WordCamps voor altijd als educatieve evenementen zonder winstoogmerk. | Details | |
Original current
The WordPress Foundation was launched in January 2010. Automattic transferred <a href="%s">the trademarks</a> later that year in September. As part of the transfer, Automattic was granted use of WordPress for WordPress.com, but not for any future domains. Matt was granted a license for WordPress.org and WordPress.net. As well as transferring the trademarks for WordPress itself, the company also transferred the WordCamp name. As with WordPress itself, this protects WordCamps as non-profit, educational events in perpetuity.
You have to log in to edit this translation. |
|||
Export as