WordPress 6.9 begins its path toward its general release with the first beta version, which already includes all the new features of this update.

Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.

Hello, I’m Alicia Ireland, and you’re listening to WPpodcast, bringing the weekly news from the WordPress Community.

In this episode, you’ll find the information from October 20 to 26, 2025.

WordPress 6.9 now has its first beta available, marking the start of the last major update of the year. This version focuses on improving site editing, with more intuitive template management, the arrival of the Abilities API, and progress in the Interactivity API. It also introduces the Notes feature, which allows leaving comments directly on blocks, enhancing collaboration in content creation.

Among the highlights are the Accordion block, the Terms Query block, the option to hide blocks without deleting them, and border radius presets to maintain visual consistency across themes. In addition, global styles are now extended to forms, the command palette has been refined, and there are improvements to DataViews, the HTML API, and overall performance.

The Test team has scheduled several review sessions through the end of November to ensure stability before the official release, planned for December 2, 2025. The community is encouraged to test the beta in staging environments and share bugs or suggestions through GitHub or Slack.

As mentioned, the new version officially includes the Accordion block, which allows collapsible content sections—ideal for FAQs or lengthy sections. On the Developers Blog, there’s a guide article for developers explaining how to customize its design to fit any theme.

Each accordion consists of four blocks: the main container, the individual items, the headers, and the panels. These can be styled via the theme.json file or with custom CSS, adjusting borders, colors, shadows, and typography.

Additionally, style variations can be created to offer different looks within the editor, making it easier for users to choose predefined designs without touching code. This allows themes to include fully customized accordions consistent with their visual identity.

The Core team has proposed updating the WordPress coding standards to explicitly state that all PHP files must use the .php extension.

The reason is to ensure compatibility and security across servers, as some environments, such as Debian or Fedora, interpret extensions like .php3 or .phtml differently. Always using .php prevents code from being displayed as plain text or not executing properly.

This consistency also allows tools like PHP Code Sniffer and the WordPress Coding Standards to correctly analyze all PHP files, strengthening code quality and uniformity across the ecosystem.

The Playground team has launched over 30 improvements in recent months, including support for naming saved projects, better deployment in self-hosted environments, and a refreshed interface with clearer icons. Documentation has also been expanded, translations added in Japanese, French, Spanish, and Portuguese, and new examples included for PHP-WASM and CLI.

Technical highlights include step-by-step debugging with PHP.wasm in PHP Storm and Visual Studio Code, as well as progress in SQLite to improve compatibility with MySQL and tools like phpMyAdmin.

This reinforces Playground’s role as a fast, accessible WordPress development environment, combining performance, portability, and clearer documentation to make experimentation easier for developers and educators alike.

The Community team is looking for developers to improve WordPress event tools, including CampTix, GatherPress, and the events.wordpress.org platform. Planned improvements range from a more modern ticketing system to a future WordPress Events App.

CampTix needs new features such as invitation letter generation, better multi-purchase flow, and more reporting options. GatherPress requires real-world testing and technical support to integrate with WordPress.org, along with messaging and data export capabilities.

Improvements are also proposed for the events website: budgeting tools, planning features, and user experience enhancements. A mobile app for WordCamp is also being considered, featuring messaging, networking, and interactive maps, inspired by a prototype already in use in Spain.

And finally, this podcast is distributed under a Creative Commons license as a derivative version of the podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WPpodcast .org.

Thanks for listening, and until the next episode!

The main focus of WordPress 6.9 is to integrate new blocks and, above all, finalize the integration of the Abilities API into core.

Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.

Hello, I’m Alicia Ireland, and you’re listening to WPpodcast, bringing the weekly news from the WordPress Community.

In this episode, you’ll find the information from October 13 to 19, 2025.

The AI team is concentrating all its efforts to ensure that the Abilities API is ready in time for the WordPress 6.9 beta, scheduled for October 21. They have extended internal deadlines to complete critical reviews and merges without compromising stability.

The priority is to ensure that essential functions, such as registering and retrieving abilities, are ready, while secondary features like filtering are postponed to avoid unnecessary complexity. It was also highlighted that the GatherPress plugin already uses the API with eleven implemented abilities, demonstrating its maturity and real applicability within the WordPress ecosystem.

And finally, this podcast is distributed under a Creative Commons license as a derivative version of the podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WPpodcast .org.

Thanks for listening, and until the next episode!

WordPress 6.9 will include the option to leave notes for other writers and reviewers, linked to the content of blocks within the editor.

Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.

Hello, I’m Alicia Ireland, and you’re listening to WPpodcast, bringing the weekly news from the WordPress Community.

In this episode, you’ll find the information from October 6 to 12, 2025.

It’s time to get ready for WordPress 6.9. In just one week, the first beta version will be released on October 21, 2025. Three weeks later will come the first release candidate on November 11, and the final release is set for December 2, 2025, at 15:00 UTC.

The AI team confirmed the deployment of the MCP Adapter on WordPress.com, a key step to test this new technology in real environments. They also reviewed progress on the Abilities repository, which already has several active contributions, and planned a better documentation structure for the project.

Regarding the Abilities API, it was agreed that categories will be mandatory from the first version to maintain order and scalability. The discussion focused on defining which parameters should go at the root level and which in the “meta” object, to avoid overloading the API. They also discussed adapting the PHP AI client to WordPress coding standards and advancing the experiments plugin, whose next development phase will begin soon.

On the Developers Blog, there’s a summary of recent updates, including the fact that global styles now also apply to form controls. With this improvement, themes can define colors, borders, or typography for text fields, dropdowns, or buttons directly in theme.json. This way, all forms across the site—such as search, comments, or plugin forms—automatically inherit the general design without the need for additional CSS.

The Notes feature, formerly known as block comments, greatly improves collaboration within the editor. It allows users to leave comments directly on blocks, with clearer alerts when the associated block is deleted, and a visual system that highlights the commented content. Performance has also been optimized with a new hook that better manages conversations, making content review smoother and more practical for editorial teams.

The Test team has issued several calls to action.

The first thing to test is the changes in template management within the Site Editor. You can now create, edit, and save multiple versions of the same template, enable or disable each one, and keep custom templates when switching themes. Separate views have been added for active and custom templates, along with improvements to revisions, duplication, and deletion.

They also invite you to test a new feature in Gutenberg 21.8: the ability to hide blocks on the frontend without deleting them from the editor. This option lets you keep content or designs hidden, making it easier to experiment without losing information or affecting the published version. Users can toggle the visibility of any block from the options menu or the list view, even within groups or columns.

And finally, they’re asking for help testing the new Accordion block, which will arrive with WordPress 6.9. This block allows expandable content sections, ideal for FAQs or lists of information. Each accordion contains several items with a title and expandable content area and can be styled with global design settings.

The Accessibility team has shared several updates. The redesign of the admin area has been removed from the WordPress 6.9 plan, which will reduce the design team’s workload. There will also be no new default theme in this release.

In documentation, the WP Accessibility Knowledge Base is now ready to receive contributions, and a Website Accessibility Conformance Evaluation Methodology audit will be carried out in November to ensure compliance with standards. Contributions are encouraged via GitHub, though it’s recommended to focus on familiar topics, as AI is not yet reliable for accessibility tasks.

And finally, this podcast is distributed under a Creative Commons license as a derivative version of the podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WPpodcast .org.

Thanks for listening, and until the next episode!

A security update that fixes two issues has led to the release of WordPress 6.8.3, an update that is recommended to be applied urgently on all sites.

Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.

Hello, I’m Alicia Ireland, and you’re listening to WPpodcast, bringing the weekly news from the WordPress Community.

In this episode, you’ll find the information from September 29 to October 5, 2025.

WordPress 6.8.3 is now available as a security release. It includes two fixes: a data exposure issue that allowed authenticated users to access restricted content, and an XSS vulnerability in navigation menus that required an authenticated role.

The update is applied automatically on sites with background updates enabled. All users are advised to update as soon as possible. These fixes have also been backported to previous supported branches, from 4.7 onwards.

WordPress 6.9 will introduce border radius size presets, a new option for theme developers. They can be defined in the theme.json file, creating a list of values with name, slug, and CSS size. This generates reusable variables to apply rounded corners consistently across compatible blocks.

The interface shows a slider or a dropdown depending on the number of presets defined. These values are converted into custom CSS properties, making it easier to maintain a consistent style throughout the theme and simplifying visual editing.

Gutenberg 21.7 arrives with interesting updates. The command palette can now be used across all editor screens, streamlining navigation. A new experimental block, Terms Query, also appears, designed to display taxonomies in a way similar to the post query block. Additionally, unsynced patterns and template parts now have a content-only editing option, and improvements continue in the block-level comments feature.

On the technical side, new controls have been added in DataViews, such as color, password, or phone fields, along with validation improvements. The project continues to receive contributions from collaborators, including several first-time contributors, showing the vitality of the community.

The AI team focused its latest meeting on advancing with the Abilities API and the MCP Adapter, in preparation for WordPress 6.9. It was agreed to limit the scope to include only the API and a couple of small stable tools in core, while other proposals will be tested in the experiments plugin. It was also decided that categories will be required in ability registration, to make organization and interaction with AI easier.

Regarding the MCP Adapter, merging version 0.3, still considered alpha, was approved as soon as possible to expand testing during the 6.9 beta. Although there are community concerns about the stability of the protocol, the team emphasized that the choice of the adapter is precisely to ensure future flexibility if the standard changes.

The Test team is overhauling the Test Handbook, which had not been updated in a long time. The goal is to keep the documentation up to date with new protocols and recent decisions, moving all content to the GitHub repository to improve traceability and collaborative work.

The plan includes syncing existing documentation, reviewing materials such as images or videos, and creating a content manifesto. Once this phase is completed, future improvements will be managed with issues and pull requests in GitHub, ensuring transparency, quality control, and broader community participation.

The Community team has reported that an organizer misused leftover funds from a WordCamp in 2024 for personal expenses, totaling about 734 dollars. Despite several attempts, the money could not be recovered, and new measures have been decided: from now on, global grants will be delivered in several small payments instead of a single one, to reduce the risk of mismanaged leftovers.

As for sanctions, the person involved has been reported to local authorities, permanently banned from organizing and participating in WordPress events, and their WordPress.org and Slack accounts have been permanently blocked. The team stresses that event organization is based on trust, and although this is an isolated case, these measures have been taken to protect the community.

And finally, this podcast is distributed under a Creative Commons license as a derivative version of the podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WPpodcast .org.

Thanks for listening, and until the next episode!

WordPress 6.9 will arrive on December 2, and we are just one month away from the release of the first beta version, which should already include all the new features.

Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.

Hello, I’m Alicia Ireland, and you’re listening to WPpodcast, bringing the weekly news from the WordPress Community.

In this episode, you’ll find the information from September 15 to 21, 2025.

WordPress 6.9 is moving forward with several key updates as it approaches beta 1, scheduled for October 21.

Among the changes in development are the ability to hide blocks, which is being refined as an experiment within Gutenberg, and the expansion of the command palette, although its use on the frontend has been ruled out for now. Work is also underway on block-level comments, improving the interface, and resolving accessibility issues before graduating the feature from experimental to stable.

Another focus is the new blocks that could be added to this version: accordion, query terms, breadcrumbs for posts, icons, responsive text, tabs, and others in stabilization, such as the table of contents block or the estimated reading time block. All of them are grouped as experiments in Gutenberg and will be individually evaluated to decide their inclusion in the final version of 6.9. The community is encouraged to test them and report issues to polish the experience.

Finally, there is an effort to simplify site editing, exploring two paths: a switched writing and design mode, or an approach where patterns are content only by default. The idea is to offer a simpler experience, without adding unnecessary layers of complexity, allowing users to focus on content and detail patterns only when necessary. Although still in an experimental phase, this direction points to being one of the most important conceptual changes that could shape editing in WordPress 6.9.

The AI team is following the discussion on the future of the Abilities API, key for WordPress 6.9. It was recommended to separate CRUD operations into more specific abilities, create distinct capabilities for each content type, and define a more granular and secure permission system.

The next steps include finalizing the scope of the API in version 6.9, implementing filters by categories and namespaces, and establishing exposure controls in the REST API. The goal is for the system to be scalable and clear both for developers and for its integration with artificial intelligence models.

The WordPress 6.9 beta is scheduled for October 21, at which time the first version of the Abilities API will be integrated into core. This has led to discussions about changing the API package type to a WordPress plugin, expectations around Composer packages, and the possible inclusion of client-side abilities.

It was decided to release a minimum number of initial abilities, including one for “discovering abilities”, and to move forward with the publication of MCP Adapter 0.2.0. In a few days it will be decided which specific abilities will arrive with WordPress 6.9.

The BuddyPress team has released versions 14.4.0, 12.6.0, and 11.5.1 as maintenance and security updates. These versions fix a flaw in the REST API that could expose registration data, including email addresses, and improve the email unsubscribe function. Updating immediately is recommended to ensure site security.

And finally, this podcast is distributed under a Creative Commons license as a derivative version of the podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WPpodcast .org.

Thanks for listening, and until the next episode!

A new Core team, a sort of Meta-Core, has been launched to coordinate all aspects of the WordPress core.

Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.

Hello, I’m Alicia Ireland, and you’re listening to WPpodcast, bringing the weekly news from the WordPress Community.

In this episode, you’ll find the information from September 15 to 21, 2025.

The creation of the Core Program Team has been announced, a new team whose goal is to improve coordination among the different WordPress development teams, the Core, increase efficiency, and make it easier for new contributors to integrate without friction.

The role of the team will not be to define the direction of the product, but to facilitate processes: documenting best practices, making roadmaps visible, and supporting new teams with clear processes.

Tammie Lister joins as the first representative, and the initiative is part of an experimental phase to refine internal collaboration.

The focus is on removing obstacles and connecting the different work areas; each Core team keeps its autonomy, but now there will be a point of connection.

And the final details are already being refined for the release of WordPress 6.9, calling regular bug scrub sessions to make sure the release comes out as stable as possible. These meetings will be held twice a week during the “alpha” phase, with the goal of covering different time zones and making global participation easier. As the release date approaches, the number of sessions is expected to increase if needed.

The Documentation team has pointed out that the main Core team was not clear on what the Documentation team’s work is during the launch of a new version.

For version 6.9, a temporary Docs Liaison has been appointed, with the mission of assisting the release team, reviewing the roadmap for user documentation, and collaborating on the day of the final release.

In addition, to help other documenters learn this process, at the next online Documentation Contributor Day there will be a mentoring session on this workflow, and videos will be recorded to be added to the Handbook in the section on documentation process during a new version release.

As a result of the situation of incorporating Documentation into releases, a team member has been temporarily stepped away from their duties.

The decision was made after a series of comments that, according to team leaders, were not aligned with the group’s purposes, which created tensions.

Leadership first tried to handle this privately, asking them to stop publishing those discussions, but since the situation did not change, it was decided to take a step back so their participation could be reassessed. An apology was also issued to the community and to those who felt affected, clarifying that those comments do not reflect the official stance of the Documentation team.

The Community team has launched a call for mentors for the WordPress Credits program, the educational initiative to connect university students with real open source projects.

Mentors, now called Event Supporters, must have experience organizing a WordCamp, have at least 2 hours a week available throughout the program (which lasts between 13 and 18 weeks), meet with their mentees weekly, provide asynchronous support, and commit to offering useful and real mentorship.

Responsibilities include guiding up to 5 students per mentor, helping them navigate contribution tasks, fostering collaboration and accountability, and providing feedback on their progress and final project. Although for now only a limited number of universities in Italy and Costa Rica are participating, WordPress aims to build a global network of mentors for when more institutions join.

And finally, this podcast is distributed under a Creative Commons license as a derivative version of the podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WPpodcast .org.

Thanks for listening, and until the next episode!

The WordPress core will incorporate native functionality to include embedded images in emails without relying on external links or BASE64 content.

Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.

Hello, I’m Alicia Ireland, and you’re listening to WPpodcast, bringing the weekly news from the WordPress Community.

In this episode, you’ll find the information from September 1 to 7, 2025.

The Core team has introduced improved support for embedded images directly within system-generated emails. It is now possible to include inline images in the email body, ensuring they display correctly in clients that block external images or don’t automatically load attachments. The approach aims for greater visual fidelity without sacrificing compatibility or delivery reliability.

This functionality is implemented with a system that uses content IDs to reference embedded images, instead of relying on external links or base64 encoding, which often fail or are blocked by email clients. The result is more robust emails, visually more consistent, and less likely to break due to recipient client restrictions.

On the Developer Blog, there is an explanation of how to take plugin development a step further by integrating PHP namespaces, Composer autoloading, and unified coding standards for PHP, JavaScript, and CSS. The goal is to maintain code quality and scale efficiently, both for individual developers and large teams.

Concrete steps are detailed: configuring PSR-4 autoloading in a composer.json, splitting functionality into classes within clear namespaces, using linting and auto-formatting to maintain consistent standards across all used languages, and organizing the plugin structure to be modular, maintainable, and free from naming conflicts.

The Hosting team has launched its annual survey to analyze aspects of how hosting companies that provide WordPress services operate, with questions covering the company, technology stack, security practices, experience with WordPress, and support, among others.

The survey is now available and will close on October 15.

The Plugins team has published a recap noting that there are 60,187 plugins in the WordPress.org directory, and that in the first 9 months more than 7,600 plugins have been submitted for review, which is 87% more than during the entire previous year.

A very interesting data point is that, thanks to the new review and control tools, 65% of developers follow the review process, representing a 17% increase compared to last year, thereby improving the workflow.

And finally, this podcast is distributed under a Creative Commons license as a derivative version of the podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WPpodcast .org.

Thanks for listening, and until the next episode!

The WordPress core will incorporate native functionality to include embedded images in emails without relying on external links or BASE64 content.

Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.

Hello, I’m Alicia Ireland, and you’re listening to WPpodcast, bringing the weekly news from the WordPress Community.

In this episode, you’ll find the information from September 1 to 7, 2025.

The Core team has introduced improved support for embedded images directly within system-generated emails. It is now possible to include inline images in the email body, ensuring they display correctly in clients that block external images or don’t automatically load attachments. The approach aims for greater visual fidelity without sacrificing compatibility or delivery reliability.

This functionality is implemented with a system that uses content IDs to reference embedded images, instead of relying on external links or base64 encoding, which often fail or are blocked by email clients. The result is more robust emails, visually more consistent, and less likely to break due to recipient client restrictions.

On the Developer Blog, there is an explanation of how to take plugin development a step further by integrating PHP namespaces, Composer autoloading, and unified coding standards for PHP, JavaScript, and CSS. The goal is to maintain code quality and scale efficiently, both for individual developers and large teams.

Concrete steps are detailed: configuring PSR-4 autoloading in a composer.json, splitting functionality into classes within clear namespaces, using linting and auto-formatting to maintain consistent standards across all used languages, and organizing the plugin structure to be modular, maintainable, and free from naming conflicts.

The Hosting team has launched its annual survey to analyze aspects of how hosting companies that provide WordPress services operate, with questions covering the company, technology stack, security practices, experience with WordPress, and support, among others.

The survey is now available and will close on October 15.

The Plugins team has published a recap noting that there are 60,187 plugins in the WordPress.org directory, and that in the first 9 months more than 7,600 plugins have been submitted for review, which is 87% more than during the entire previous year.

A very interesting data point is that, thanks to the new review and control tools, 65% of developers follow the review process, representing a 17% increase compared to last year, thereby improving the workflow.

And finally, this podcast is distributed under a Creative Commons license as a derivative version of the podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WPpodcast .org.

Thanks for listening, and until the next episode!

The latest version of the Gutenberg plugin introduces the first phase of the accordion block, which is expected to be included in WordPress 6.9.

Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.

Hello, I’m Alicia Ireland, and you’re listening to WPpodcast, bringing the weekly news from the WordPress Community.

In this episode, you’ll find the information from August 25 to 31, 2025.

Gutenberg 21.5 introduces the accordion block as its main feature, which could make its way into WordPress 6.9. It’s still in experimental mode but should already be functional for testing.

It also extends the Command Palette to the entire admin dashboard, not just the Editor, and introduces a default border-radius system applied consistently to all blocks that should include it.

On the Developer Blog, an advanced guide was published on refactoring multi-block plugins. Starting from a simpler base, it proposes a more robust approach that makes scaling and maintaining plugins easier. The new organization separates static, dynamic, and interactive blocks into individual folders under src/blocks, while block registration is automated through a blocks-manifest.php file. This eliminates the need to manually register each block and leverages modern APIs depending on the WordPress version for cleaner management.

The guide also covers adding interactive blocks using specific templates and adapting the build process with Webpack. It explains how to include shared assets via separate enqueue functions and how to extend Webpack’s default configuration to compile those scripts alongside the rest of the plugin. This modular architecture significantly improves performance and maintainability for plugins with many blocks.

WordCamp US 2025 took place in Portland from August 26–29 at the Oregon Convention Center, bringing together developers, designers, content creators, and WordPress enthusiasts. The event opened with Contributor Day, a collaborative session where participants of all levels contributed to teams like Core, Hosting, Test, AI, and Community, working on code, documentation, testing, and improvements. Both in-person and remote options were available.

The main conference days included Showcase Day, featuring live demos, real-world case studies, and inspiration around design, accessibility, performance, AI, and more. Highlights included “The System is the Strategy” by Tammie Lister on design systems, and “Unlock Developer Superpowers with AI” by Adam Silverstein on AI in workflows. There were also sessions highlighting stories from creators like YouTubers and WordPress influencers, alongside a lively Sponsor Hall that combined networking, demos, and even an arcade, reinforcing the community spirit.

The closing remarks came from Matt Mullenweg, who shared WordPress growth stats: over 124,000 new social media followers and more than a 10% increase in WordPress.org users. He also highlighted community projects such as WordPress Campus Connect, which has already benefited 570 students across 11 events, reflecting a 32.8% increase in events compared to 2024. Additionally, the Open Horizons scholarship was introduced, awarding $14,670 to six participants from five countries. The event concluded with a closing party in Portland and a message of gratitude to everyone involved.

And finally, this podcast is distributed under a Creative Commons license as a derivative version of the podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WPpodcast .org.

Thanks for listening, and until the next episode!

This week WordCamp US 2025 is taking place, with high-profile guests and a focus on the upcoming release of WordPress 6.9.

Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.

Hello, I’m Alicia Ireland, and you’re listening to WPpodcast, bringing the weekly news from the WordPress Community.

In this episode, you’ll find the information from August 18 to 24, 2025.

As previously announced, WordPress 6.9 will have a much smaller release squad, and this time only 11 people will be leading the release.

Once again, under the leadership of Matt Mullenweg, the team includes both well-known contributors who have been part of the project for a long time and some who have recently been involved as Team Reps.

On the Developer Blog, you’ll find an article about registering custom social icons in WordPress 6.9, which will extend functionality to the already long list of existing icons.

It’s a technical article for developers that shows how to add new icons with a plugin and serves as a guide to one of the new features coming in the next release.

This week WordCamp US 2025 is happening, running from Tuesday, August 26, which will be Contributor Day, through Friday, August 29, when the event wraps up. The conference is highly business-focused and runs entirely during the week.

The event will open with a keynote by John Maeda, head of Microsoft’s AI division and a former Automattic employee. The closing party will take place at the World Forestry Center, which will also allow attendees to visit its museum.

And finally, this podcast is distributed under a Creative Commons license as a derivative version of the podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WPpodcast .org.

Thanks for listening, and until the next episode!