{"id":30468,"date":"2024-04-17T13:57:00","date_gmt":"2024-04-17T12:57:00","guid":{"rendered":"https:\/\/www.web-systems.pl\/wordpress-6-5-what-changes-for-company-website\/"},"modified":"2026-10-13T14:39:51","modified_gmt":"2026-10-13T13:39:51","slug":"wordpress-6-5-what-changes-for-company-website","status":"publish","type":"post","link":"https:\/\/www.web-systems.pl\/en\/wordpress-6-5-what-changes-for-company-website\/","title":{"rendered":"WordPress 6.5: what it changes in day-to-day work on a company website"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>WordPress 6.5<\/strong> &#8220;Regina&#8221; was released on April 2, 2024. Editors get font management straight from the dashboard and a tidier way of installing plugins, while the people who build the site get two new APIs for working with blocks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We rely here on the <a href=\"https:\/\/wordpress.org\/news\/2024\/04\/regina\/\" rel=\"nofollow noopener\" target=\"_blank\">official Regina release announcement<\/a>. The order is this: first what the person editing content gains, then what the developer gets, and finally a list of things to check before you click &#8220;update&#8221;. And we look at all of it through the eyes of a company that has a working website and does not want to take it down with a single click.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of contents<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.web-systems.pl\/en\/wordpress-6-5-what-changes-for-company-website\/#Which_WordPress_65_features_will_a_company_notice_day_to_day\" >Which WordPress 6.5 features will a company notice day to day?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.web-systems.pl\/en\/wordpress-6-5-what-changes-for-company-website\/#The_WordPress_Font_Library_typography_without_touching_code\" >The WordPress Font Library: typography without touching code<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.web-systems.pl\/en\/wordpress-6-5-what-changes-for-company-website\/#Plugin_dependencies_fewer_errors_when_installing_add-ons\" >Plugin dependencies: fewer errors when installing add-ons<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.web-systems.pl\/en\/wordpress-6-5-what-changes-for-company-website\/#Interactivity_API_and_Block_Bindings_API_what_does_the_site_developer_gain\" >Interactivity API and Block Bindings API: what does the site developer gain?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.web-systems.pl\/en\/wordpress-6-5-what-changes-for-company-website\/#Editor_and_accessibility_improvements_in_everyday_editing\" >Editor and accessibility improvements in everyday editing<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.web-systems.pl\/en\/wordpress-6-5-what-changes-for-company-website\/#Updating_to_WordPress_65_what_to_check_before_you_click\" >Updating to WordPress 6.5: what to check before you click?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.web-systems.pl\/en\/wordpress-6-5-what-changes-for-company-website\/#Frequently_asked_questions\" >Frequently asked questions<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.web-systems.pl\/en\/wordpress-6-5-what-changes-for-company-website\/#Is_updating_to_WordPress_65_safe_for_a_company_website\" >Is updating to WordPress 6.5 safe for a company website?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.web-systems.pl\/en\/wordpress-6-5-what-changes-for-company-website\/#Does_the_Font_Library_work_in_every_theme\" >Does the Font Library work in every theme?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.web-systems.pl\/en\/wordpress-6-5-what-changes-for-company-website\/#Does_the_Interactivity_API_require_changes_to_an_existing_site\" >Does the Interactivity API require changes to an existing site?<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Which_WordPress_65_features_will_a_company_notice_day_to_day\"><\/span>Which WordPress 6.5 features will a company notice day to day?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The changes come in two kinds. The ones visible in the dashboard are fonts, plugins and the editor. The technical ones, meaning the Interactivity API and the Block Bindings API, will be useful to whoever builds your site. You will see the first group right after logging in. The second? Only with the next round of development work.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Font Library<\/strong> - managing typefaces in the Site Editor; relevant to the editor and to whoever looks after the look of the site.<\/li>\n<li><strong>Plugin dependencies<\/strong> - information about what an add-on needs in order to work; relevant to the administrator.<\/li>\n<li><strong>Interactivity API<\/strong> - a standard for building interactive front-end elements; relevant to the developer.<\/li>\n<li><strong>Block Bindings API<\/strong> - connecting blocks to data; relevant to the developer.<\/li>\n<li><strong>Editor and accessibility improvements<\/strong> - more comfortable work in the dashboard; relevant to the whole editorial team.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Publishing posts itself? No change. Nobody on the team has to learn the dashboard from scratch, and the new features can be picked up calmly, bit by bit.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"The_WordPress_Font_Library_typography_without_touching_code\"><\/span>The WordPress Font Library: typography without touching code<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">You install, enable and remove typefaces in the Site Editor, regardless of the active theme. That&#8217;s it. For a company it simply means it is easier to stay consistent with the visual identity, because changing the heading font stops being a small job for a developer (and &#8220;small&#8221; jobs like that can sit in the queue for quite a while). And the typefaces stay in place after you switch themes - they are not tied to the theme.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">But there is a catch. The feature works in block themes, and every extra typeface is another file that the visitor&#8217;s browser has to download. In my opinion there is no point going overboard: a few variants are enough, usually one for headings and one for body text. If you want to better understand how typography ties in with the rest of the editor, have a look at our article on <a href=\"https:\/\/www.web-systems.pl\/en\/advanced-gutenberg-editing-blocks-dynamic-content\/\">Gutenberg blocks and components<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Plugin_dependencies_fewer_errors_when_installing_add-ons\"><\/span>Plugin dependencies: fewer errors when installing add-ons<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The mechanism is simple: an add-on declares which other extensions it needs, and the dashboard shows this before activation. The administrator sees a clear message instead of a crash after enabling an extension whose base plugin is missing. It works the other way round too. The system will not let you deactivate an add-on that others depend on for as long as they are active.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A typical case is a store extension, for example a payment or shipping module, that requires the main plugin. Until now you had to know the installation order or dig it out of the documentation. Now the dashboard itself suggests it. Only it will not choose anything for you, so it is still worth knowing which <a href=\"https:\/\/www.web-systems.pl\/en\/wordpress-plugins-must-haves-for-every-site\/\">essential WordPress plugins<\/a> you actually need and which ones only weigh the site down.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Interactivity_API_and_Block_Bindings_API_what_does_the_site_developer_gain\"><\/span>Interactivity API and Block Bindings API: what does the site developer gain?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">These are tools for developers. According to the announcement, they open up new possibilities for interaction on the front end and make it easier to connect blocks to data. The site owner will not see them in the dashboard. They will feel them instead in the way future jobs get done.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The <strong>Interactivity API<\/strong> is a standard way of building elements that respond to what the user does without reloading the page, such as filtering a list or searching. Until now every developer solved this in their own way. The result? Having someone else take over a project could be difficult.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The <strong>Block Bindings API<\/strong> lets a core block, for example a paragraph or a heading, display a value from a custom field. You enter the data once, say a phone number or opening hours, and it appears in many places and updates everywhere at the same time. All in all, there is one takeaway for a company: less custom code to maintain. Except that the benefit only comes with new development work, not right away.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Editor_and_accessibility_improvements_in_everyday_editing\"><\/span>Editor and accessibility improvements in everyday editing<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In this release the editor received usability fixes, and the admin dashboard received accessibility fixes. The authors write about numerous accessibility improvements across the platform, including an important change that unlocks the dashboard submenus for people who use screen readers and navigate with the keyboard. The contrast of focus states, the positioning of elements and cursor behavior were improved as well.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What does an editorial team working in the block editor get out of it? Above all, smoother handling. It is easier to tell which element is active and to move around the menu without a mouse. And if this makes you wonder about changing the tool you build subpages with, you will find a comparison in our article <a href=\"https:\/\/www.web-systems.pl\/en\/elementor-vs-gutenberg-which-editor-to-choose\/\">Elementor or Gutenberg<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Updating_to_WordPress_65_what_to_check_before_you_click\"><\/span>Updating to WordPress 6.5: what to check before you click?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Three things: a backup, a test on a copy of the site, and confirmation that the theme and plugins are compatible. In practice this turns into a short list of steps.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Make a full backup of the files and the database, then make sure it can actually be restored.<\/li>\n<li>Run the update on a working copy of the site, the so-called staging environment.<\/li>\n<li>Check whether the authors of the theme and the add-ons declare compatibility with the new version.<\/li>\n<li>After the update, go through the most important subpages and forms, and in a store also the cart and checkout.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">What should you watch out for most? Plugins that have not been updated for a long time and heavily modified themes, because these are the ones that most often cause trouble after a version change. Teams that want to use the new editor features on their own are helped by WordPress and <a href=\"https:\/\/www.web-systems.pl\/en\/wordpress-woocommerce-training\/\">WooCommerce training<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The companies that gain the most are those with a block theme and their own editorial team: they will set up typography themselves, and installing add-ons will become more predictable. Other sites get accessibility fixes and a more solid foundation for future development work. Either way, we roll out every WordPress update only after a test on a copy, not on the live site.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Frequently_asked_questions\"><\/span>Frequently asked questions<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1790879476332-0\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><span class=\"ez-toc-section\" id=\"Is_updating_to_WordPress_65_safe_for_a_company_website\"><\/span>Is updating to WordPress 6.5 safe for a company website?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Yes, provided that you make a backup first and check the new version on a copy of the site. The risk lies mainly in outdated plugins and modified themes, not in the release itself. Did the test go through without errors? Then rolling it out on the production site is a formality.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1790879476332-1\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><span class=\"ez-toc-section\" id=\"Does_the_Font_Library_work_in_every_theme\"><\/span>Does the Font Library work in every theme?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>No. The feature is available in block themes, because it relies on the Site Editor. In classic themes, typefaces are still set by the theme itself or by the site developer. The release itself does not change how text looks in them.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1790879476332-2\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><span class=\"ez-toc-section\" id=\"Does_the_Interactivity_API_require_changes_to_an_existing_site\"><\/span>Does the Interactivity API require changes to an existing site?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>No, it is a tool for developers used when building new features. After the update, your current site works without any modifications. The API will only start to matter when you commission an expansion with interactive elements.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>WordPress 6.5 &#8220;Regina&#8221; was released on April 2, 2024. Editors get font management straight from the dashboard and a tidier way of installing plugins, while the people who build the site get two new APIs for working with blocks. We rely here on the official Regina release announcement. The order is this: first what the [&hellip;]<\/p>\n","protected":false},"author":9,"featured_media":30429,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[834,838],"tags":[2391,1142,2388,1194,2324,1192],"class_list":["post-30468","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news-trends","category-wordpress-en","tag-block-editor","tag-company-website","tag-fonts","tag-plugins","tag-updates-x","tag-wordpress-en"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/posts\/30468","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/comments?post=30468"}],"version-history":[{"count":3,"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/posts\/30468\/revisions"}],"predecessor-version":[{"id":30527,"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/posts\/30468\/revisions\/30527"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/media\/30429"}],"wp:attachment":[{"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/media?parent=30468"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/categories?post=30468"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.web-systems.pl\/en\/wp-json\/wp\/v2\/tags?post=30468"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}