Nieuws van politieke partijen in Almelo inzichtelijk

3778 documenten

10 Amazing WordPress Design Resouces

Democraten NU Democraten NU Almelo 18-04-2024 20:37

Designing a beautiful website from scratch can be difficult for developers of all skill levels. Luckily, in today’s Build and Beyond video, Jamie Marsland reveals his ten favorite WordPress design tools and websites to elevate your next build.

Get inspiration for your next website’s design and then start building with WordPress.com. Ready to get going? Click below to embark on your free trial today:

Here are the sites and resources mentioned in the video:

Stunning backgrounds and visuals

A design-your-own-theme tool using block patterns

Free CSS generator for a glass effect

Save and explore inspiring designs

Easy mockups for products and thumbnails

WordPress.com’s free library of block patterns

Generate color palettes with a click

Another block pattern library, but with community-uploaded designs

The best AI image generator

WordPress plugin to easily find free-to-use images

Missing out on the latest WordPress.com developments? Enter your email below to receive future announcements direct to your inbox. An email confirmation will be sent before you will start receiving notifications—please check your spam folder if you don't receive this.

Making 43% of the Web More Dynamic with the WordPress Interactivity API

Democraten NU Democraten NU Almelo 17-04-2024 12:00

Creating rich, engaging, and interactive website experiences is a simple way to surprise, delight, and attract attention from website readers and users. Dynamic interactivity like instant search, form handling, and client-side “app-like” navigation where elements can persist across routes, all without a full page reload, can make the web a more efficient and interesting place for all.

But creating those experiences on WordPress hasn’t always been the easiest or most straightforward, often requiring complex JavaScript framework setup and maintenance.

Now, with the Interactivity API, WordPress developers have a standardized way for doing that, all built directly into core.

ELI5: The Interactivity API and the Image Block

Several core WordPress blocks, including the Query Loop, Image, and Search blocks, have already adopted the Interactivity API. The Image block, in particular, is a great way to show off the Interactivity API in action.

At its core, the Image blocks allow you to add an image to a post or page. When a user clicks on an image in a post or page, the Interactivity API launches a lightbox showing a high-resolution version of the image.

The rendering of the Image block is handled server-side. The client-side interactivity, handling resizing and opening the lightbox, is now done with the new API that comes bundled with WordPress. You can bind the client-side interactivity simply by adding the

to the image element, referencing the

You might say, “But I could easily do this with some JavaScript!” With the Interactivity API, the code is compact and declarative, and you get the context (local state) to handle the lightbox, resizing, side effects, and all of the other needed work here in the store object.

actions: { showLightbox() { const ctx = getContext(); // Bails out if the image has not loaded yet. if ( ! ctx.imageRef?.complete ) { return; } // Stores the positons of the scroll to fix it until the overlay is // closed. state.scrollTopReset = document.documentElement.scrollTop; state.scrollLeftReset = document.documentElement.scrollLeft; // Moves the information of the expaned image to the state. ctx.currentSrc = ctx.imageRef.currentSrc; imageRef = ctx.imageRef; buttonRef = ctx.buttonRef; state.currentImage = ctx; state.overlayEnabled = true; // Computes the styles of the overlay for the animation. callbacks.setOverlayStyles(); }, ...

The lower-level implementation details, like keeping the server and client side in sync, just work; developers no longer need to account for them.

This functionality is possible using vanilla JavaScript, by selecting the element via a query selector, reading data attributes, and manipulating the DOM. But it’s far less elegant, and up until now, there hasn’t been a standardized way in WordPress of handling interactive events like these.

With the Interactivity API, developers have a predictable way to provide interactivity to users on the front-end. You don’t have to worry about lower-level code for adding interactivity; it’s there in WordPress for you to start using today. Batteries are included.

How is the Interactivity API different from Alpine, React, or Vue?

Prior to merging the Interactivity API into WordPress core, developers would typically reach for a JavaScript framework to add dynamic features to the user-facing parts of their websites. This approach worked just fine, so why was there a need to standardize it?

At its core, the Interactivity API is a lightweight JavaScript library that standardizes the way developers can build interactive HTML elements on WordPress sites.

Mario Santos, a developer on the WordPress core team, wrote in the Interactivity API proposal that, “With a standard, WordPress can absorb the maximum amount of complexity from the developer because it will handle most of what’s needed to create an interactive block.”

The team saw that the gap between what’s possible and what’s practical grew as sites became more complex. The more complex a user experience developers wanted to build, the more blocks needed to interact with each other, and the more difficult it became to build and maintain sites. Developers would spend a lot of time making sure that the client-side and server-side code played nicely together.

For a large open-source project with several contributors, having an agreed-upon standard and native way of providing client-side interactivity speeds up development and greatly improves the developer experience.

Block-first and PHP-first: Prioritizing blocks for building sites and server side rendering for better SEO and performance. Combining the best for user and developer experience.

Backward-compatible: Ensuring compatibility with both classic and block themes and optionally with other JavaScript frameworks, though it’s advised to use the API as the primary method. It also works with hooks and internationalization.

Declarative and reactive: Using declarative code to define interactions, listening for changes in data, and updating only relevant parts of the DOM accordingly.

Performant: Optimizing runtime performance to deliver a fast and lightweight user experience.

Other goals are on the horizon, including improvements to client-side navigation, as you can see in this PR.

The Interactivity API shares a few similarities to Alpine—a lightweight JavaScript library that allows developers to build interactions into their web projects, often used in WordPress and Laravel projects.

Similar to Alpine, the Interactivity API uses directives directly in HTML and both play nicely with PHP. Unlike Alpine, the Interactivity API is designed to seamlessly integrate with WordPress and support server-side rendering of its directives.

With the interactivity API, you can easily generate the view from the server in PHP, and then add client-side interactivity. This results in less duplication, and its support in WordPress core will lead to less architectural decisions currently required by developers.

So while Alpine and the Interactivity API share a broadly similar goal—making it easy for web developers to add interactive elements to a webpage—the Interactivity API is even more plug-and-play for WordPress developers.

Interactivity API vs. React and Vue

Many developers have opted for React when adding interactivity to WordPress sites because, in the modern web development stack, React is the go-to solution for declaratively handling DOM interactivity. This is familiar territory, and we’re used to using React and JSX when adding custom blocks for Gutenberg.

Loading React on the client side can be done, but it leaves you with many decisions: “How should I handle routing? How do I work with the context between PHP and React? What about server-side rendering?”

Part of the goal in developing the Interactivity API was the need to write as little as little JavaScript as possible, leaving the heavy lifting to PHP, and only shipping JavaScript when necessary.

The core team also saw issues with how these frameworks worked in conjunction with WordPress. Developers can use JavaScript frameworks like React and Vue to render a block on the front-end that they server-rendered in PHP, for example, but this requires logic duplication and risks exposure to issues with WordPress hooks.

For these reasons, among others, the core team preferred Preact—a smaller UI framework that requires less JavaScript to download and execute without sacrificing performance. Think of it like React with fewer calories.

Luis Herranz, a WordPress Core contributor from Automattic, outlines more details on Alpine vs the Interactivity API’s usage of Preact with a thin layer of directives on top of it in this comment on the original proposal.

Preact only loads if the page source contains an interactive block, meaning it is not loaded until it’s needed, aligning with the idea of shipping as little JavaScript as possible (and shipping no JavaScript as a default).

In the original Interactivity API proposal, you can see the run-down and comparison of several frameworks and why Preact was chosen over the others.

What does the new Interactivity API provide to WordPress developers?

In addition to providing a standardized way to render interactive elements client-side, the Interactivity API also provides developers with directives and a more straightforward way of creating a store object to handle state, side effects, and actions.

Graphic from Proposal: The Interactivity API – A better developer experience in building interactive blocks on WordPress.org

Directives, a special set of data attributes, allow you to extend HTML markup. You can share data between the server-side-rendered blocks and the client-side, bind values, add click events, and much more. The Interactivity API reference lists all the available directives.

These directives are typically added in the block’s

file, and they support all of the WordPress APIs, including actions, filters, and core translation APIs.

Here’s the render file of a sample block. Notice the click event (

data-wp-on--click="actions.toggle"

), and how we bind the value of the aria-expanded attributes via directives.

data-wp-interactive="create-block" false ) ); ?> data-wp-watch="callbacks.logIsOpen" >

Do you need to dynamically update an element’s inner text? The Interactivity API allows you to use

on an element, just like you can use v-text in Vue.

You can bind a value to a boolean or string using

on the element. This means you can write PHP and HTML and sprinkle in directives to add interactivity in a declarative way.

Handling state, side effects, and actions

The second stage of adding interactivity is to create a store, which is usually done in your

file. In the store, you’ll have access to the same context as in your

In the store object, you define actions responding to user interactions. These actions can update the local context or global state, which then re-renders and updates the connected HTML element. You can also define side effects/callbacks, which are similar to actions, but they respond to state changes instead of direct user actions.

import { store, getContext } from '@wordpress/interactivity'; store( 'create-block', { actions: { toggle: () => { const context = getContext(); context.isOpen = ! context.isOpen; }, }, callbacks: { logIsOpen: () => { const { isOpen } = getContext(); // Log the value of `isOpen` each time it changes. console.log( `Is open: ${ isOpen }` ); }, }, } );

The Interactivity API is production-ready and already running on WordPress.com! With any WordPress.com plan, you’ll have access to the core blocks built on top of the Interactivity API.

If you want to build your own interactive blocks, you can scaffold an interactive block by running the below code in your terminal:

npx @wordpress/create-block@latest my-interactive-block --template @wordpress/create-block-interactive-template

This will give you an example interactive block, with directives and state handling set up.

You can then play around with this locally, using

, using a staging site, or by uploading the plugin directly to your site running a plugin-eligible WordPress.com plan.

If you want a seamless experience between your local dev setup and your WordPress.com site, try using it with our new GitHub Deployments feature! Developing custom blocks is the perfect use case for this new tool.

The best way to learn something new is to start building. To kick things off, you may find the following resources a good starting point:

Missing out on the latest WordPress.com developments? Enter your email below to receive future announcements direct to your inbox. An email confirmation will be sent before you will start receiving notifications—please check your spam folder if you don't receive this.

WordPress Website Speed Build: The Masters Golf Tournament

Democraten NU Democraten NU Almelo 16-04-2024 16:43

Congratulations are in order for Scottie Scheffler, the winner of the 2024 Masters Tournament in Augusta, Georgia! In today’s Build and Beyond video, Jamie Marsland takes on the slightly less intimidating task of re-creating the Masters website as quickly as he can. Can he possibly do it in just 30 minutes?

Along the way, you’ll learn about sticky navigation menus, image overflows and breakouts, card layouts, and more.

Interested in a free trial that allows you to test our all that WordPress.com has to offer? Click below:

Missing out on the latest WordPress.com developments? Enter your email below to receive future announcements direct to your inbox. An email confirmation will be sent before you will start receiving notifications—please check your spam folder if you don't receive this.

Registering Custom Post Types in the WordPress Admin: Our CloudFest Hackathon Report

Democraten NU Democraten NU Almelo 15-04-2024 12:00

With WordPress today you need to use custom code or a plugin to create a custom post type like “Book” or “Member.” This is a popular need, and there are a variety of approaches; however, one challenge is that the end-user experience can be confusing and non-standardized.

A few weeks ago, some Automatticians and I went to the 7th CloudFest Hackathon in Rust, Germany to explore a solution for this. We started hacking on a deeply nerdy project, JSON Schema forms and fields, and ended up with a fascinating approach to an age-old question: What if you could register custom post types and custom fields directly in the WordPress admin?

Forty-eight hours turns an idea into reality

The CloudFest Hackathon is an event that allows developers from around the globe to take ideas and turn them into realities.

During the Hackathon, teams of developers from various content management systems and hosting companies come together to contribute to projects that align with the core principles of the event: the projects must be not-for-profit, interoperable, and open source.

This year, we focused on a JSON Schema Field/Form Renderer. While most of us explored using JSON Schema to dynamically register admin forms and fields, Dennis Snell and Adam Zieliński decided to take the project one step further! They hacked together a plugin that introduced the ability to register custom post types and custom fields directly from the WordPress admin. More notably, everything happens within the block editor—you have to see it to believe it:

This work poses some interesting possibilities for custom post type and custom field implementation because it could fundamentally change the way low- to no-code WordPress users modify their sites.

Should WordPress let you register custom post types and custom fields from the admin? #CFHack2024

— daniel (@dbchhbr) March 17, 2024

I got quite a range of responses, ranging from “Heck Yes! It should have already been a core feature now. Such an integral part of every other site” to “Admin should only be for content and user management. Everything else should be configured in code and version controllable.”

So why the range in responses? Let’s discuss.

Dennis and Adam built our prototype using the following conventions:

A custom post type

holds templates for user-defined data types.

The title of a post in the

defines the name of the new data type. The post itself is the rendering template and comprises any set of normal blocks. Names are given to select block attributes within the post, and these names are mapped into the data type.

When creating new posts for the given data type, the locked template is copied from the

template, and the block attribute annotations are preserved.

Finally, when rendering the

template, the attributes are pulled from the individual post of the given data type and spliced into the template.

The fascinating idea is that we don’t have to think about form fields; blocks already provide a rendering view and a modal editing experience. We can rely on the fundamental way blocks work and use the very same user experience to create custom data types in a way that users are already familiar with when editing a post or a site.

We can provide JSON-LD markup properties to the block editor using our Custom Fields Names block settings.

Custom post types define custom data types, so we use a template to not only define the data type, but also to provide a default rendering template. Each data attribute within a post type has a field where it’s possible to define that field with its JSON-LD property.

For example, say you had a “Book” custom post type. A few JSON-LD properties you could define using custom fields are:

We also chose to store a copy of each block attribute in the JSON attributes for that block. Since WordPress can now provide a post-to-JSON function, which merges the extracted attributes with the names assigned in the custom post type template, that template may have changed since the custom post was created. This means that no database migrations are necessary to render an updated version of a post.

The best part? The WordPress infrastructure that already exists (aka Gutenberg!) defines the data type. Because these custom posts are normal posts, and because they adopt the locked template for the data type definition, they are, in fact, renderable on their own! Even if the template has been updated and only the post itself is rendered, it will still display a meaningful representation of the data type as it was when it was created.

While our original Hackathon project was tailored towards developers and UX designers who would love to see a forms and fields API in WordPress, this prototype puts more power in the hands of low- to no-code WordPress users.

It also opens up a world of possibilities for providing a rendering view for any structured data. Imagine uploading a CSV and mapping the column names to block attributes, or connecting to a database or JSON API to map the records in the same way.

For example, if you had a CSV with business names, addresses, a rating, and a description, we could take that template post and insert a map block, a heading block, a star rating block, and a paragraph block and set the attributes to map to the CSV columns. It’s essentially an instant structured data renderer!

But even if we can define custom post types and fields in the editor, should we, as a WordPress community, consider adding it to core?

The existential question: Should it exist?

Adding this kind of functionality into WordPress core could open up a ton of opportunities for the average WordPress user. Instead of needing to get a developer involved to add a custom post type to their site, a user could simply do it themselves and define the necessary fields and structured data attributes.

On the other hand, allowing everyday users, who may not have a full grasp of how custom post types and structured data should work, free reign to create these data types themselves could have detrimental effects on the user experience of their websites. Clunky or incorrect implementation of structured data markup could also cause issues with how search engines crawl these sites, causing unintended negative impacts to search traffic.

Not only that, but as of right now, if a custom post type is accidentally deleted, all of the content posted to that custom post type will no longer be accessible through the admin (even though it will still be stored in the database). The user could think they “lost” their data.

What do you think? Are you in favor of giving website owners the ability to change and customize their custom post types and attributes? Or are there some website features that should always require a more technical hand and implementer?

We’d love to chat with you about your thoughts in the comments below.

Thanks to Lars Gersmann for leading the JSON Schema project with me and to everyone on the Syntax Errors team: Adam Zieliński, Dennis Snell, Julian Haupt, Michael Schmitz, Anja Lang, Thomas Rose, Marko Feldmann, Fabian Genes, Michael Schmitz, Jan Vogt, Lucisu, Maximilian Andre, Marcel Schmitz, and Milana Cap.

Missing out on the latest WordPress.com developments? Enter your email below to receive future announcements direct to your inbox. An email confirmation will be sent before you will start receiving notifications—please check your spam folder if you don't receive this.

Een stukje cultuur is ook met de (verdwenen) bruggen verdwenen……..

Partij Vrij Almelo (PVA) Partij Vrij Almelo (PVA) Almelo 10-04-2024 16:34

Gesprek met oud wethouder Sjoers over de monorail

Al jarenlang wordt over het onderscheidende karakter van de Almelose stad gesproken. In 1960 wordt de Havenkom, waar thans C&A is gevestigd gedempt en de markt wordt verplaatst naar de Haven NZ/ZZ. Begin jaren 80 wordt het ontbreken van water in de binnenstad als een groot gemis ervaren. Even daarna pleit men voor het water-weg-terug in de binnenstad. Maar zover is het dan nog lang niet. In 1976 begon de grootschalige bouw rond het marktplein van onder andere de Rabobank, de Kloosterhofflat en C&A. Een jaartje later begon men met de bouw van het politiebureau en de ambulancegarage. In 1989 werd begonnen met de grootschalige reconstructie van de binnenstad. De afbraak van de laatste textielfabriek aan de Haven ZZ is dan een feit. Als herinnering aan wat eens een grote fabrieksstad in Twente was, is alleen nog maar de markante schoorsteen en de portiersloge van de fabriek Van Heek-Scholco overgebleven.

Op dit moment is de gemeente Almelo alweer bezig met de berekening van nieuwe plannen. Bij het uitwerken van het eerste ontwerp naar een definitief plan is gebleken dat men bij grote projecten nooit in staat is geweest de juiste kosten in beeld te brengen. Toch hebben wij, de Partij Vrij Almelo, altijd gewaarschuwd voor de ontwikkelingen waarmee het college van B&W bezig was. Volgens ons kan het allemaal wel wat bescheidener dan al die afschuwelijke hoogbouw die het Almelose bestuur steeds weer wil neerzetten.

Het eerste project dat de sfeer in Almelo zou gaan verpesten was de bouw van een torenflat aan de Hofstraat. Je zou je kunnen afvragen wie op het idee komt zo’n monster van 70 meter in een historisch gebied neer te zetten. Gelukkig ging het niet door want het massale protest van Almeloërs leverde ruim 4500 handtekeningen op.

Maar daar bleef het niet bij, allerlei hoogbouwprojecten passeerden de Raad inclusief het Monorail plan. In alle vergaderingen ging het over geld, haalbaarheid en economie, maar zelden over ideeën. Almelo op hoog niveau was het modewoord. Almelo is definitief de stad Almelo geworden. Almelo, een stad in het Twentse landschap verworden tot een samenraapsel van betonnen kolossen en koude blokkendozen waar voor cultuurhistorie geen plaats meer is.

In 2011 kwam de Partij Vrij Almelo met een eigen beleidsplan dat vrijwel direct de aandacht trok van een zeer enthousiaste en bevlogen ambtenaar, wijlen de heer Jacob Melsen, hoofd van de dienst binnenstadsontwikkeling. Het weer terugbrengen van het water in de binnenstad, inclusief de twee oude bruggen die volgens de heer Melsen na de grootschalige afbraak waren opgeslagen en dus bewaard zijn gebleven. Hergebruik van deze bruggen aan zowel de Egbert Gorterstraat als aan de Klara Zetkinstraat zou naar onze mening sterk bijdragen aan het herstel van de identiteit van Almelo. Door op een verstandige manier het water bij het centrum te betrekken kan dit zelfs leiden tot enige vorm van toerisme. Vooral als het water bevaarbaar wordt gemaakt voor lichte boten. Met een drankje in de hand, zwaaien naar waterfietsen en roeibootjes. Wat wil je nog meer?

Cultuurhistorie kan een inspiratiebron zijn voor nieuwe ontwikkelingen en toekomstige plannen extra kwaliteit geven. De wens van de Partij Vrij Almelo was om de vroegere ophaalbruggen weer terug te brengen in het straatbeeld. De originele tekeningen van de bruggen bleken er nog te zijn. Het balletje begon te rollen toen het adviesbureau Royal Haskoning DHV in opdracht van de gemeente Almelo een onderzoek uitvoerde naar het toepassen van een tweedehands brug in de binnenstad van Almelo.

Tijdens een politiek beraad kwamen de oude Almelose bruggen weer ter discussie waarna Ingenieur Luuk Dijkstra van Royal Haskoning DHV de Partij Vrij Almelo benaderde met de vraag of wij hier iets meer van wisten zodat zij de uitvoerbaarheid konden onderzoeken. Maar geen enkele benaderde, naar onze mening wegduikende ambtenaar kon ons verder helpen en zelfs op een mail aan Stadsherstel kregen we geen enkele reactie.

Een stukje cultuur is ook met de (verdwenen) bruggen verdwenen……..

Harry de Olde

Site-Building Made Simple: Introducing the Public Pattern Library

Democraten NU Democraten NU Almelo 10-04-2024 16:31

When it comes to website-building, WordPress themes set your site up for success by providing stylish, preselected options for fonts, colors, and layouts. Even though themes provide the overall aesthetic, you still need to build out the posts, pages, and templates on your site. That’s where block patterns come in!

The WordPress.com Pattern Library is your new go-to resource for finding any kind of pattern for your beautiful WordPress website. With hundreds of pre-built patterns to choose from across over a dozen categories, you’ll be covered no matter your website’s specific needs.

Block patterns are collections of blocks made to work seamlessly with our modern themes. Need an “About” page? Check. A gallery? Check. A testimonial? Check. How about a newsletter? Check. We have just about anything you’ll need.

Best of all: for each pattern, the fonts, colors, and spacing will adapt to your theme’s settings, making for a cohesive look. Still, patterns aren’t locked or static either—after you’ve added the pattern to your post, page, or template, you can tweak it however you like.

This new public Pattern Library allows you to browse, preview, and easily share or implement whichever design speaks your tastes. Let’s take a look around.

If you want to explore the Pattern Library and don’t have anything in particular that you’re looking for, click through each category to spark some ideas.

At the top, you’ll find a fast and easy-to-use search box, allowing you to find exactly what you need. This is a great option if you don’t feel like browsing and want to jump right into a solution for your specific needs.

Sometimes you just need the components of a post, page, or template: a header, a “Subscribe” box, a store module, etc. Other times, you want to be able to copy and paste an entire page into existence. Scroll down past the categories and you’ll find our full-page patterns for whole pages: About, Blog, Contact, Store, and more.

Test the mobile responsiveness for each pattern

When looking through the library on a desktop or laptop device, you’ll see a gray vertical bar next to each pattern. That’s a nifty little slider that we’ve built into the library which allows you to see how each pattern responds to different screen sizes. Using your cursor to move the bar to the left, you’ll see what that design looks like on a mobile device; in the middle is where most tablets fall; and scroll back all the way to the right for the desktop/laptop version.

Like what you see? Simply click the blue “Copy pattern” button, open the WordPress.com editor to the post, page, or template you’re working on, and paste the design. It’s that easy. Once inserted, you can customize each block as needed using the right sidebar.

Your new favorite page-building tool

The Pattern Library is especially useful if you build websites for clients. Each pattern is built to work with any theme that follows our technical standards, speeding up page-building not just for you but also for your clients—all while maintaining the overall style of your theme.

In concrete terms, this means that our patterns take font, color, and spacing settings from the theme itself rather than using standard presets. This makes it far less likely for a site to break (or just look off) when you—or a client—experiment and make updates.

Our goal is always to make your life both easier and more beautiful. This new resource does just that. Check out the WordPress.com Pattern Library today to enhance your website-building experience!

Missing out on the latest WordPress.com developments? Enter your email below to receive future announcements direct to your inbox. An email confirmation will be sent before you will start receiving notifications—please check your spam folder if you don't receive this.

10 WordPress Influencers to Follow in 2024

Democraten NU Democraten NU Almelo 09-04-2024 19:18

In this “Build and Beyond” video, Jamie Marsland highlights 10 WordPressers to keep an eye on in 2024.

A couple of weeks ago, we shared a list of 15 WordPress developers you should follow to stay on top of WordPress development news and tips. This video broadens the scope and features folks worth following, regardless of your role or experience with WordPress. If you’re at all interested in or curious about WordPress, these are folks to pay attention to.

Interested in a free trial that allows you to test our all that WordPress.com has to offer? Click below:

Remkus is a well-known figure in the WordPress community, recognized for his contributions to WordPress development and his overall expertise in web technology.

Kevin helps digital agency owners, freelancers, and web designers to learn best practices for UX/UI design, development, and CSS.

Tyler has free video lessons on YouTube that teach people how to create their own professional website without any coding experience.

Sabrina is a WordPress performance engineer, who’s daily work is to speed up WordPress websites, plugins, and themes.

Mike is a designer and principal software engineer from the USA. He builds killer products and brands that people love, including the fantastic Ollie WordPress theme.

Jonathan runs a small web development agency, creates courses, and makes YouTube videos. He started is WordPress-focused YouTube channel in late 2018.

Birgit works as developer advocate for WordPress, curates community voices on Gutenberg Times, and co-hosts the Gutenberg Changelog podcast.

For the past 20 years David has worked professionally developing websites and in IT management.

Paul has over 15 years of commercial web design and development experience working on a large range of diverse projects, with clients ranging from start-ups to blue-chip companies.

The WP Minute, founded by Matt, is a website dedicated to delivering the most important news and topics from the WordPress ecosystem, keeping WordPress professionals informed, educated, and entertained.

Imran has 17+ years of web design and marketing experience. His YouTube channel has over 55k YouTube subscribers.

Rich describes himself as a multidisciplinary maker specializing in the intersection of product, design, and engineering.

Jamie has trained over 5,000 people on WordPress in the past 10 years, and he also makes WordPress plugins. His YouTube channel is dedicated to helping people with WordPress Blocks.

Missing out on the latest WordPress.com developments? Enter your email below to receive future announcements direct to your inbox. An email confirmation will be sent before you will start receiving notifications—please check your spam folder if you don't receive this.

In naam van klimaatverandering wordt ontbossing versneld

Partij Vrij Almelo (PVA) Partij Vrij Almelo (PVA) Almelo 08-04-2024 15:33

Ruim 10 procent van het landoppervlak in Nederland is bos. Daarna nam het bosoppervlak af, tot nu ongeveer 363.800 hectare. De afgelopen vier jaar is geprobeerd meer bos te planten. Dat is deels gelukt, maar netto is er nog steeds een ontbossing

Als men op grote schaal bomen zou planten, in plaats van windmolenparken, lithiumbatterijen en andere hoogtechnologische onzin, dan zou het “klimaatprobleem” nog voor 2030 of 2050 zijn opgelost. Een verbod op het transport van biobrandstof zou daarbij behulpzaam zijn, want terwijl men in Afrika en Spanje bomen plant, worden massa’s bomen in Brazilie en Canada gekapt, versnipperd, in dieselschepen gestort en naar Europa vervoerd, om daar te worden verbrand in elektriciteitscentrales. En dat noemt men dan groene stroom. Bijna de helft van de oorspronkelijke bossen op aarde is al verdwenen. Een recente analyse van het Nederlandse bosareaal op basis van topografische kaarten en luchtfoto’s, die geplubiceerd is in het Vakblad Natuur, Bos en Landschap, laat zien dat ook de oppervlakte bos in Nederland sinds 2013 jaarlijks met 1350 hectare is afgenomen.

Per jaar is gemiddeld 3036 hectare bos verdwenen, terwijl we al het dunst beboste land van Europa zijn. Zijn we gek geworden? Als men zo bang is voor CO2, waarom plant men dan geen bomen, in plaats van die smerige windmolens? Bomen nemen CO2 op! Ze houden ook het grondwater vast met hun wortels en veranderen  zo woestijnen in parklandschappen. Geen windmolenparken, maar echte parken waarin je kunt wandelen, voedsel verbouwen en dieren laten grazen! Deze groene revolutie is goed voor de natuur, de planten en dieren, de mensen en het klimaat. Voor het bedrag van 1 miljard dollar kan men de hele aarde weer groen maken. In plaats daarvan pompt men miljarden in de strijd tegen CO2. Dat is toch te dwaas… Er is niets mis met CO2, maar de meeste mensen zijn dusdanig gefopt door het IPCC en de “groene” propaganda, dat ze deze simpele waarheid niet meer zien.

Grote delen van wat ooit vruchtbaar land was, veranderden langzaam maar zeker in woestijnen. Het gedrag van mensen heeft daar de laatste eeuw sterk aan bijgedragen. Verstedelijking maakt dat er minder bomen groeien, het rooien van oerwouden draagt daar ook flink toe bij. En het zogenaamde natuurbeheer blijkt vaak averechts te werken. Bomen nemen niet alleen CO2 op uit de lucht maar brengen ook nog eens de temperatuur naar beneden op het aardoppervlak. Bomen werken namelijk ook nog eens verkoelend waarbij die 1,5 graad Celsius makkelijk mee gehaald kan worden van dat oh zo goed uitgewerkte klimaat akkoord. Als je de geschiedenis boeken induikt werd er al 100 jaar geleden hierop ingespeeld want in heel Afrika werd verteld dat bomen je water opdrinken dus die moet je eruit halen.

Hier onder de werking van worteldruk, uitgelegd door een biologie leraar. Het water dat verdampt via de huidmondjes ontrekt de warmte uit lucht. En zo zie je maar weer dat een boom eigenlijk ook een warmtepomp is waar je de klimaatgekkies nog nooit over hebt gehoord en ook niets terug zal vinden in het klimaat akkoord.

Bomvolle zaal vol met tegenstanders mega windturbines

Partij Vrij Almelo (PVA) Partij Vrij Almelo (PVA) Almelo 05-04-2024 13:06

Mega windturbines van 280 meter hoog

Permanente hinder van geluid, slagschaduw, knipperende lichten en voelbare geluidstrillingen. Leefbaarheid aangetast voor mens, dier en natuur.

Grote zorgen bij inwoners van Overijssel over de mogelijke komst van windmolens in hun omgeving. Het prachtige Nederlandse landschap verandert zienderogen in een industriële omgeving, volgebouwd met mega windturbines.

Zo ook in het Overijsselse Daarle, waar de provincie clusters met windturbines wil bouwen, tot boosheid van veel bewoners. Stichting Tegenwind Daarle/Wierden en Clintel (Stichting Climate Intelligence) slaan nu de handen ineen bij de eerste editie van Clintel on Tour  op 4 april in Hoge Hexel.

Bert Weteringe is vliegtuigbouwkundig ingenieur, auteur van het boek ‘Windhandel’ en is één van de sprekers op deze avond met als thema: wat is de impact van deze grootschalige energieopwekking met windturbines op de mens, natuur en samenleving en hoe kun je als inwoner het tij keren?

De weerstand tegen windmolens is door heel Nederland zichtbaar. Overal zijn actiegroepen actief. Dat dat juist nu gebeurt is niet verwonderlijk. Veel groepen voelen zich overvallen door de plannen zoals die zijn opgesteld in de zogenoemde Regionale Energie Strategieën.

Online is dat ook zichtbaar in de vorm van verschillende protestpetities. Om samen een vuist te kunnen maken moeten we met zoveel mogelijk verschillende actiegroepen optrekken. Die samenwerking moet, als het aan ons ligt, uitgroeien tot een nationale actiegroep. “We moeten ons verenigen met heel Nederland”.

De Partij Vrij Almelo was hierbij aanwezig.

Hier maken artsen het medisch onderzoek naar windturbines voor iedereen toegankelijk

Streamlining Your Content Creation: Adding Images From Your Phone With Ease

Democraten NU Democraten NU Almelo 04-04-2024 19:35

The internet is rife with small annoyances, which often lead to breakthroughs in user experience. For example, needing to hit “refresh” or “next page” led to infinite scroll, which is now baked into our media consumption habits.

Today, we’re excited to share a new feature in the desktop editor and Jetpack mobile app that eliminates one of those small annoyances and makes it a breeze to upload media to your WordPress posts and pages.

While working in the editor on your laptop or desktop device, you can now seamlessly add photos directly from your phone.

Here’s how to do it:

Insert an “Image” or “Gallery” Block on your post/page.

Click “Select Image”: From the dropdown menu, select “Your Phone.”

Use your phone to scan the QR code: This will automatically open the Jetpack app and then your photo library.

Choose your image(s): From there, simply click the image or images you wish to add to your post/page.

Click “Add”: Watch your image(s) automagically appear in your desktop editor.

Check it out in action below:

We hope this will inspire you to snap even more photos and share them with the world.

Missing out on the latest WordPress.com developments? Enter your email below to receive future announcements direct to your inbox. An email confirmation will be sent before you will start receiving notifications—please check your spam folder if you don't receive this.

Zie je content die volgens jou niet op deze site hoort? Check onze disclaimer.