&utm_campaign=virtual-wordpress-page-builder-summit-kicks-off-october-5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6348:\"<p class=\"has-drop-cap\">From October 5 through October 9, the first <a href=\"https://summit.camp/\">Page Builder Summit</a> will open its virtual doors to all attendees for free. Nathan Wrigley, the podcaster behind WP Builds, and Anchen le Roux, the founder and lead developer of Simply Digital Design, are hosting the five-day online event that focuses on the vast ecosystem of page builders for WordPress.</p>\n\n\n\n<p>The summit will include 35 sessions spread out over the <a href=\"https://summit.camp/schedule/\">event schedule</a>. Each session will last around 30 minutes, so it will be easy to pop in and watch one in your downtime. Sessions will cover a range of builders, including the default WordPress block editor, Elementor, Beaver Builder, Oxygen, Brizy, and Divi.</p>\n\n\n\n<p>&ldquo;It&rsquo;s an event specifically for users of WordPress page builders, or those curious about what they can do,&rdquo; said Wrigley. &ldquo;I feel like a page builder style interface for creating websites is the future for our industry. WordPress itself is moving in this direction with the block editor (a.k.a. Gutenberg). With that in mind, it seemed like a good idea to create a dedicated event to share knowledge about this side of WordPress. We&rsquo;ve tried to include presentations from as many page builders as we could.&rdquo;</p>\n\n\n\n<p>Wrigley made sure to point out that it is not all geared toward developers, discussing the inner-workings of builders. Some of the sessions focus on marketing, optimization, and conversion, which provides a wider range of topics for potential attendees.</p>\n\n\n\n<p>The summit hosts created an <a href=\"https://summit.camp/page-builder-quiz/\">online quiz</a> for those who are unsure about which sessions to watch.</p>\n\n\n\n<p>There is a small catch. The sessions will be freely available only from the time they begin and the following 24 hours. After that, accessing the videos will come at a premium. Attendees can gain lifetime access to the PowerPack for $47 if they purchase within 15 minutes of signing up. Then, prices will rise to $97 until the event kicks off on October 5. Beyond, the price jumps to $147. The lifetime access includes access to the presentations, transcripts, a workbook, and other bonuses from the speakers.</p>\n\n\n\n<p>For those unsure about forking over the cash, they can still watch the sessions during the 24-hour window.</p>\n\n\n\n<p>The proceeds from the event will go out to paying affiliate commissions to speakers and partners. Some of it will go into planning and investing in a second summit down the road.</p>\n\n\n\n<p>&ldquo;Both myself and Nathan have specific charities that we want to donate to after the event,&rdquo; said le Roux. &ldquo;It was part of our goals to be able to do this, but we didn&rsquo;t want to make this an <em>official contribution</em>.&rdquo;</p>\n\n\n\n<h2>Why a Page Builder Summit?</h2>\n\n\n\n<p class=\"has-drop-cap\">Both Wrigley and le Roux have their preferred builders. But, the goal of the summit is to offer a wide look at the tools available and help freelancers and agencies better streamline their businesses and create happier clients.</p>\n\n\n\n<p>&ldquo;I&rsquo;ve been a user of page builders for many years, but only at the point where they truly showed in the editing interface something that almost perfectly reflected what the end-user would see did I get really immersed,&rdquo; said Wrigley. &ldquo;Having come from a background in which I built entire websites from a collection of text files (HTML, CSS, PHP, etc.), I was fascinated that we&rsquo;d reached a point where the learning curve for building a good website was significantly reduced.&rdquo;</p>\n\n\n\n<p>He pointed out that it is not always so simple though. While the same level of coding skills may not be necessary, people must figure out how to navigate their preferred page builder, which can come with its own learning curve.</p>\n\n\n\n<p>&ldquo;You need to learn their way of doing things and how to achieve your design choices,&rdquo; he said. &ldquo;It&rsquo;s always going to work out better if you know the code, but the WordPress mission of democratizing publishing certainly seems to align quite nicely with the adoption of tools, like page builders, which mean that once-difficult tasks are now easier.&rdquo;</p>\n\n\n\n<p>For le Roux, her interest in hosting the Page Builder Summit falls back to her design studio.</p>\n\n\n\n<p>&ldquo;As a developer, my main reason for switching to page builders was around streamlining and creating more efficient but quality websites in the shortest amount of time,&rdquo; she said. &ldquo;Especially now that we focus on day rates, creating the best possible website that clients would love fast would not have been possible without page builders.&rdquo;</p>\n\n\n\n<h2>The Hosts&rsquo; Go-To Builders</h2>\n\n\n\n<p>&ldquo;We prefer using Beaver Builder with Themer at Simply Digital Design,&rdquo; said le Roux. &ldquo;We use Gutenberg for blog posts or where possible with custom post types or LMS software. However, we&rsquo;ve also taken on a few Elementor projects where that&rsquo;s the client&rsquo;s preferred option.&rdquo;</p>\n\n\n\n<p>Wrigley uses some of the same tools. His main work is on the WP Builds website where he hosts podcasts.</p>\n\n\n\n<p>&ldquo;I have used Beaver Builder&rsquo;s Themer to create templates for specific layouts, but for content creation within those layouts I&rsquo;m using the block editor,&rdquo; said Wrigley. &ldquo;My content is mainly text and the WordPress editor is utterly remarkable in this situation. I kept the classic editor installed for a few months after WordPress 5.0 came about, but I soon realized that this was folly and that the editing interface of Gutenberg is superior. The ability to insert and move text, buttons, etc. is such a joy to work with, and the iterations that have been made in the last two years make it, in my opinion, the best text editing experience on the web.&rdquo;</p>\n\n\n\n<p>Wrigley sees a future in which the WordPress block editor takes over much of the work that page builders are currently handling. However, that future is &ldquo;still over the horizon.&rdquo;</p>\n\n\n\n<p>&ldquo;I&rsquo;m excited about this future though, and we&rsquo;ve got a few crystal ball-gazing presentations; trying to work out what that future might look like,&rdquo; he said.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 01 Oct 2020 20:31:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:29;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"WPTavern: Jetpack 9.0 to Introduce New Feature for Publishing WordPress Posts to Twitter as Threads\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105448\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:243:\"https://wptavern.com/jetpack-9-0-to-introduce-new-feature-for-publishing-wordpress-posts-to-twitter-as-threads?utm_source=rss&utm_medium=rss&utm_campaign=jetpack-9-0-to-introduce-new-feature-for-publishing-wordpress-posts-to-twitter-as-threads\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3318:\"<p>Jetpack 9.0, coming on October 6, will debut a new feature that allows users to <a href=\"https://github.com/Automattic/jetpack/pull/16699\">share blog posts as Twitter threads</a> in multiples tweets. A recent version of Jetpack introduced the ability to import and <a href=\"https://wptavern.com/jetpack-8-7-adds-new-tweetstorm-unroll-feature-improves-search-customization\">unroll tweetstorms for publishing inside a post</a>. The 9.0 release will run it back the other way so the content originates in WordPress, yet still reaps all the same benefits of circulation on Twitter as a thread. </p>\n\n\n\n<p>The new Twitter threads feature is being added as part of Jetpack&rsquo;s Publicize module under the Twitter settings.  After linking up a Twitter account, the Jetpack sidebar options for Publicize allow users to publish to Twitter as a link to the blog or a set of threaded tweets. It&rsquo;s not just limited to text content &ndash; the threads feature will also upload and attach any images and videos included in the post. </p>\n\n\n\n<img />\n\n\n\n<p>When first introduced to the idea of publishing a Twitter thread from WordPress, I wondered if threads might lose their trademark pithy punch, since users aren&rsquo;t forced to keep each segment to the standard length of a tweet. Would each tweet be separated in an odd, unreadable way? The Jetpack team anticipated this, so the thread option adds more information to the block editor to show where the paragraphs will be split into multiple tweets.</p>\n\n\n\n<p>&ldquo;Threads are wildly underused on Twitter,&rdquo; Gary Pendergast said in a <a href=\"https://pento.net/2020/09/29/more-than-280-characters/\">post</a> introducing the feature. &ldquo;I think a big part of that is the UI for writing threads: while it&rsquo;s suited to writing a thread as a series of related tweet-sized chunks, it doesn&rsquo;t lend itself to writing, revising, and editing anything more complex.&rdquo; The tool Pendergast has been working on for Jetpack gives users the best of both worlds.</p>\n\n\n\n<p>In response to a comment requesting Automattic &ldquo;concentrate on tools to get people off social media,&rdquo; Pendergast said, &ldquo;If we&rsquo;re also able to improve the quality of conversations on social media, I think it&rsquo;d be remiss of us to not do so.&rdquo; He also credits IndieWeb discussions on&nbsp;<a href=\"https://indieweb.org/tweetstorm\">Tweetstorms</a>&nbsp;and&nbsp;<a href=\"https://indieweb.org/POSSE\">POSSE</a> (Publish (on your) Own Site,&nbsp;Syndicate&nbsp;Elsewhere) as inspirations for the feature.</p>\n\n\n\n<p>For years, blogging advocates have tried to convince those who post lengthy tweetstorms to switch to a publishing medium that is more suitable to the length of their thoughts. The problem is that Twitter users lose so much of the immediate feedback and momentum that their thoughts would have generated when composed as a tweetstorm.</p>\n\n\n\n<p>Instead of lecturing people about how they should really be blogging instead of tweetstorming, Jetpack is taking a fresh approach by enabling full content ownership with effortless social syndication. You can test out the experience for yourself by adding the <a href=\"https://jetpack.com/download-jetpack-beta/\">Jetpack Beta Testers</a> plugin and running the 9.0 RC version on your site.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 01 Oct 2020 02:56:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:30;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"WPTavern: Ask the Bartender: How To WordPress in a Block World?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105491\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:167:\"https://wptavern.com/ask-the-bartender-how-to-wordpress-in-a-block-world?utm_source=rss&utm_medium=rss&utm_campaign=ask-the-bartender-how-to-wordpress-in-a-block-world\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:9755:\"<blockquote class=\"wp-block-quote\"><p>I love your articles. And now, in the middle of the WordPress revolution, I realized I&rsquo;m constantly searching for an answer regarding WP these days.</p><p>So many things are being said, so many previsions of the future, problems, etc., but, right now, I think I, as a designer, just want to understand one thing that seemed answered already but it&rsquo;s never clear:</p><p>Is WordPress a good choice to build a client&rsquo;s template where he just has to insert the info that will show in the frontend where I want to? And he doesn&rsquo;t have to worry about formatting blocks? I love blocks, don&rsquo;t get me wrong, but will normal templating end?</p><p>I just think that having a super CMS, HTML, CSS, and being able to play with a database with ACF is so powerful, that I&rsquo;m wondering if it&rsquo;s lost. After so much reading, I still don&rsquo;t understand if this paradigm is going to disappear.</p><p>Right now, I don&rsquo;t know if it&rsquo;s best to stop making websites as I used to and adopt block patterns instead.</p><cite>Ricardo</cite></blockquote>\n\n\n\n<p class=\"has-drop-cap\">WordPress is definitely changing. Over the past two years, we have seen much of it reshaped into something different from the previous decade and more. However, this is not new. WordPress has always been a constantly-changing platform. It just feels far too different this time around, almost foreign to many. The platform had to make a leap. Otherwise, it would have started falling behind.</p>\n\n\n\n<p>And, it is a big <em>ask</em> of the existing community to come along with it, to take that leap together.</p>\n\n\n\n<p>It can be scary as a developer whose livelihood has depended on things working a certain way or who has built tools and systems around pre-block WordPress. Many freelancers and agencies had their world turned upside down with the launch of the block editor. It is perfectly OK to feel a bit lost.</p>\n\n\n\n<p>Now, it is time for a little tough love. It has been two years. As a professional, you need to have a plan in place already. Whether that is an educational plan for yourself or a transitional plan for your clients, you should already be tackling projects that leverage the block editor. If you are at a point where you have not been building with blocks, you are now behind. However, you can still catch up and continue advancing in your WordPress career.</p>\n\n\n\n<p>There are so many changes coming down the pipeline that anyone who plans to develop for WordPress will be in continual education mode for years to come.</p>\n\n\n\n<p>When building for clients, the biggest thing to remember is that it is not about you. It is about getting something into the hands of your clients that addresses their specific needs. Freelancers and agencies need to often be the Jacks and Jills of all trades. Sometimes, this even means having a backup CMS or two that you can use that are not named WordPress. It helps to be well-rounded enough to jump around when needed, especially if you are not at a point in your career where you can demand specific work and pass on jobs that would put food on the table.</p>\n\n\n\n<p>It is also easy to look at every job as a nail and WordPress as the hammer. Or, even specific plugins as the tool that will always get the job done. I have seen developers in the past rely on tools like ACF, CMB2, or Meta Box but could not code a custom metadata solution when necessary to save their life.  Sometimes a bigger toolbox is necessary.</p>\n\n\n\n<p>Every WordPress developer needs a solid, foundational understanding of the languages that WordPress uses. Gone are the days of skating by on HTML, CSS, and PHP knowledge. You need to learn JavaScript deeply. Matt Mullenweg, the co-founder of WordPress, was not joking around when he <a href=\"https://wptavern.com/state-of-the-word-2015-javascript-and-api-driven-interfaces-are-the-future-of-wordpress\">said this back in 2015</a>. It holds true more and more each day. In another five years, it will tough to be a developer in the WordPress world without knowing JavaScript, at least for backend work.</p>\n\n\n\n<p>It also depends on what types of sites you are building. If you are primarily handling front-end design, you will likely be able to get by with a lower skill level. You will just need to know the &ldquo;WordPress way&rdquo; of building themes.</p>\n\n\n\n<p>Within the next year, you should be able to build just about any theme design with decent CSS and HTML knowledge along with an understanding of how the block system works. Full-site editing and block-based themes will change how we build the front end of the web. It is going to be a challenging transition at first, especially for those of us who are steeped in traditional theme development, but client sites will often be far easier to build.  I highly recommend the twice-monthly <a href=\"https://make.wordpress.org/themes/\">block-based themes meetings</a> if your focus is on the front end.</p>\n\n\n\n<h2>Block Templates</h2>\n\n\n\n<p class=\"has-drop-cap\">Based on your question, I am going to make some assumptions. You have a history of essentially building out meta boxes via ACF where the client just pops in their data. Then, you format that data on the front end. You are likely mixing this with custom post types (CPTs). This is a fairly common scenario.</p>\n\n\n\n<p>One of the great things about the block system is that you can lock the post editor for individual CPTs. WordPress already has you covered with its <a href=\"https://developer.wordpress.org/block-editor/developers/block-api/block-templates/\">block templates feature</a>, which allows you to define just what a post should look like. You can set up which blocks you want to appear and have the client drop their content in. At the moment, this feature is limited to the post type level. However, it should grow more robust over time, particularly when it works alongside the traditional &ldquo;page templates&rdquo; system.</p>\n\n\n\n<p>Block templates are a powerful tool in the ol&rsquo; toolbox that will come in handy when building client sites.</p>\n\n\n\n<h2>Block Patterns</h2>\n\n\n\n<p class=\"has-drop-cap\">You do not have to stop making websites as you are accustomed to at the moment. However, you should start leveraging new block features as they become available and make sense for a specific project. I am a fanatic when it comes to <a href=\"https://wptavern.com/block-patterns-will-change-everything\">block patterns</a>, so my bias will definitely show.</p>\n\n\n\n<p>The biggest thing with block patterns and clients is education. For the uninitiated, you will need to spend some time teaching them how to insert a pattern and how it can be used to their advantage. That is the hurdle you must jump.</p>\n\n\n\n<p>For many of the users that I have seen introduced to well-designed patterns, they have fallen in love with the feature. Even many who were reluctant to switch to the block editor became far more comfortable working with it after learning how patterns worked. This is not the case for every user or client, but it has been a good introduction point to the block editor for many.</p>\n\n\n\n<p>To answer your question regarding patterns: yes, you should absolutely begin to adopt them.</p>\n\n\n\n<h2>ACF Is Evolving</h2>\n\n\n\n<p class=\"has-drop-cap\">Because you are accustomed to ACF, you should be aware that the framework is evolving to keep up with the block editor. <a href=\"https://wptavern.com/advanced-custom-fields-5-8-0-introduces-acf-blocks-a-php-framework-for-creating-gutenberg-blocks\">Version 5.8.0</a> introduced a PHP framework for creating custom blocks over a year ago. And, it has been improving ever since. There are even projects like <a href=\"https://wptavern.com/acf-blocks-provides-assortment-of-blocks-built-from-advanced-custom-fields-pro\">ACF Blocks</a>, which will provide even more tools for your arsenal.</p>\n\n\n\n<p>It is important to learn from what some of the larger agencies are doing. Read up on how <a href=\"https://webdevstudios.com/2020/09/08/gutenberg-first/\">WebDevStudios is tackling block development</a>. The company also has an open-source <a href=\"https://github.com/WebDevStudios/wds-acf-blocks\">block library</a> for ACF.</p>\n\n\n\n<h2>Solving Problems</h2>\n\n\n\n<p class=\"has-drop-cap\">Your job as a developer is to be a problem solver. Whatever system you are building with is merely a part of your toolset. You need to be able to solve issues regardless of what tool you are using. At the end of the day, it is just code. If you can learn HTML, you can learn CSS. If you can learn those, you can learn PHP. And, if you can manage PHP, you can certainly pick up JavaScript.</p>\n\n\n\n<p>A decade or two from now, you will need to learn something else to stay relevant in your career. Web technology changes. You must change with it. Always consider yourself a student and continue your education. Surround yourself and learn from those who are more advanced than you. Emulate, borrow, and steal good ideas. Use what you have learned to make them great.</p>\n\n\n\n<p>There is no answer I can give that will be perfect for every scenario. Each client is unique, and you will need to decide the best direction for each.</p>\n\n\n\n<p>However, yes, you should already be on the path to building with a block-first mindset if you plan to continue working with WordPress for the long haul. Immerse yourself in the system. Read, study, and build something any chance you get.</p>\n\n\n\n<p class=\"has-white-color has-blue-700-background-color has-text-color has-background text-white bg-blue-700\">This is the first post in the Ask the Bartender series.  Have a question of your own? <a href=\"https://wptavern.com/contact-me/ask-the-bartender\">Shoot it over</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 30 Sep 2020 20:35:25 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:31;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:91:\"WPTavern: Supercharge the Default WordPress Theme With Twentig, a Toolbox for Twenty Twenty\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105344\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:225:\"https://wptavern.com/supercharge-the-default-wordpress-theme-with-twentig-a-toolbox-for-twenty-twenty?utm_source=rss&utm_medium=rss&utm_campaign=supercharge-the-default-wordpress-theme-with-twentig-a-toolbox-for-twenty-twenty\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6455:\"<img />Custom page pattern from the Twentig plugin.\n\n\n\n<p class=\"has-drop-cap\">I am often on the hunt for those hidden gems when it comes to block-related plugins. I like to see the interesting places that plugin authors venture. That is why it came as a surprise when <a href=\"https://twitter.com/Gtarafdarr/status/1310240580140556290\">someone recommended</a> I check out the <a href=\"https://wordpress.org/plugins/twentig/\">Twentig plugin</a> a few days ago. Somehow, it has flown under my radar for months. And, it has managed to do this while being one of the more interesting plugins for WordPress I have seen in the past year.</p>\n\n\n\n<p>Twentig is a plugin that essentially gives superpowers to the default Twenty Twenty theme.  Diane and Yann Collet are the sibling co-founders and brains behind the plugin.</p>\n\n\n\n<p>While I have been generally a fan of Twenty Twenty since it was <a href=\"https://wptavern.com/twenty-twenty-bundled-in-core-beta-features-overview\">first bundled in core</a>, it was almost a bit of a letdown in some ways. It was supposed to be the theme that truly showcased what the block editor could do &mdash; and it does a fine job of styling the default blocks &mdash; but there was a lot of potential left on the table. The Twentig plugin turns Twenty Twenty into something worthier of a showcase for the block editor. It is that missing piece, that extra mile in which WordPress should be marching its default themes.</p>\n\n\n\n<p>While the new <a href=\"https://wptavern.com/first-look-at-twenty-twenty-one-wordpresss-upcoming-default-theme\">Twenty Twenty-One</a> default theme is just around the corner, Twentig is breathing new life into the past year&rsquo;s theme. The developers behind the plugin are still fixing bugs and bringing new features users.</p>\n\n\n\n<p>Of its 34 reviews on WordPress.org, Twentig has earned a solid five-star rating. That is a nice score for a plugin with only 4,000 active installations. As I said, it has flown under the radar a bit, but the users who have found it have obviously discovered something that adds those extra touches to their sites they need.</p>\n\n\n\n<h2>What Does Twentig Do?</h2>\n\n\n\n<p class=\"has-drop-cap\">It is a toolbox for Twenty Twenty. The headline feature is its block editor features, such as custom patterns and page layouts. It also offers a slew of customizer options that allow end-users to put their own design spin on the default theme. However, my interest is primarily in how it extends the block editor. </p>\n\n\n\n<p>Let&rsquo;s get this out of the way up front. Twentig&rsquo;s one downside is that it adds a significant amount of additional CSS on top of the already-heavy Twenty Twenty and block editor styles. I will blame the current lack of a full design system from WordPress on most of this. Styling for the block editor can easily bloat a stylesheet. Adding an extra 100+ kb per page load might be a blocker for some who would like to try the plugin. Users will need to weigh the trade-offs between the additional features and the added page size.</p>\n\n\n\n<p>The thing that makes Twentig special is its extensive patterns and pages library, which offers one-click access to hundreds of layouts specifically catered to the Twenty Twenty theme.</p>\n\n\n\n<img />Inserting one of the hero patterns.\n\n\n\n<p>It took me a few minutes to figure out how to access the patterns &mdash; mainly because I did not read the manual. I expected to find them mixed in with the core patterns inserter. However, the plugin adds a new sidebar panel to the editor, which users can access by clicking the &ldquo;tw&rdquo; icon. After seeing the list of options, I can understand why they probably would not fit into WordPress&rsquo;s limited block and patterns inserter UI.</p>\n\n\n\n<p>It would be easier to list what the plugin does not have than to go through each of the custom patterns and pages.</p>\n\n\n\n<p>The one thing that truly sets this plugin apart from the dozens of other block-library types of plugins is that there are no hiccups with the design. Almost every similar plugin or tool I have tested has had CSS conflicts with themes because they are trying to be a tool for every user. Twentig specifically targets the Twenty Twenty theme, which means it does not have to worry about whether it looks good with the other thousands of themes out there. It has one job, which is to extend its preferred theme, and it does it with well-designed block output.</p>\n\n\n\n<p>The other aspect of this is that it does not introduce new blocks. Every pattern and page layout option uses the core WordPress blocks, which includes everything from hero sections to testimonials to pricing tables to event listings.  And more.</p>\n\n\n\n<p>Twentig does not stop adding features to the block editor with custom patterns. The useful and sometimes fun bits are on the individual block level, and I have yet to explore everything. I continue to discover new settings each time I open my editor.</p>\n\n\n\n<p>Whether it is custom pullquote styles, a photo image frame, or an inner border tweak to the Cover block (shown below), the plugin adds little extras that push what users can do with their content.</p>\n\n\n\n<img />Inner border style for the Cover block.\n\n\n\n<p>Each block also gets some basic top and bottom margin options, which comes in handy when laying out a page. At this point, I am simply looking forward to discovering features I have yet to find.</p>\n\n\n\n<h2>Areas Themes Should Explore</h2>\n\n\n\n<p class=\"has-drop-cap\">One of the things I dislike about many of these features being within the Twentig plugin is that I would like to see them within the Twenty Twenty theme instead. Obviously not every feature belongs in the theme &mdash; some features firmly land in plugin territory. The default WordPress themes should also leave some room for plugin authors to explore. But, shipping some of the more prominent patterns and styles with Twenty Twenty would make a more robust experience for the average end-user looking to get the most out of blocks.</p>\n\n\n\n<p>Block patterns were not a core WordPress feature when Twenty Twenty landed. However, for the upcoming Twenty Twenty-One theme, which is expected to bundle some unique patterns, the design team should explore what the Twentig plugin has brought to the current default. That is the direction that theme development should be heading, and theme developers can learn a lot by <s>stealing</s> borrowing from this plugin.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 29 Sep 2020 22:00:42 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:32;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:105:\"WPTavern: Coming in Jetpack 9.0: Shortcode Embeds Module Updated to Handle Facebook and Instagram oEmbeds\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105381\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:253:\"https://wptavern.com/coming-in-jetpack-9-0-shortcode-embeds-module-updated-to-handle-facebook-and-instagram-oembeds?utm_source=rss&utm_medium=rss&utm_campaign=coming-in-jetpack-9-0-shortcode-embeds-module-updated-to-handle-facebook-and-instagram-oembeds\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2938:\"<p>Facebook and Instagram are&nbsp;<a href=\"https://wptavern.com/upcoming-api-change-will-break-facebook-and-instagram-oembed-links-across-the-web-beginning-october-24\">dropping unauthenticated oEmbed support</a>&nbsp;on October&nbsp;24. WordPress will be removing both Facebook and Instagram as oEmbed providers in an upcoming release. After evaluating third-party solutions, WordPress VIP is <a href=\"https://lobby.vip.wordpress.com/2020/09/28/updates-and-recommendations-facebook-and-instagram-changing-oembed-to-require-authentication/\">recommending</a> its partners enable Jetpack&rsquo;s <a href=\"https://jetpack.com/support/shortcode-embeds/\">Shortcode Embeds</a> module. Jetpack will be shipping the update in its <a href=\"https://github.com/Automattic/jetpack/milestone/166\">9.0 release</a>, which is anticipated to land prior to the October 24th deadline.</p>\n\n\n\n<p>The module is being <a href=\"https://github.com/Automattic/jetpack/pull/16814\">updated</a> to provide a seamless transition for users who might otherwise be negatively impacted by Facebook&rsquo;s upcoming API change. WordPress contributors have run some simulations but are not yet sure what will happen to the display for previously embedded content.</p>\n\n\n\n<p>&ldquo;It is possible that they change the contents of the JS file to manipulate cached embeds, perhaps to display a warning that the site is using an old method to embed content or that the request is not properly authenticated,&rdquo; Jonathan Desrosiers commented on the trac <a href=\"https://core.trac.wordpress.org/ticket/50861#comment:35\">ticket</a> for removing the oEmbed providers.</p>\n\n\n\n<p>WordPress.com VIP roughly outlined what users can expect if they do not enable a solution to begin authenticating oEmbeds:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>By default, WordPress caches oEmbed contents in post metadata. These embeds will continue to display in previously-published content.&nbsp;If you edit older posts in the Block Editor, regardless of whether you update the post by saving changes, the embeds in the post will no longer be cached and will stop displaying.&nbsp;If you view these older posts using the Classic Editor, so long as the post is not re-saved, the embeds will continue to function and display properly. If you update the post content, the embed will cease functioning unless you have a mitigation installed.</p></blockquote>\n\n\n\n<p>Although WordPress VIP recommends using the Jetpack module as the best solution, self-hosted WordPress users may want to investigate other options if they are not already using Jetpack. <a href=\"https://wordpress.org/plugins/oembed-plus/\">oEmbed Plus</a> is a free plugin created specifically for solving the problem of WordPress dropping Facebook and Instagram as oEmbed providers but it is more work to set up and configure. It requires users to register as a Facebook developer and create an app to get API credentials.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 29 Sep 2020 21:18:52 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:33;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:52:\"WPTavern: W3C Selects Craft CMS for Redesign Project\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105265\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:149:\"https://wptavern.com/w3c-selects-craft-cms-for-redesign-project?utm_source=rss&utm_medium=rss&utm_campaign=w3c-selects-craft-cms-for-redesign-project\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:9407:\"<p>W3C has <a href=\"https://w3c.studio24.net/docs/cms-selection-report/\">selected Craft CMS</a> over Statamic for its redesign project, after <a href=\"https://wptavern.com/w3c-drops-wordpress-from-consideration-for-redesign-narrows-cms-shortlist-to-statamic-and-craft\">dropping WordPress from consideration</a> in an earlier round of elimination: </p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>In the end, our decision mostly came down to available resources. Craft had already committed to reach AA compliance in Craft 4 (it is currently on version 3.5, the release of version 4 is planned for April 2021). They had also arranged for an external agency to provide them with accessibility issues to tackle weekly. In the end, they decided instead to hire an in-house accessibility specialist to perform assessments and assist the development team in adopting accessibility patterns in the long run.</p><cite><a href=\"https://w3c.studio24.net/docs/cms-selection-report/\">W3C CMS Selection Report</a></cite></blockquote>\n\n\n\n<p>Last week we published a <a href=\"https://wptavern.com/w3c-drops-wordpress-from-consideration-for-redesign-narrows-cms-shortlist-to-statamic-and-craft\">post</a> urging W3C to revisit Gutenberg for a fair shake against the proprietary CMS&rsquo;s or consider adopting another open source option. During the selection process, Studio 24, the agency contracted for the redesign, cited its extensive experience with WordPress as the reason for not performing any accessibility testing on more recent versions of Gutenberg. </p>\n\n\n\n<p>When asked if the  team contacted anyone from WordPress&rsquo; Accessibility Team during the process or put Gutenberg through the same tests as the proprietary CMS&rsquo;s, Studio 24 founder Simon Jones <a href=\"https://twitter.com/simonrjones/status/1309817109636157440\">confirmed</a> they had not. </p>\n\n\n\n<p>&ldquo;No, we only reached out to the two shortlisted CMS&rsquo;s&rdquo; Jones said. &ldquo;I&rsquo;m afraid we didn&rsquo;t have time to do more. We did test GB a few months ago based on editing content &ndash; though it wasn&rsquo;t the only factor in our choice. As an agency we do plan to keep reviewing GB in the future.&rdquo; </p>\n\n\n\n<p>In response to our concerns regarding licensing, Jones penned an update titled &ldquo;<a href=\"https://w3c.studio24.net/updates/on-not-choosing-wordpress/\">On not choosing WordPress,</a>&rdquo; which further elaborated on the reasons why the agency was not inclined towards using or evaluating the new editor:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>From a business perspective I also believe Gutenberg creates a complexity issue that makes it challenging for use by many agencies who create custom websites for clients; where we have a need to create lots of bespoke blocks and page elements for individual client projects.</p><p>The use of React complicates front-end build. We have very talented front-end developers, however, they are not React experts &ndash; nor should they need to be. I believe front-end should be built as standards-compliant HTML/CSS with JavaScript used to enrich functionality where necessary and appropriate.</p><p>As of yet, we have not found a satisfactory (and profitable) way to build custom Gutenberg blocks for commercial projects.&nbsp;</p></blockquote>\n\n\n\n<p>The CMS selection report also stated that W3C needs the CMS to be &ldquo;usable by non-sighted users&rdquo; by the launch date, since some members of the staff who contribute to the website are non-sighted. </p>\n\n\n\n<p>Since the most recent version of WordPress was not tested in comparison with the proprietary CMS&rsquo;s, it&rsquo;s unclear how much better they handle accessibility. Ultimately, W3C and Studio 24 were more comfortable moving forward with a proprietary vendor that was able to make certain assurances about the future accessibility of its authoring tool, despite having a smaller pool of contributors.</p>\n\n\n\n<p>&ldquo;[I&rsquo;m] also deeply curious since the cursory notes on accessibility for both of the reviewed CMSes seem to highlight a ton of issues like &lsquo;Buttons and Checkboxes are built using div elements&rsquo; or most inputs lacking clear focus styles,&rdquo; Gutenberg technical lead Mat&iacute;as Ventura said. &ldquo;An element like the&nbsp;<em>Calendar</em>&nbsp;for choosing a post date seems entirely inoperable with keyboard on Craft, for example, while WordPress&rsquo; has had significant effort and rounds of feedback poured into that element alone to make it fully operable.&rdquo;</p>\n\n\n\n<p>WordPress developer Anthony Burchell commented on how using a relatively new proprietary CMS seemed counter to W3C&rsquo;s stated goal to select an option on the basis of longevity. Craft CMS&rsquo;s continued success is contingent upon its business model and the company&rsquo;s ability to remain profitable. </p>\n\n\n\n<p>&ldquo;FOSS have the same opportunity of direct access to developers,&rdquo; Burchell <a href=\"https://twitter.com/antpb/status/1309883204728430593?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1309883204728430593%7Ctwgr%5Eshare_3&ref_url=https%3A%2F%2Fwptavern.com%2Fwp-admin%2Fpost.php%3Fpost%3D105265action%3Dedit\">said</a>. &ldquo;I recognize there are many accessibility shortcomings in popular software, but I think it&rsquo;s more constructive to rally behind and contribute, not use a proprietary CMS that boasts beer budget in their guidelines.&rdquo; </p>\n\n\n\n<p>On the other side of the issue, accessibility advocates took the W3C&rsquo;s decision as a referendum on Gutenberg&rsquo;s continued struggles to meet WCAG AA standards. WordPress accessibility specialist Amanda Rush <a href=\"https://www.customerservant.com/w3c-is-prioritizing-accessibility-over-its-open-source-licensing-preferences-why-is-that-a-bad-thing-again/\">said</a> it was &ldquo;nice to see the W3C flip tables over this.&rdquo;</p>\n\n\n\n<p>&ldquo;Gutenberg is not mature software,&rdquo; accessibility consultant and WordPress contributor Joe Dolson said in a <a href=\"https://www.joedolson.com/2020/09/the-w3c-drops-wordpress-from-consideration/\">post</a> elaborating on his comments at WPCampus 2020 Online. He emphasized the lack of stability in the project that Studio 24 alluded to when documenting the reasons against using WordPress.</p>\n\n\n\n<p>&ldquo;It is still undergoing rapid changes, and has grand goals to add a full-site editing experience for WordPress that almost guarantees that it will continue to undergo rapid changes for the next few years,&rdquo; Dolson said. &ldquo;Why would any organization that is investing a large amount into a site that they presumably hope will last another 10 years want to invest in something this uncertain?&rdquo;</p>\n\n\n\n<p>Dolson also said the accessibility improvements he referenced regarding the audit were only a small part of the whole picture.  </p>\n\n\n\n<p>&ldquo;They only encompass issues that existed in the spring of 2019,&rdquo; he said. &ldquo;Since then, many features have been added and changed, and those features both resolve issues and have created new ones. The accessibility team is constantly playing catch up to try and provide enough support to improve Gutenberg. And even now, while it is more or less accessible, there are critical features that are not yet implemented. There are entirely new interface patterns introduced on a regular basis that break prior accessibility expectations.&rdquo;</p>\n\n\n\n<p>WordPress is also being used by millions of people who are constantly reporting issues to fuel the software&rsquo;s continued refinement, which increases the <a href=\"https://github.com/WordPress/gutenberg/labels/Accessibility%20%28a11y%29\">backlog of issues</a>. Unfortunately, Studio 24 did not properly evaluate Gutenberg against the proprietary CMS&rsquo;s in order to determine if these software projects are in any better shape. </p>\n\n\n\n<p>Instead, they decided that Craft CMS&rsquo;s community was more receptive to collaborating on issues without reaching out to WordPress. Given the W3C&rsquo;s stated preference for open source software, WordPress, as the only CMS under consideration with an <a href=\"https://opensource.org/licenses\">OSD-compliant license</a>, should have received the same accessibility evaluation.</p>\n\n\n\n<p>&ldquo;I can&rsquo;t make any statements that would be meaningful about the other content management systems under consideration; but if WordPress wants to be taken seriously in environments where accessibility is a legal, ethical, and mission imperative, there&rsquo;s still a lot of work to be done,&rdquo; Dolson said.</p>\n\n\n\n<p>Studio 24&rsquo;s evaluation may not have been equitable to the only open source CMS under consideration, but the situation serves to highlight a unique quandary: when using open source software becomes the impractical choice for organizations requiring a high level of accessibility in their authoring tools.</p>\n\n\n\n<p>&ldquo;Studio 24 ultimately determined that working with a CMS to make it better was more possible with a smaller, proprietary vendor than with a large open-source project,&rdquo; accessibility advocate Brian DeConinck said. &ldquo;Project leadership would be more receptive, and the smaller community means changes can be made more quickly. That should prompt a lot of soul-searching for&hellip;well, everyone. What does that say about the future of open source?&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 29 Sep 2020 04:56:21 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:34;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"Gary: More than 280 characters\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"https://pento.net/?p=5405\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"https://pento.net/2020/09/29/more-than-280-characters/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5187:\"<p>It&#8217;s hard to be nuanced in 280 characters.</p>\n\n\n\n<p>The Twitter character limit is a major factor of what can make it so much fun to use: you can read, publish, and interact, in extremely short, digestible chunks. But, it doesn&#8217;t fit every topic, ever time. Sometimes you want to talk about complex topics, having honest, thoughtful discussions. In an environment that encourages hot takes, however, it&#8217;s often easier to just avoid having those discussions. I can&#8217;t blame people for doing that, either: I find myself taking extended breaks from Twitter, as it can easily become overwhelming.</p>\n\n\n\n<p>For me, the exception is Twitter threads.</p>\n\n\n\n<h2>Twitter threads encourage nuance and creativity.</h2>\n\n\n\n<p>Creative masterpieces like this Choose Your Own Adventure are not just possible, they rely on Twitter threads being the way they are.</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">Being Beyoncé’s assistant for the day: DONT GET FIRED THREAD <a href=\"https://t.co/26ix05Hkhp\">pic.twitter.com/26ix05Hkhp</a></p>&mdash; green chyna (@CORNYASSBITCH) <a href=\"https://twitter.com/CORNYASSBITCH/status/1142591156884127744?ref_src=twsrc%5Etfw\">June 23, 2019</a></blockquote>\n</div>\n\n\n\n<p>Publishing a short essay about your experiences in your job can bring attention to inequality.</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">DOWNTOWN BROOKLYN: I\'m working arraignments tonight, representing poor New Yorkers who were arrested yesterday on Thanksgiving. <br /><br />It was the coldest Thanksgiving in more than a century. Tonight\'s also bitterly cold, even in the courtroom. I\'m wearing my scarf &amp; coat.</p>&mdash; Rebecca Kavanagh (@DrRJKavanagh) <a href=\"https://twitter.com/DrRJKavanagh/status/1066144860619636736?ref_src=twsrc%5Etfw\">November 24, 2018</a></blockquote>\n</div>\n\n\n\n<p>And Tumblr screenshot threads are always fun to read, even when they take a turn for the epic (over 4000 tweets in this thread, and it isn&#8217;t slowing down!)</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">Tumblr textposts thread, probably?</p>&mdash; we are a family forged in bureaucracy (@ex_aItiora) <a href=\"https://twitter.com/ex_aItiora/status/1165987806621184002?ref_src=twsrc%5Etfw\">August 26, 2019</a></blockquote>\n</div>\n\n\n\n<p>Everyone can think of threads that they&#8217;ve loved reading.</p>\n\n\n\n<p>My point is, threads are wildly underused on Twitter. I think I big part of that is the UI for writing threads: while it&#8217;s suited to writing a thread as a series of related tweet-sized chunks, it doesn&#8217;t lend itself to writing, revising, and editing anything more complex.</p>\n\n\n\n<p>To help make this easier, I&#8217;ve been working on a tool that will help you publish an entire post to Twitter from your WordPress site, as a thread. It takes care of transforming your post into Twitter-friendly content, you can just&#8230; write. <img src=\"https://s.w.org/images/core/emoji/13.0.0/72x72/1f642.png\" alt=\"🙂\" class=\"wp-smiley\" /></p>\n\n\n\n<p>It doesn&#8217;t just handle the tweet embeds from earlier in the thread: it handles handle uploading and attaching any images and videos you&#8217;ve included in your post.</p>\n\n\n\n<ul class=\"blocks-gallery-grid\"><li class=\"blocks-gallery-item\"><img width=\"3264\" height=\"2448\" src=\"https://pento.net/wp-content/uploads/2018/12/mvimg_20181231_0910291833340677198697139.jpg\" alt=\"A selfie of me feeding a giraffe.\" class=\"wp-image-3608\" /></li><li class=\"blocks-gallery-item\"><img width=\"4000\" height=\"3000\" src=\"https://pento.net/wp-content/uploads/2018/12/GOPR0365.jpg\" alt=\"A selfie of me on an iceberg south of the Antarctic circle.\" class=\"wp-image-3591\" /></li><li class=\"blocks-gallery-item\"><img width=\"3264\" height=\"2448\" src=\"https://pento.net/wp-content/uploads/2018/12/00006IMG_00006_BURST20181002212033_COVER.jpg\" alt=\"A selfie of me with a fire breathing dragon at the Harry Potter themed amusement park in Orlando, Florida.\" class=\"wp-image-3604\" /></li><li class=\"blocks-gallery-item\"><img width=\"1793\" height=\"469\" src=\"https://pento.net/wp-content/uploads/2018/12/48944769_986954175890_2085904447019417600_o.jpg\" alt=\"A panoramic view of sunset over Nairobi National Park.\" class=\"wp-image-3554\" /></li></ul>\n\n\n\n<p>All sorts of embeds work, too. <img src=\"https://s.w.org/images/core/emoji/13.0.0/72x72/1f609.png\" alt=\"😉\" class=\"wp-smiley\" /></p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<div class=\"jetpack-video-wrapper\"></div>\n</div>\n\n\n\n<p>It&#8217;ll be coming in Jetpack 9.0 (due out October 6), but you can try it now in <a href=\"https://jetpack.com/download-jetpack-beta/\">the latest Jetpack Beta</a>! Check it out and tell me what you think. <img src=\"https://s.w.org/images/core/emoji/13.0.0/72x72/1f642.png\" alt=\"🙂\" class=\"wp-smiley\" /></p>\n\n\n\n<p>This might not fix all of Twitter&#8217;s problems, but I hope it&#8217;ll help you enjoy reading and writing on Twitter a little more. <img src=\"https://s.w.org/images/core/emoji/13.0.0/72x72/1f496.png\" alt=\"💖\" class=\"wp-smiley\" /></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 29 Sep 2020 02:33:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Gary\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:35;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:100:\"WPTavern: Themes Team Releases a Web Fonts Loader, Likely To Prohibit Hotlinking Any Off-Site Assets\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105363\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:243:\"https://wptavern.com/themes-team-releases-a-web-fonts-loader-likely-to-prohibit-hotlinking-any-off-site-assets?utm_source=rss&utm_medium=rss&utm_campaign=themes-team-releases-a-web-fonts-loader-likely-to-prohibit-hotlinking-any-off-site-assets\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5815:\"<p class=\"has-drop-cap\">Last Friday, the WordPress Themes Team <a href=\"https://make.wordpress.org/themes/2020/09/25/new-package-to-allow-locally-hosting-webfonts/\">announced the release</a> of its new <a href=\"https://github.com/WPTT/webfont-loader\">Webfonts Loader project</a>. It is a drop-in script that allows theme authors to load web fonts from the user&rsquo;s site instead of a third-party CDN. The secondary message included in the team&rsquo;s announcement is that it no longer plans to allow themes to hotlink Google Fonts in the future.</p>\n\n\n\n<p>Throughout most of the team&rsquo;s history, it has not allowed themes to hotlink or use CDNs for hosting theme assets, such as CSS, JavaScript, and fonts. The one <a href=\"https://make.wordpress.org/themes/handbook/review/required/#stylesheets-and-scripts\">exception to this rule</a> was the use of Google Fonts. This allowed themes to have richer typography options at their disposal from what the team has generally declared a reliable source.</p>\n\n\n\n<p>&ldquo;The exception was made because there was no practical way to not have the exception at the time,&rdquo; said Aria Stathopoulos, a Themes Team representative and developer behind the Webfonts Loader project. &ldquo;The exception for Google Fonts was made out of necessity. Now that there is another way, the exception will not be necessary.&rdquo;</p>\n\n\n\n<p>In effect, disallowing the Google Fonts CDN would not be a new ban. It would be a removal of an exception to the existing ban.</p>\n\n\n\n<p>Google Fonts has become so embedded into the theme developer toolset over the years, there was no way the team could simply pull the plug and prohibit the use of the CDN overnight. If the Themes Team members wanted to focus more on privacy, they would need to build a tool that made it dead simple for theme authors to use.</p>\n\n\n\n<p>There is no hard deadline for when the team will remove the exception for Google Fonts, and it is not set in stone at this point. Stathopoulos said removing it has been the goal from the beginning, disallowing all CDNs. However, it took a while to find an efficient way to handle this. With a viable alternative in place, they can discuss moving forward.</p>\n\n\n\n<h2>Webfonts Loader for Themes</h2>\n\n\n\n<p class=\"has-drop-cap\">The Webfonts Loader project keeps it simple for theme authors. It introduces a new <code>wptt_get_webfont_styles()</code> function that developers can plug in a stylesheet URL. Once a page is loaded with that function call, it will download the fonts locally to a <code>/fonts</code> folder in the user&rsquo;s <code>/wp-content</code> directory. This way, fonts will always be served from the user&rsquo;s site.</p>\n\n\n\n<p>The system is not limited to Google Fonts either. Any URL that serves CSS with an <code>@font-face {}</code> rule will work. It does not currently include authentication for CDNs that require API keys, such as Adobe Fonts. However, that is something the team might add in the future.</p>\n\n\n\n<p>&ldquo;For end-users, moving away from CDNs and locally hosting web fonts will improve performance (fewer handshake roundtrips for SSL), and is the privacy-conscious choice,&rdquo; said Stathopoulos. &ldquo;The only &lsquo;valid privacy concern&rsquo; is that the web fonts&rsquo; CDN does not disclose information that is fundamental to the GDPR: what information gets logged, for how long these logs remain, how they are processed, if there is any cross-referencing with all the other wealth of information the company has from users, etc. The concern is a lack of disclosure and information. If a site owner doesn&rsquo;t know what kind of information a third-party logs for its visitors, then they should ethically not enforce that on their visitors. With this package, the CDN is removed from the equation and the font still gets served fast &mdash; if not faster.&rdquo;</p>\n\n\n\n<h2>A Path to Core WordPress</h2>\n\n\n\n<p class=\"has-drop-cap\">Today, there is now a broader focus on privacy concerns related to third-party resources, particularly with tech giants like Google. Such concerns extend to whether third parties are tracking users or collecting data. Additional concerns are around whether sites are disclosing the use of third-party resources, which may be required in some jurisdictions. Site owners who are often unable to work through the web of potential issues are stuck in the middle.</p>\n\n\n\n<p>Jono Alderson opened a ticket to <a href=\"https://core.trac.wordpress.org/ticket/46370\">create an API</a> for loading web fonts locally in core WordPress in February 2019. It is a lengthy and detailed proposal, but it has yet to see much buy-in outside of a handful of developers.</p>\n\n\n\n<p>&ldquo;If such a script is standardized and included in WordPress core, one of the main benefits would be more respect for the end-user&rsquo;s privacy,&rdquo; said Stathopoulos. &ldquo;In the end, that&rsquo;s all privacy is about: respecting users.&rdquo;</p>\n\n\n\n<p>A standard API like Alderson proposes could solve some issues. Namely, it would virtually eliminate any privacy concerns. However, loading fonts locally could allow WordPress to optimize font loading and would create a shared system where plugins and themes do not load duplicate assets because of the current limitations of the enqueuing system. A standard API would also put the responsibility of efficiently loading fonts on WordPress&rsquo;s shoulders instead of theme and plugin developers.</p>\n\n\n\n<p>The Themes Team&rsquo;s new project is a solid start and strengthens the current proposal.</p>\n\n\n\n<p>&ldquo;If we&rsquo;re serious about WordPress becoming a fast, privacy-friendly platform, we can&rsquo;t rely on theme developers to add and manage fonts without providing a framework to support them,&rdquo; wrote Alderson in the ticket.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 28 Sep 2020 20:58:48 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:36;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"WPTavern: Fuxia Scholz First to Pass 100K Reputation Points on WordPress Stack Exchange\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105282\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:219:\"https://wptavern.com/fuxia-scholz-first-to-pass-100k-reputation-points-on-wordpress-stack-exchange?utm_source=rss&utm_medium=rss&utm_campaign=fuxia-scholz-first-to-pass-100k-reputation-points-on-wordpress-stack-exchange\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5096:\"<p><a href=\"https://stackexchange.com/users/113787/fuxia\">Fuxia Scholz</a>, a prolific <a href=\"https://wordpress.stackexchange.com/\">WordPress Stack Exchange</a> (WPSE) contributor, is the first member to reach 100,000 reputation points. The popular Q&amp;A community site rewards expert advice by floating the highest quality answers to the top, allowing users to earn reputation points. The gamified help community has proven to be more motivating for developers than many traditional forums, since the upvotes communicate how useful their answers are to others.</p>\n\n\n\n<div class=\"wp-block-image\"><img /></div>\n\n\n\n<p>Scholz started on Stack Overflow a few months before WordPress had its own site. She wrote around 50 answers and made connections with other WordPress developers ahead of the site&rsquo;s <a href=\"https://area51.stackexchange.com/proposals/1500/wordpress-development\">beta phase in June 2010</a>. Once the site graduated and got its own logo and design, Scholz started writing more.</p>\n\n\n\n<p>&ldquo;One core idea for all Stack Exchange sites is gamification: You earn reputation, and you get access to <a href=\"https://wordpress.stackexchange.com/help/privileges\">certain privileges</a>,&rdquo; Scholz said.</p>\n\n\n\n<p>&ldquo;You can say I got a bit addicted. My favorite questions were about problems for which I didn&rsquo;t know the answer, and couldn&rsquo;t find one with a search engine, because no one else had solved that before. I used my answers to teach myself, and I learned a lot this way! In May 2011 <a href=\"https://stackexchange.com/users/113787/fuxia?tab=reputation\">my reputation on WPSE was already higher than on Stack Overflow</a>, and for the next years it went up in a steep curve.&rdquo; Ten years after WPSE launched, Scholz has become the first to reach 100,000 reputation points.</p>\n\n\n\n<p>&ldquo;What reputation and karma do is send a message that this is a community with norms, it&rsquo;s not just a place to type words onto the internet. (That would be 4chan.)&rdquo; Stack Overflow co-creator Joel Spolsky <a href=\"https://www.joelonsoftware.com/2018/04/13/gamification/\">said</a>. &ldquo;We don&rsquo;t really exist for the purpose of letting you exercise your freedom of speech. You can get your freedom of speech somewhere else. Our goal is to get the best answers to questions. All the voting makes it clear that we have standards, that some posts are better than others, and that the community itself has some norms about what&rsquo;s good and bad that they express through the vote.&rdquo;</p>\n\n\n\n<p>The reputation points were originally inspired by Reddit Karma. Spolsky admits that the points not a perfect system but they do tend to &ldquo;drive a tremendous amount of good behavior.&rdquo; Gamification can shape and encourage certain behaviors but Spolsky said it&rsquo;s a weak force that cannot motivate people to do things they are not already interested in doing. For Scholz, it was the community aspect and an earned sense of ownership and responsibility that kept her hooked.</p>\n\n\n\n<p>&ldquo;In 2012, the community elected me as a moderator, and that changed a lot,&rdquo; she said. &ldquo;Now it wasn&rsquo;t just a game anymore, it was a duty. I felt responsible for the site. I still do. I also found some friends on there. We met at WordCamps and in private, and worked together on different projects.&rdquo;</p>\n\n\n\n<p>Scholz no longer works in development and said she doesn&rsquo;t care about WordPress anymore, but she is still a regular contributor on the WPSE.</p>\n\n\n\n<p>&ldquo;I switched careers and work as a writer, translator, and community manager for <a rel=\"noreferrer noopener\" href=\"https://t.co/mIhjlVjPv4?amp=1\" target=\"_blank\">Chess24.com</a> now,&rdquo; she said. &ldquo;But I still care about the site WordPress Stack Exchange! I keep an eye on new tags, handle flagged posts and comments, try to make every new user feel welcome, and I search for people who are abusing the system &mdash; vote fraud and spam. And, very rarely, I even write an answer, because I still know all this stuff. </p>\n\n\n\n<p>&ldquo;Checking the site has become a part of my daily routine, like feeding the cat.&rdquo; </p>\n\n\n\n<p>This daily habit has snowballed into Scholz racking up more than 2,000 answers. She is getting upvotes on many of her old answers nearly every day, which is what pushed her over the 100k milestone.</p>\n\n\n\n<p>&ldquo;There is a lot to say about the way our site developed over the years,&rdquo; Scholz said. &ldquo;I&rsquo;m not happy about some things. The enthusiasm of the early days is gone. We don&rsquo;t have enough regulars, there is no discussion about the site on <a href=\"https://t.co/tlRekl6sOt?amp=1\">WordPress Development Meta Stack Exchange</a>, and our chat, once very active, funny, and friendly, is now almost dead. </p>\n\n\n\n<p>&ldquo;Maybe that&rsquo;s normal, I don&rsquo;t know. But it&rsquo;s still &lsquo;my&rsquo; site. Reputation and badges don&rsquo;t really mean anything for a long time now, but keeping the site working, useful and friendly is more important.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 26 Sep 2020 15:27:03 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:37;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"WPTavern: PhotoPress Plugin Seeks to Revolutionize Photography for WordPress Users\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104770\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:209:\"https://wptavern.com/photopress-plugin-seeks-to-revolutionize-photography-for-wordpress-users?utm_source=rss&utm_medium=rss&utm_campaign=photopress-plugin-seeks-to-revolutionize-photography-for-wordpress-users\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5638:\"<p class=\"has-drop-cap\">Peter Adams, the owner of the <a href=\"https://wordpress.org/plugins/photopress/\">PhotoPress plugin</a>, announced a couple of weeks ago that <a href=\"https://www.photopressdev.com/its-time-for-photopress/\">now is the time for his project</a> to take center stage. &ldquo;It&rsquo;s Time for PhotoPress,&rdquo; read the title of his post in which he laid out a four-phase plan for the future of his project.</p>\n\n\n\n<p>Adams is no stranger to manipulating WordPress to suit the needs of photographers. He described photography as his first love and second career. He initially found the art of taking photos in high school and set off to college to become a professional photographer in the early &rsquo;90s.</p>\n\n\n\n<p>As his university graduation loomed, he was recruited to run web development for an internet ad agency that built websites for Netscape, Bill Clinton&rsquo;s White House, and dozens of Fortune 500 companies. He spent the next 15 years starting or running tech companies before returning to his roots as a photographer.</p>\n\n\n\n<p>Today, he photographs for various magazines and companies. And, that&rsquo;s where his PhotoPress project comes in.</p>\n\n\n\n<p>&ldquo;As far as WordPress has come, it is at risk of losing an entire generation of photographers to photo website services such as Photoshelter, SmugMug, Squarespace, and PhotoFolio,&rdquo; he said. Adams wants to change that, making WordPress the go-to platform for photographers around the world.</p>\n\n\n\n<h2>The Jetpack of Photography Plugins</h2>\n\n\n\n<p class=\"has-drop-cap\">If you dig into the history of the PhotoPress plugin on WordPress.org, it seems to have a 15-year history. However, this is not the same plugin that was published a decade and a half ago by a different developer. The original plugin is now defunct, and Adams took over when the name was freed up on the directory.</p>\n\n\n\n<p>Adams wrote in his announcement post that WordPress has done a great job of delivering several media features over the years. &ldquo;Yet despite that, there are still many rough edges and missing features that keep WordPress from being the first choice for a photographer that needs to publish a beautiful portfolio of their work, put their image catalog/archive online, or showcase a photo editorial/project.&rdquo;</p>\n\n\n\n<p>He outlined a list of 10 specific problem areas that he wants to address in a &ldquo;Jetpack-like&rdquo; plugin for photographers. This is the bread and butter of the first of the planned four phases, which he said is about 80% finished. He had originally planned to develop PhotoPress as a series of separate plugins, each addressing a specific problem. Now, it is a single plugin with modules than can be enabled or disabled.</p>\n\n\n\n<p>When asked why the &ldquo;right time&rdquo; is now, Adams explained it is because the Gutenberg (block editor) project is a giant leap forward in usability in terms of creating photography blogs.</p>\n\n\n\n<img />PhotoPress Gallery block in the editor.\n\n\n\n<p>&ldquo;Photogs are a rare breed of non-technical users with high design sense,&rdquo; he said. &ldquo;Things that I used to have to teach photographers to do using shortcode syntax and custom CSS can now be simple controls with live feedback inside a Gutenberg block. It&rsquo;s really a game-changer for getting people comfortable with customizing things like gallery styling &mdash; which is the number one thing photographers need to do.&rdquo;</p>\n\n\n\n<p>The primary piece of the PhotoPress plugin is its custom PhotoPress Gallery block. It allows users to choose between a range of gallery styles, such as columns, masonry, justified, and mosaic. Each style has its own options. Images can also be launched into a slideshow when one is clicked.</p>\n\n\n\n<p>Based on some quick tests, the block&rsquo;s front-end output will go farther with some themes than others. This is mainly because of conflicting CSS and issues which can be solved by testing against more themes.</p>\n\n\n\n<p>Aside from the block, the plugin can automatically extract image metadata and group that data through custom taxonomies, such as cameras, lenses, locations, keywords, and more. WordPress stores this information out of the box, but it is hidden away as post meta. The plugin uses the taxonomy system to make it manageable for end-users.</p>\n\n\n\n<p>Ultimately, Adams set out to create a photography plugin that fits in with the WordPress admin user interface and experience, which he has accomplished.</p>\n\n\n\n<h2>The Future of PhotoPress</h2>\n\n\n\n<p class=\"has-drop-cap\">The project is still a work in progress. Adams is still moving through Phase I of the four-phase plan. Once it is complete, he can move on to the next steps in the process.</p>\n\n\n\n<p>Phase II is to create themes that are designed specifically to work with the PhotoPress plugin. He has three planned thus far. One for handling portfolio sites. Another for creating a stock photo archive. And the last for photojournalism and exhibits. Each will be built on top of his <a href=\"https://github.com/photopress-dev/frame\">photography theme framework</a>.</p>\n\n\n\n<p>The themes in Phase II will likely be commercial products. Adams said he needs a way to fund the next phases of the project. He hopes to have this step underway by the end of the year.</p>\n\n\n\n<p>For 2021, he wants to begin tackling Phases III and IV. The former will be a website-as-a-service (WaaS) similar to WordPress.com but for photographers. It will begin as a paid project but could have some free options for emerging photographers and students. The final phase is to build an onboarding system.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 25 Sep 2020 19:08:15 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:38;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"WPTavern: Google Officially Releases Its Web Stories for WordPress Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105227\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:191:\"https://wptavern.com/google-officially-releases-its-web-stories-for-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=google-officially-releases-its-web-stories-for-wordpress-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5593:\"<img />Web Stories for WordPress dashboard.\n\n\n\n<p class=\"has-drop-cap\">Two and a half months after the <a href=\"https://wptavern.com/google-launches-beta-of-amp-powered-web-stories-plugin-for-wordpress\">launch of its public beta</a>, Google <a href=\"https://blog.google/web-creators/create-compelling-web-stories-wordpress/\">released its Web Stories</a> for WordPress plugin. So far, the plugin has over 10,000 active installations and has garnered a solid five-star rating from four reviews.</p>\n\n\n\n<p>Google created the Web Stories format through its AMP Project to allow publishers to create visually-rich stories. It is primarily geared toward mobile site visitors, allowing them to quickly jump through story pages with small chunks of content.</p>\n\n\n\n<p>The <a href=\"https://wordpress.org/plugins/web-stories/\">Web Stories plugin</a> creates a visual interface within WordPress for creating Stories. It breaks away from the traditional WordPress interface and introduces users to an almost Photoshop-like experience for building out individual Stories. The Stories editor is completely drag-and-drop.</p>\n\n\n\n<p>The plugin also offers eight predesigned templates out of the box that cover a small range of niches. However, according to Google&rsquo;s announcement, the company plans to add more templates in future updates.</p>\n\n\n\n<h2>Web Stories Are for Storytelling</h2>\n\n\n\n<p>&ldquo;Firstly&hellip;the power of Stories,&rdquo; wrote Jamie Marsland, founder of Pootlepress, in a <a href=\"https://twitter.com/pootlepress/status/1309020235102597122\">Twitter thread</a>. &ldquo;Stories are how we (humans) see the world and share our experiences. Up to now the platforms that we have to tell stories have been limited to books/films/tv/websites/blogs/instagram stories etc.&rdquo;</p>\n\n\n\n<p>&ldquo;Websites are ok for telling stories but in many ways the format doesn&rsquo;t really fit the linear arc of storytelling. When Marshall McLuhan said &lsquo;the medium is the message&rsquo; in 1964 he was talking about how the medium itself has a social impact, and change the communication itself&hellip;and the possibilities for what is communicated and how it is perceived. But we should keep coming back to Stories. Stories are the key here imo. Now we have an open format to tell Stories, and we have an open platform (WordPress) where those Stories can be told easily.&rdquo;</p>\n\n\n\n<p>Marsland finished his thread by saying that using Stories as a replacement for a brochure or website is a missed opportunity. He said that it was a platform for storytelling and should be used as such.</p>\n\n\n\n<p>It is far too early to tell if Web Stories will simply be a fad or still in wide use years from now. The technology certainly lends itself well to telling stories, particularly in mobile format, but I doubt we have seen the best of what is possible on the web. The format feels too limited to be the end-all-be-all of storytelling. It is merely one medium that will live and die by its popularity with users.</p>\n\n\n\n<p>With the right design skills, some people will craft beautiful Web Stories. And, that is just what Marsland has done with the <a href=\"https://jamiemarsland.staging.wpengine.com/web-stories/wilson-and-pootle/\">first Story he shared</a>:</p>\n\n\n\n<img />Page from the Wilson and Pootle Web Story by Jamie Marsland.\n\n\n\n<p>I agree with his conclusion. Web Stories should be about storytelling. When you move outside of that zone, the technology feels out of place.</p>\n\n\n\n<p>Where I disagree is that websites are not ideal for storytelling. Ultimately, the WordPress block editor will allow artistic end-users to craft intricate stories, mixing content and design in ways that we have not seen. We are just now scratching the surface. I expect our community of developers to build more intricate tools than what the Web Stories plugin currently allows, and we can do so in a way that revolutionizes storytelling on the web.</p>\n\n\n\n<h2>New Features</h2>\n\n\n\n<img />Story editor with Unsplash photo integration.\n\n\n\n<p class=\"has-drop-cap\">The Web Stories plugin now adds support for Unsplash images and Coverr videos out of the box. The plugin adds a new tab with a &ldquo;media&rdquo; icon. For users of the first beta version of the plugin, this may be a bit confusing. The previous media icon was for a tab that displayed the user&rsquo;s media. Now, the user&rsquo;s media is under the tab with the &ldquo;upload&rdquo; icon.</p>\n\n\n\n<p>It is also not immediately clear that the Unsplash images and Coverr videos are not hosted on the site itself. There is a &ldquo;powered by&rdquo; notice at the bottom of the tab, but it can be easy to miss because it blends in with the media in the background.</p>\n\n\n\n<p>Media from Unsplash and Coverr is hosted off-site and not downloaded to the user&rsquo;s WordPress media library. I could find no mention of this in the plugin&rsquo;s documentation. Such hotlinking was a <a href=\"https://wptavern.com/unsplash-responds-to-image-licensing-concerns-clarifies-reasons-for-hotlinking-and-tracking\">cause for debate</a> over the recent official release of the Unsplash plugin.</p>\n\n\n\n<p>Google also announced it planned to add more &ldquo;stock media integrations&rdquo; in the near future. According to a <a href=\"https://docs.google.com/document/d/1q8rkYYMKZh3R2eqkpwgGkx6QX0oSXoLYtIO6ml1BFD0/edit#heading=h.xqcejitqohdk\">document</a> shared via a GitHub <a href=\"https://github.com/google/web-stories-wp/issues/3909#issuecomment-674053068\">ticket</a>, such future integrations may include Google Photos and GIF-sharing site Tenor.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 24 Sep 2020 21:13:42 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:39;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:106:\"WPTavern: W3C Drops WordPress from Consideration for Redesign, Narrows CMS Shortlist to Statamic and Craft\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105108\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:255:\"https://wptavern.com/w3c-drops-wordpress-from-consideration-for-redesign-narrows-cms-shortlist-to-statamic-and-craft?utm_source=rss&utm_medium=rss&utm_campaign=w3c-drops-wordpress-from-consideration-for-redesign-narrows-cms-shortlist-to-statamic-and-craft\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:11563:\"<p>The <a href=\"https://www.w3.org/\">World Wide Web Consortium</a> (<em>W3C</em>), the international standards organization for the web,&nbsp;is redesigning its website and will soon be selecting a new CMS. Although WordPress is&nbsp;already used to manage W3C&rsquo;s <a href=\"https://www.w3.org/blog/\">blog</a> and <a href=\"https://www.w3.org/blog/news/\">news</a> sections of the website, the organization is open to adopting a new CMS to meet its list of preferences and <a href=\"https://w3c.studio24.net/docs/cms-strategy-and-requirements/\">requirements</a>. </p>\n\n\n\n<p>Studio 24, the digital agency selected for the redesign project, narrowed their consideration to three CMS candidates:</p>\n\n\n\n<ol><li><a href=\"https://w3c.studio24.net/docs/w3c-cms-selection-process-update/#statamic\">Statamic</a></li><li><a href=\"https://w3c.studio24.net/docs/w3c-cms-selection-process-update/#craft-cms\">Craft CMS</a></li><li><a href=\"https://w3c.studio24.net/docs/w3c-cms-selection-process-update/#wordpress\">WordPress</a></li></ol>\n\n\n\n<p>Studio 24 was aiming to finalize their recommendations in July but found that none of them complied with the W3C&rsquo;s authoring tool <a href=\"https://www.w3.org/WAI/standards-guidelines/atag/\">accessibility guidelines</a>. The CMS&rsquo;s that were better at compliance with the guidelines were not as well suited to the other project requirements.</p>\n\n\n\n<p>In the most recent project <a href=\"https://w3c.studio24.net/updates/weeknotes-11-sept/\">update</a> posted to the site, Studio 24 reported they have&nbsp;shortlisted two CMS platforms. Coralie Mercier, Head of Marketing and Communications at W3C, confirmed that these include Statamic and Craft CMS.</p>\n\n\n\n<p>WordPress was not submitted to the same review process as the Studio 24 team claims to have extensive experience working with it. In the summary of their concerns, Studio 24 cited Gutenberg, accessibility issues, and the fact that the Classic Editor plugin will <a href=\"https://make.wordpress.org/core/2018/11/07/classic-editor-plugin-support-window/\">stop being officially maintained on December 31st, 2021</a>:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>First of all, we have concerns about the longevity of WordPress&nbsp;<strong>as we use it</strong>. WordPress released a new version of their editor in 2018: Gutenberg. We have already rejected the use of Gutenberg in the context of this project due to accessibility issues.</p><p>If we choose to do away with Gutenberg now, we cannot go back to it at a later date. This would amount to starting from scratch with the whole CMS setup and theming.</p><p>Gutenberg is the future of WordPress. The WordPress core development team keeps pushing it forward and wants to roll it out to all areas of the content management system (navigation, sidebar, options etc.) as opposed to limiting its use to the main content editor as is currently the case.</p><p>This means that if we want to use WordPress long term, we will need to circumvent Gutenberg and keep circumventing it for a long time and in more areas of the CMS as time goes by.&nbsp;</p></blockquote>\n\n\n\n<p>Another major factor in the decision to remove WordPress from consideration was that they found &ldquo;no elegant solution to content localization and translation.&rdquo;</p>\n\n\n\n<p>Studio 24 also expressed concerns that tools like ACF, Fewbricks, and other plugins might not being maintained for the Classic Editor experience &ldquo;in the context of a widespread adoption of Gutenberg by users and developers.&rdquo;</p>\n\n\n\n<p>&ldquo;More generally, we think this push to expand Gutenberg is an indication of WordPress focusing on the requirements of their non-technical user base as opposed to their audience of web developers building custom solutions for their clients.&rdquo;</p>\n\n\n\n<p>It seems that the digital agency W3C selected for the project is less optimistic about the future of Gutenberg and may not have reviewed recent improvements to the overall editing experience since 2018, including those related to accessibility. </p>\n\n\n\n<p>Accessibility consultant and WordPress contributor Joe Dolson recently gave an <a href=\"https://www.youtube.com/watch?v=EKZulmYKYJg\">update on Gutenberg accessibility audit</a> at WPCampus 2020 Online. He reported that while there are still challenges remaining, many issues raised in the audit have been addressed across the whole interface and 2/3 of them have been solved. &ldquo;Overall accessibility of Gutenberg is vastly improved today over what it was at release,&rdquo; Dolson said.</p>\n\n\n\n<p>Unfortunately, Studio 24 didn&rsquo;t put WordPress through the same content creation and accessibility tests that it used for Statamic and Craft CMS. This may be because they had already planned to use a Classic Editor implementation and didn&rsquo;t see the necessity of putting Gutenberg through the paces. </p>\n\n\n\n<p>These <a href=\"https://w3c.studio24.net/docs/w3c-cms-selection-process-update/#the-review-process\">tests</a> involved creating pages with &ldquo;flexible components&rdquo; which they referred to as &ldquo;blocks of layout,&rdquo; for things like titles, WYSIWYG text input, and videos. It also involved creating a template for news items where all the content input by the user would be displayed (without formatting). </p>\n\n\n\n<p>Gutenberg would lend itself well to these uses cases but was not formally tested with the other candidates, due to the team citing their &ldquo;extensive experience&rdquo; with WordPress. I would like to see the W3C team revisit Gutenberg for a fair shake against the proprietary CMS&rsquo;s. </p>\n\n\n\n<h2>W3C Is Prioritizing Accessibility Over Its Open Source Licensing Preferences</h2>\n\n\n\n<p>The document outlining the CMS requirements for the project states that &ldquo;W3C has a strong preference for an open-source license for the CMS platform&rdquo; as well as &ldquo;a CMS that is long-lived and easy to maintain.&rdquo; This preference may be due to the economic benefits of using a stable, widely adopted CMS, or it may be inspired by the undeniable symbiosis between open source and open standards.</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>&ldquo;The industry has learned by experience that the only software-related standards to fully achieve [their] goals are those which not only permit but encourage open source implementations. Open source implementations are a quality and honesty check for any open standard that might be implemented in software&hellip;&rdquo;</p><cite><a href=\"https://opensource.org/osr-rationale\">Open Source Initiative</a></cite></blockquote>\n\n\n\n<p>WordPress is the only one of the three original candidates to be distributed under an&nbsp;<a href=\"https://opensource.org/licenses\">OSD-compliant license</a>.&nbsp;(CMS code available on GitHub isn&rsquo;t the same.)</p>\n\n\n\n<p>Using proprietary software to publish the open standards that underpin the web isn&rsquo;t a good look. While proprietary software makers are certainly capable of implementing open standards, regardless of licensing, there are a myriad of benefits for open standards in the context of open source usage: </p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>&ldquo;The community of participants working with OSS may promote open debate resulting in an increased recognition of the benefits of various solutions and such debate may accelerate the adoption of solutions that are popular among the OSS participants. These characteristics of OSS support evolution of robust solutions are often a significant boost to the market adoption of open standards, in addition to the customer-driven incentives for interoperability and open standards.&rdquo;</p><cite><a href=\"http://airccse.org/journal/ijsea/papers/0111ijsea01.pdf\">International Journal of Software Engineering &amp; Applications</a></cite></blockquote>\n\n\n\n<p>Although both Craft CMS and Statamic have their code bases available on GitHub, they share similarly restrictive licensing models. The Craft CMS <a href=\"https://github.com/craftcms/cms/blob/develop/CONTRIBUTING.md\">contributing document</a> states:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p><strong>Craft isn&rsquo;t FOSS</strong><br />Let&rsquo;s get one thing out of the way: Craft CMS is <strong>proprietary software</strong>. Everything in this repo, including community-contributed code, is the property of Pixel &amp; Tonic.</p><p>That comes with some limitations on what you can do with the code:</p><p>&ndash; You can&rsquo;t change anything related to licensing, purchasing, edition/feature-targeting, or anything else that could mess with our alcohol budget.<br />&ndash; You can&rsquo;t publicly maintain a long-term fork of Craft. There is only One True Craft.</p></blockquote>\n\n\n\n<p>Statamic&rsquo;s contributing docs have similar restrictions:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Statamic is not Free Open Source Software. It is <strong>proprietary</strong>. Everything in this and our other repos on Github &mdash; including community-contributed code &mdash; is the property of Wilderborn. For that reason there are a few limitations on how you can use the code:</p></blockquote>\n\n\n\n<p>Projects with this kind of restrictive licensing often fail to attract much contribution or adoption, because the freedoms are not clear. </p>\n\n\n\n<p>In a GitHub issue <a href=\"https://github.com/craftcms/cms/issues/842\">requesting Craft CMS go open source</a>, Craft founder and CEO Brandon Kelly said, &ldquo;Craft isn&rsquo;t closed&nbsp;<em>source</em>&nbsp;&ndash;&nbsp;all the source code is right here on GitHub,&rdquo; and claims the license is relatively unrestrictive as far as proprietary software goes, that contributing functions in a similar way to FOSS projects.  This rationale is not convincing enough for some developers commenting on the thread.</p>\n\n\n\n<p>&ldquo;I am a little hesitant to recommend Craft with a custom open source license,&rdquo; Frank Anderson said. &ldquo;Even if this was a MIT+ license that added the license and payment, much like React used to have. I am hesitant because the standard open source licenses have been tested.&rdquo;</p>\n\n\n\n<p>When asked about the licensing concerns of Studio 24 narrowing its candidates to two proprietary software options, Coralie Mercier told me, &ldquo;we are prioritizing accessibility.&rdquo; A recent project <a href=\"https://w3c.studio24.net/updates/weeknotes-11-sept/\">update</a> also reports that both CMS suppliers W3C is reviewing &ldquo;have engaged positively with authoring tool accessibility needs and have made progress in this area.&rdquo;</p>\n\n\n\n<p>Even if you have cooperative teams at proprietary CMS&rsquo;s that are working on accessibility improvements as the result of this high profile client, it cannot compare to the massive community of contributors that OSD-compliant licensing enables. </p>\n\n\n\n<p>It&rsquo;s unfortunate that the state of open source CMS accessibility has forced the organization to narrow its selections to proprietary software options for its first redesign in more than a decade. </p>\n\n\n\n<p>Open standards go hand in hand with open source. There is a mutually beneficial connection between the two that has caused the web to flourish. I don&rsquo;t see using a proprietary CMS as an extension of W3C values, and it&rsquo;s not clear how much more benefit to accessibility the proprietary options offer in comparison. W3C may be neutral on licensing debates, but in the spirit of openness, I think the organization should adopt an open source CMS, even if it is not WordPress.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 24 Sep 2020 20:13:24 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:40;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"WPTavern: First Look at Twenty Twenty-One, WordPress’s Upcoming Default Theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105166\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:195:\"https://wptavern.com/first-look-at-twenty-twenty-one-wordpresss-upcoming-default-theme?utm_source=rss&utm_medium=rss&utm_campaign=first-look-at-twenty-twenty-one-wordpresss-upcoming-default-theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6907:\"<blockquote class=\"wp-block-quote\"><p>Fashion is ephemeral. Art is eternal. Indeed what is a fashion really? A fashion is merely a form of ugliness so absolutely unbearable that we have to alter it every six months!</p></blockquote>\n\n\n\n<p>Thus wrote Oscar Wilde on Victorian-era fashion in an article titled &ldquo;The Philosophy of Dress&rdquo; for the <em>New-York Tribune</em> in 1885.</p>\n\n\n\n<p>In many ways, WordPress theming is the same as the ever-changing landscape of fashion. Rounded corners are in one day and out the next. Box shadows are in one year after being frowned up just months earlier. Perhaps web design is so intolerable that we must change it every six months. Or, at least freshen it up every year in the case of WordPress.</p>\n\n\n\n<p>If art is eternal, there are only two default, Twenty* themes that I can truly recall from past years: Twenty Ten and Twenty Fourteen &mdash; yes, Twenty Twenty is memorable, but it is also still the current default. Twenty Ten was a classic that paid homage to WordPress&rsquo;s past. Twenty Fourteen was such a leap away from tradition that it is hard to forget. Everything else has seemed to fade to varying degrees.</p>\n\n\n\n<p>With WordPress 5.6 and the end of the year looming, it is time to look forward to the latest trend. As Mel Choyce-Dwan noted in the <a href=\"https://make.wordpress.org/core/2020/09/23/introducing-twenty-twenty-one/\">announcement of Twenty Twenty-One</a>, the next default theme, &ldquo;<a href=\"https://www.garnishstudios.com/\">Pastels</a> and <a href=\"https://www.designbyparker.com/\">muted</a> <a href=\"https://westportcondos.ca/\">colors</a> are <a href=\"https://arisacoba.com/\">pretty</a> <a href=\"https://www.collaborativechange.global/\">in</a> <a href=\"https://paradigmacreation.com/\">right</a> <a href=\"https://taregrocery.com/\">now</a>.&rdquo;</p>\n\n\n\n<p>She is not wrong. The colors are a refreshing change of pace. Now that we are into the second day of autumn, I am getting <em>the good kind of vibes</em> from some of the more earthy-tones from a couple of the color palettes expected to ship with the theme.</p>\n\n\n\n<img />Potential color palette options for Twenty Twenty-One.\n\n\n\n<p>Whether Twenty Twenty-One will be a fashionable theme for the year or art that we can remember a decade from now, only history will be able to judge. For now, let&rsquo;s enjoy the creation and take a look at what we should expect from the next default WordPress theme.</p>\n\n\n\n<h2>The Current Twenty Twenty-One</h2>\n\n\n\n<p class=\"has-drop-cap\">The new default theme is a fork of <a href=\"https://wordpress.org/themes/seedlet/\">Automattic&rsquo;s Seedlet</a>, a project in which I lauded as the <a href=\"https://wptavern.com/exploring-seedlet-automattics-block-first-wordpress-theme\">next step in the evolution of theming</a>. It is a theme that is focused on WordPress&rsquo;s future of being completely comprised of blocks. It gives us an ideal insight into where theme development is heading. It makes sense as the foundation for the new default. Few other themes would make for a good starting point right now. With WordPress theme development in flux, Seedlet is simply ahead of the pack in terms of foundational elements.</p>\n\n\n\n<img />Seedlet WordPress theme screenshot.\n\n\n\n<p>&ldquo;This provides us with a thorough system of nested CSS variables to make child theming easier, and to help integrate with the global styles functionality that&rsquo;s under development for full-site editing,&rdquo; wrote Choyce-Dwan of using Seedlet as a starting point.</p>\n\n\n\n<p>There are no plans to spin up a Google Web Font for this theme. The design team is going native and sticking with the default system font stack. Choyce-Dwan listed several reasons for the choice, such as keeping a neutral font that allows broad use, speed, and customizability via a child theme.</p>\n\n\n\n<p>Despite the neutral font, the default pastel green is a fairly opinionated design decision. It will not be used broadly across industries. However, the team plans to create multiple color palettes that will give it more range. Presumably, these palettes can also be overwritten.</p>\n\n\n\n<img />Pastel green color scheme on single post view.\n\n\n\n<p>Other than the colors, the design is relatively simple. Choyce-Dwan said that the theme&rsquo;s block patterns support is where it will be truly unique.</p>\n\n\n\n<p>I was initially <a href=\"https://wptavern.com/decision-time-what-block-patterns-should-ship-with-wordpress-5-5\">unhappy with the patterns</a> that were going to ship with WordPress 5.5. However, an 11th-hour <a href=\"https://wptavern.com/gutenberg-8-7-adds-minor-changes-updates-block-pattern-designs-and-continues-full-site-editing-work\">update improved the situation</a> so that they did not feel entirely experimental. The foundational Seedlet theme for Twenty Twenty-One has some unique patterns that begin to scratch the surface of what&rsquo;s possible with this WordPress feature. My hope is that the new default theme steps it up a notch.</p>\n\n\n\n<p>Currently, the theme does not register any custom patterns. However, it has a placeholder file and a note that they are a work in progress. Choyce-Dwan shared some patterns the team has already designed in the announcement.</p>\n\n\n\n<img />Currently-designed block patterns.\n\n\n\n<p>&ldquo;We&rsquo;ll be relying on our talented community designers for more ideas,&rdquo; she wrote. The team has also created a GitHub template for anyone to <a href=\"https://github.com/WordPress/twentytwentyone/issues\">contribute pattern design ideas</a>.</p>\n\n\n\n<p>Currently, the theme does not support the upcoming full-site editing feature of WordPress. After the Beta 1 release of WordPress 5.6, the team plans to begin exploring the addition of this support. WordPress is expected to ship a public beta of full-site editing in its <a href=\"https://make.wordpress.org/core/2020/08/13/wordpress-5-6-release-planning/\">next major release</a>, but it is unclear whether it will be far enough along to be a headline feature for the Twenty Twenty-One theme.</p>\n\n\n\n<p>The team and volunteers have less than a month before the October 20th deadline for committing the new theme to trunk, the core WordPress development branch. At that stage, the theme should be nearly complete and ready for production. Of course, there will be several rounds of patches, bug fixes, and updates before WordPress 5.6 lands in December. Right now is the best time for anyone who wants to get involved with Twenty Twenty-One to do so.</p>\n\n\n\n<p>Useful links with more information:</p>\n\n\n\n<ul><li><a href=\"https://github.com/WordPress/twentytwentyone\">GitHub Repository</a></li><li><a href=\"https://www.figma.com/file/Fv7BODXobfo2prksqRDySy/Introducing-Twenty-Twenty-One?node-id=0%3A1\">Theme Mockups via Figma</a></li><li><a href=\"https://www.pinterest.com/melchoyce/tt1/\">Twenty Twenty-One Idea Pinterest Board</a></li></ul>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 23 Sep 2020 20:01:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:41;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"HeroPress: Hello World – Hevo Nyika\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=3308\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:176:\"https://heropress.com/essays/hello-world-discovering-the-world-through-wordpress/#utm_source=rss&utm_medium=rss&utm_campaign=hello-world-discovering-the-world-through-wordpress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:14438:\"<img width=\"960\" height=\"480\" src=\"https://s20094.pcdn.co/wp-content/uploads/2021/09/092220-min.jpg\" class=\"attachment-large size-large wp-post-image\" alt=\"Pull Quote: Find your purpose, pursue it relentlessly\" /><p><a href=\"https://heropress.com/feed/#shona\"><span class=\"css-901oao css-16my406 r-1qd0xha r-ad9z0x r-bcqeeo r-qvutc0\">Unokwanisa kuverenga rondedzero iyi muChiShona</span></a></p>\n<p>So I chose a career in Web Development!!</p>\n<p>To be honest it&#8217;s kind of funny when I think about it and quite surreal to be here talking about my story. It has been a journey and I would like to share my story with you.</p>\n<p>I have been lucky in the Dad department. My Dad encouraged me to work hard and dream big from a very young age. I remember occasionally having ‘when I grow up’ talks.</p>\n<p>For quite some time I wanted to be a Judge, however awesome this dream sounds it was not very inspired. After binge-watching Judge Judy for a whole weekend, I started calling myself Judge Thelma. Though I don&#8217;t remember much of this my sister says that I used to say I would arrest all the men in the World if I ever became a Judge. HAHAHA! (clearly I didn&#8217;t understand how the World works)</p>\n<p>I did not understand what being a Judge meant or what was required for me to start banging that gavel to my heart&#8217;s desire. Eventually, I learnt that I had to become a lawyer first then magistrate before I could be nominated to be a Judge and let us just say that is how I sentenced that dream to a lifetime down the drain.</p>\n<p>See what I did there? hahaha!</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2021/09/tandd-min.jpg\"><img /></a>With Daddy Dearest\n<p>A few years later, I was in High School and that is when I decided to pursue a career in Computer Science. I did not know what I would be doing or how I would get there but I just knew that I was going to pursue a career in ICT. I wrote my first line of code when I was 16 years old.</p>\n<p>This was after I had joined the school&#8217;s computer class, initially, I thought I would be learning about Excel Sheets and Word Documents until I was assigned to write my first program in C (talk about a double-take!!). It was not easy but it was very exciting, l remember writing up simple code for a Video Club &#8211; a simple check-in/out for VHS tapes and CDs. Dear World, thus began my fascination with computers.</p>\n<p>Seven years later, I was now in university studying ICT as I had always wanted. I was doing a Bachelors in Business Management &amp; Information Technology. In my third year, I was interning at a local Webdesign and hosting company. This was never my plan, I only took on that job after I had failed to get a job with local banks or telecommunications companies. Before I was introduced to Website Design I envisioned myself suiting up and working in IT Audit or offering IT support. Even though things did not go as I had planned, I am glad they did not exactly go my way in that aspect. So in 2017, I was designing websites using HTML, CSS, PHP, JavaScripts and Joomla which was the prefered content management system at that company. I knew about WordPress but I was not using it for anything. People have this misconception that WordPress is not for real developers and it is not secure and at that time I was one of those people.</p>\n<h3>Finding my tribe</h3>\n<p>One day when I was working at the front desk <a href=\"https://heropress.com/essays/wordpress-opened-whole-new-world/\">Thabo Tswana</a> came to give a colleague of mine a purple WooCommerce pen. I did not know what WooCommerce was at that time but I was taken by the purple shirt and pen he was carrying. I asked him about it and he explained what WooCommerce was and that what he was carrying was called &#8216;swag&#8217;. So the love of freebies led me to the WordCamp Harare website, instead of buying a ticket I applied to volunteer. I learnt more about WordPress, I was a volunteer, without any knowledge on WordPress.org or WordPress.com. I only started using WordPress because of the awesome people that l had met at that Wordcamp.</p>\n<p>Everyone was so welcoming, a week later with help from Thabo I designed my first ever WP website.</p>\n<p>Soon after I was part of the community and a bit more involved in the meetups. We had our first-ever Women Who WordPress meetup in 2018. So many ladies came on board bloggers and developers alike. We were free to talk and discuss a lot of things. We had more time to discuss the difference between WordPress.com and WordPress.org we shared views on how to handle discrimination at work, how to promote your website and a whole lot of other things.</p>\n<p><a href=\"https://s20094.pcdn.co/wp-content/uploads/2021/09/20180324_105352-min.jpg\"><img /></a></p>\n<h3>Establishing roots</h3>\n<p>In 2018, Harare had its first-ever female Lead Organiser <a href=\"https://tapiwanashe.com/\">Tapiwanashe Manhobo</a> whoop whoop! I was also part of the organising team that year, I was assigned to handle Harare’s first Kids Camp. The planning process was stressful because the economic crisis in Zimbabwe was getting worse, luckily we had over 8 months to plan and with help from sponsors, we managed to pull through. In the end, everything turned out great. I wrote an article about the <a href=\"https://thelmachido.wordpress.com/2019/11/21/wordpress-juniours-first-edition/\">Kids Camp here</a>.</p>\n<p>After the first Kids Camp, we had several WordPressors that were enthusiasts about encouraging kids to embrace ICT. In 2019 we had not planned to have a Kids Camp because of financial constraints but to our surprise, we had some anonymous donations and we managed to have a WordPress Community outreach to a youth centre a week after our WordCamp. We had the outreach at the <a href=\"https://cttzim.org/\">Centre for Total Transformation</a> which is a non-formal school that caters for underprivileged and vulnerable children. We taught them about WordPress, Computer Hardware and Software.</p>\n<p>Here is a small video I took with Ellen when we were about to leave. Did l mention that I am terrible on camera? hahaha!</p>\n<div class=\"wp-video\"><a href=\"https://thelmachido.me/vid.mp4\">https://thelmachido.me/vid.mp4</a></div>\n<p><a href=\"https://thelmachido.wordpress.com/2020/09/18/kids-camp-2019-centre-for-total-transformation/\">Kids Camp 2019 &#8211; Centre for Total&nbsp;Transformation</a></p>\n<p>I have fallen deeply for WordPress because of the Community, I enjoy attending WordCamps, meeting new people and just learning new stuff. I have a huge list of WordCamps I need to attend before l kick the bucket, hopefully. Last year I managed to cross WordCamp</p>\n<p>Johannesburg off my bucket list. This year I was going to attend WordCamp Capetown but unfortunately, 2020 had other plans for the whole world. Anyway when everything is back to normal my plan to travel to WordCamps will proceed. (fingers crossed)</p>\n<h3>Reaping Fruits</h3>\n<p>Meanwhile, my plan to improve my developing skills has not been on hold. Even though I can still cook up code in C and Java, for now, I have also included WordPress PHP functions to the mix. It was not easy to get to this point, daring myself got me to this slightly better stage. My IQ is not way up there, however, I try to do my best where I can and I am happy to say it has paid off so far.</p>\n<p>Around November last year, I was designing as a freelancer while job hunting. Out of the blue l got a call for a job offer from <a href=\"https://zw.linkedin.com/in/trust-nhokovedzo\">Trust Nhokovenzo</a> who is big on <a href=\"https://afrodigital.org/\">Digital marketing</a> and also part of the WordPress Community. He had asked someone in the community about developers and my name happened to come up. So since February, I have been part of his team at <a href=\"https://calmlock.co.zw/\">Calmlock Digital Marketing Agency</a>.</p>\n<p>There is so much more in the world of WordPress that l am yet to tap into so even though I am ending my write up here, for now, my story is going to continue &#8230;</p>\n<p>Until next time&#8230;</p>\n<h1 id=\"shona\">Hevo Nyika</h1>\n<p>Saka ini ndakasarudza kugadzira mawebhusayiti.</p>\n<p>Ndakaita rombo rakanaka pana baba vandakapihwa naMwari. Baba vangu vaindikurudzira kuti ndishande nesimba. Ndinoyeuka pano neapo tichiita hurukuro dzedu dzekuti ‘kana ndakura ndoda kuveyi’.</p>\n<p>Kwenguva yakati rebei ndaida kuve Mutongi. Kunyangwe ini ndisingazvirangariri mukoma wangu anotaura kuti ndaiti ndaizosunga varume vese vari pasi rino kana ndikangoita mutongi HAHAHA zveshuwa handaiziva kuti mitemo yenyika inofambiswa seyi.<br />\nNdanga ndisinga nzwisisi kuti kuva mutongi kwairevei kana zvaidikanwa kwandiri kuti nditange kurova iro ghavheu kuchishuwo chemoyo wangu. Pakupedzisira, ndakadzidza kuti ndaifanirwa kuzoita gweta ipapo magistrate ndisati ndasarudzwa kuita Mutongi naizvozvo ndokupera kwakaita chiroto chekuva Mutongi.</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2021/09/tandd-min-1.jpg\"><img /></a>Na Baba Vangu\n<p>Gare gare papfura makore mashoma pandakanga ndave kuHigh School ndakanga ndakuda kuita basa rema kombiyuta. Ndakanyora mutsara wekutanga wekodhi pandaive nemakore gumi nematanhatu. Izvi zvakaitika mushure mekunge ndapinda mukirasi yemakombiyuta, pakutanga ndaifunga kuti ndinenge ndichidzidza nezveExcel Sheets neWord zvisineyi ndakaona ndakunyora kodhi yangu yekutanga muC. Zvaisave nyore kunyora kodhi asi zvainakidza kwazvo, ndorangarira ndichinyora kodhi yeVhidhiyo Kirabhu.</p>\n<p>Makore manomwe apfura, ndakanga ndava kuyunivhesiti ndichidzidza ICT zvandakagara ndakaronga. Ndaiita Bachelors muBusiness Management &amp; Information Technology. Mugore rangu rechitatu ndainge ndave kushanda kune imwe kambani yaita zvekugadzira mawebhusaiti. Ndakawana basa iri mushure mekunge ndatadza kuwana basa kumabhanga. Kunyangwe hazvo zvinhu zvisina kuenda sezvandaive ndakaronga, ndinofara kuti hazvina kunyatso enda nenzira yangu. Saka muna 2017 ndaigadzira mawebhusaiti ndichishandisa HTML, CSS, PHP, JavaScript uye Joomla iyo yaive iyo inokurudzirwa kukambani kwandaive. Panguva iyi ndaiziva nezve WordPress asi ndakanga ndisingaishandisi.</p>\n<h3>Kuwanana neWordPress</h3>\n<p>Rimwe zuva pandakanga ndichishanda ndakaona <a href=\"https://heropress.com/essays/wordpress-opened-whole-new-world/\">Thabo Tswana</a> akauya kuzopa mumwe mukomana wandayishanda naye chinyoreso cheWooCommerce. Ndakanga ndisingazive kuti WooCommerce yaive chii asi ndakafarira chinyoreso nehembe ye WooCommerce yaanga akapfeka. Ndakamubvunza nezvazvo akatsanangura kuti WooCommerce yaive chii. Saka nekudawo zvakanaka, zvemahara ndakaenda pawebhusaiti yeWordCamp Harare ndikabata zvimbo zvegore iroro. Ndakazvipira kubatsirawo vamwe vekuWordPress kuWordCamp Harare. Nerubatsiro kubva kunaThabo ndakagadzira webhusaiti yangu yekutanga yeWordPress vhiki rakatevera .</p>\n<p>Mushure mekunge ndaitawo chipato cheavo vanoshandisa WordPress ndakanga ndakuenda kumisangano yeWordPress yaitwa muHarare. Takaita musangano wevakadzi chete muna 2018. Vakadzi vazhinji vakauya kumusangano uyu. Tainga takasununguka kukurukura zvinhu zvakawanda. Takakurukura pamusoro pemutsauko uripo pakati peWordPress.com neWordPress.org takagovana maonero ekugadzirisa rusarura kubasa nezvimwewo.</p>\n<p><a href=\"https://s20094.pcdn.co/wp-content/uploads/2021/09/20180324_105352-min.jpg\"><img /></a></p>\n<h3>Nguva yandakatanga kushandisa WordPress</h3>\n<p>Muna 2018, kurongwa kweWordCamp Harare kwakatungamirwa kekutanga nemusikana ainzi <a href=\"https://tapiwanashe.com/\">Tapiwanashe Manhobo</a> (waiva mufaro mukuru). Ndakanga ndiri mumwe wevairongawo naye. Hurongwa hwekuronga WordCamp Harare mugore iri hwainetsa pamusaka pekuoma kwehupfumi wemuZimbabwe, zvisineyi takaita rombo rakanaka nokuti takawana rubatsiro kubva kunevamwewo vanhu vakatiwedzera mari. Pakupedzisira, zvese zvakabudirira zvakanaka. Takarongawo WordCamp yevana varipasi pemakore gumi nechishanu, munokwanisa kuverenga pamusoro pezuva iri <a href=\"https://thelmachido.wordpress.com/2019/11/21/wordpress-juniours-first-edition/\">pawebhisaiti yangu apa</a>.</p>\n<p>Mushure mekuita WordCamp yevana, takave nevamwe vanhu veWordPress aifarira kukurudzira vana kuti vagamuchire ICT. Muna 2019 takanga tisina kuronga kuve neWordCamo yeVana nekuda kwezvimhingamupinyi zvemari asi chakatishamisa ndechekuti takawana mari kubvawo kune vamwe. Takaita Camp iyi pa<a href=\"https://cttzim.org/\">Centre for Total Transformation</a> chinova chikoro chisiri chepamutemo chinodzidzisa vana vanotambura. Tadzidzisa vana ava pamusoro peWordPress, Computer Hardware uye Software.</p>\n<div class=\"wp-video\"><a href=\"https://thelmachido.me/vid.mp4\">https://thelmachido.me/vid.mp4</a></div>\n<p>Ndofarira WordPress zvakanyanya nekuda kweavo varimu nharaunda yacho, ini ndinonakidzwa nekuenda kumaWordCampi, kusangana nevanhu vatsva uye kungo dzidza zvinhu zvitsva. Gore rakapera ndakakwanisa kuyambuka muganhu weZimbabwe ndichienda kuWordCamp Johannesburg, dai pasina kuti 2020 nyika dzepasi rino dzakawirwa nedenda reCOVID 19 zvimwe ndingadayi ndakaenda kuWordCamp Capetown. Zvisinei hazvo kana denda ranani zvimwe ndichakwanisa kufamba ndichienda kumaWordCamp edzimwe nyika.</p>\n<h3>Kukowa zvandakadyara</h3>\n<p>Zvichakadaro, chirongwa changu chekuvandudza hunyanzvi hwangu hachina kumira. Kunyangwe ini ndichiri kukwanisa kubika kodhi muC uye Java, ikozvino, ndasanganisirawo WordPress PHP. Zvaive zvisiri nyore kusvika apa, zvakatora kuzvishingisa nekushanda nesimba. Ndinofara mwari aiva neni pamufambo wangu uyu.</p>\n<p>Muna Mbudzi gore rakapera, ndaive ndichigadzira mawebhusayiti apo nditsvaga basa. Pasina nguva ndakataura na<a href=\"https://zw.linkedin.com/in/trust-nhokovedzo\">Trust Nhokovenzo</a> uyo akaandipa basa mukambani yake, kambani iyi inonzi <a href=\"https://calmlock.co.zw/\">Calmlock Digital Marketing Agency</a>.</p>\n<p>Pane zvimwe zvakawanda kuWordPress zvandisati ndapinda mazviri. Nhaizvozvo kunyangwe ndiri kupedzisa kunyora kwangu apa, nyaya yehupenyu wangu ichaenderera mberi&#8230;</p>\n<p>Kusvikira nguva inotevera &#8230;</p>\n<p><strong>&#8230;. tsvaga chinangwa chako, chiite mushe mushe ..</strong></p>\n<p>The post <a rel=\"nofollow\" href=\"https://heropress.com/essays/hello-world-discovering-the-world-through-wordpress/\">Hello World &#8211; Hevo Nyika</a> appeared first on <a rel=\"nofollow\" href=\"https://heropress.com\">HeroPress</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 23 Sep 2020 06:00:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Thelma Mutete\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:42;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:102:\"WPTavern: WordPress Contributors Debate Dashboard Notice for Upcoming Facebook oEmbed Provider Removal\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105132\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:249:\"https://wptavern.com/wordpress-contributors-debate-dashboard-notice-for-upcoming-facebook-oembed-provider-removal?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-contributors-debate-dashboard-notice-for-upcoming-facebook-oembed-provider-removal\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5885:\"<p>WordPress contributors are discussing different strategies for responding to Facebook and Instagram <a href=\"https://wptavern.com/upcoming-api-change-will-break-facebook-and-instagram-oembed-links-across-the-web-beginning-october-24\">dropping unauthenticated oEmbed support</a>&nbsp;on October&nbsp;24. WordPress will be removing both Facebook and Instagram as oEmbed providers. When a user attempts to embed content by pasting a URL as they have in the past, they may not understand why it no longer works. They may assume that WordPress broke embeds, causing an increase in the support burden for this change.</p>\n\n\n\n<p>A few participants on the <a href=\"https://core.trac.wordpress.org/ticket/50861\">trac ticket</a> for this issue have suggested WordPress detect users who will be impacted and attempt to warn them with a notice.</p>\n\n\n\n<p>&ldquo;Since this may impact users unknowingly, it is possible to push a dashboard notice to users who have Facebook/Instagram embeds in their content, showing for site admins, as a one-off that can be dismissed,&rdquo; Marius Jensen said.</p>\n\n\n\n<p>&ldquo;We&rsquo;ve previously done post-update-processing to clean up comments, so the idea of looking over content for an embed isn&rsquo;t completely outlandish, and would help with those who don&rsquo;t follow WordPress&rsquo; usual channels to learn of this.&rdquo;</p>\n\n\n\n<p>Others don&rsquo;t see the necessity. &ldquo;Why should we make exception here?&rdquo; Milan Dini&#263; said. &ldquo;It&rsquo;s not the first time oEmbed support was discontinued for a provider, and I don&rsquo;t remember anything specific was done then.&rdquo;</p>\n\n\n\n<p>There is still some uncertainty about what will happen with existing oEmbeds after Facebook updates its API. During a recent core developer meeting, Helen Helen Hou-Sand&iacute; confirmed that WordPress does not clear&nbsp;oEmbed&nbsp;caches regularly. &ldquo;Technically&nbsp;oEmbed&nbsp;caches are cleared if you save and a valid response is returned, we do not do cron-based garbage collection,&rdquo; Hou-Sand&iacute; said.</p>\n\n\n\n<p>In a post today on the core development blog, Jake Spurlock assured users and developers that the existing embeds added before Facebook&rsquo;s API change should still work:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Because oEmbed responses are cached in the database using the hidden&nbsp;<code>oembed_cache</code>&nbsp;post type, any embed added prior to the October 24th deadline will be preserved past the deprecation date. These posts are not purged by default in WordPress Core, so the contents of the embed will persist unless manually deleted.</p></blockquote>\n\n\n\n<p>Marius Jensen cautioned that there is still the possibility that existing embeds may not work going, depending on what Facebook does.</p>\n\n\n\n<p>&ldquo;We don&rsquo;t know how they plan on implementing the use of unauthorized embed attempts,&rdquo; Jensen said. &ldquo;It could not return an embed code and your link would remain a plain link, or maybe they decide to return some kind of embedded &lsquo;unauthorized&rsquo; content. I don&rsquo;t think anyone has heard any specifics on how Facebook plans on doing this, so we&rsquo;re all just kinda waiting to either hear more, or see what happens.&rdquo;</p>\n\n\n\n<p>Jensen said WordPress doesn&rsquo;t re-check the cached results except when something changes with the post, but there may be plugins that clean up temporary data that may create an unpredictable outcome.</p>\n\n\n\n<p>&ldquo;The reliability of the caches are hard to determine (and being caches, it&rsquo;s sort of in the term that it&rsquo;s not guaranteed to always be there, but rather fetched and saved for a while when needed),&rdquo; Jensen said.</p>\n\n\n\n<p>Ideally WordPress&rsquo; oEmbed caches will prevent millions of embeds from breaking, but it&rsquo;s still unknown how Facebook and third party plugins could change things.</p>\n\n\n\n<p>Coming off a rocky 5.5 core update that deprecated jQuery Migrate and flooded official support forums with&nbsp;<a href=\"https://wordpress.org/search/5.5?in=support_forums\">reports of broken sites</a>, some contributors are wary of having another situation where users are left in the dark.</p>\n\n\n\n<p>&ldquo;I think a dashboard notice is desirable,&rdquo; Jon Brown said. &ldquo;Otherwise we&rsquo;re not preemptively warning people in a way they can prepare and transition to another solution. We&rsquo;re letting them know the same instant it&rsquo;s going to break (when editing a specific post). I don&rsquo;t think we can safely assume cached data is going to persist forever either, plenty of routines out there purge transient data before its stated expiration date.</p>\n\n\n\n<p>&ldquo;I see this as potentially being similar to the problems seen in dropping JQM. It&rsquo;ll cause <em>avoidable and silent breakage</em> client side without even any error logging for a site developer to pick up on. In hindsight, what ideally would have happened with JQM would have been incorporating the detection code from Enable jQuery Migrate Helper into core temporarily, or simply installing that plugin automatically on behalf of users.&rdquo;</p>\n\n\n\n<p>Brown suggested WordPress detect calls to the cached embeds and warn users before the calls have the chance to fail so they can consider enabling a plugin to keep their embeds working more reliably.</p>\n\n\n\n<p>The discussion remains open in the make.wordpress.org/core <a href=\"https://make.wordpress.org/core/2020/09/22/facebook-and-instagram-embeds-to-be-deprecated-october-24th/\">post</a> and the corresponding <a href=\"https://core.trac.wordpress.org/ticket/50861\">trac ticket</a>. Spurlock said WordPress will likely remove Facebook and Instagram oEmbed providers in the upcoming 5.6 release (scheduled for December 8) but it could also be shipped in a 5.x minor release that happens after October 24. </p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 23 Sep 2020 04:28:56 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:43;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"WPTavern: Gutenberg Hub Launches Landing Page Templates Directory\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105009\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:175:\"https://wptavern.com/gutenberg-hub-launches-landing-page-templates-directory?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-hub-launches-landing-page-templates-directory\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7657:\"<img />\n\n\n\n<p class=\"has-drop-cap\">Munir Kamal has created <a href=\"https://wptavern.com/copy-and-paste-editor-blocks-via-gutenberghubs-block-library\">copy-and-paste blocks</a>. He has built <a href=\"https://wptavern.com/gutenberg-hub-launches-collection-of-100-block-templates\">sections or &ldquo;patterns&rdquo;</a> from those blocks. He has created a plugin that allows users to completely customize the two features via block options. Yesterday, he <a href=\"https://gutenberghub.com/introducing-gutenberg-landing-page-templates/\">released an initial offering</a> of 22 landing page templates that build upon his earlier work.</p>\n\n\n\n<p>Gutenberg Hub can almost be called his <em>magnum opus</em>, at least at this stage of his career. It is a continually growing library of free tools for WordPress&rsquo;s block editor.</p>\n\n\n\n<p>Like previous projects, Gutenberg Hub&rsquo;s landing templates require the <a href=\"https://wptavern.com/control-block-design-via-the-editorplus-wordpress-plugin\">EditorPlus plugin</a>. This plugin is essentially a suite of design controls for the core WordPress blocks. The templates make use of these options by default. Given the limitations of the block editor&rsquo;s current design controls, the use of such a plugin is necessary. Otherwise, there would be few other ways to realistically create a template system like this.</p>\n\n\n\n<p>Currently, users must copy the block code &mdash; via a convenient &ldquo;copy&rdquo; button &mdash; from the Gutenberg Hub website and then paste it in the editor. It is not an ideal situation, and I have been asking Kamal whether he would consider building a template inserter for months now.</p>\n\n\n\n<p>This time around, he preemptively said, &ldquo;And, by the way, I am already working on adding a Template Inserter in my EditorPlus plugin. That will allow users to browse and insert these templates directly from Gutenberg without leaving the website.&rdquo;</p>\n\n\n\n<p>He knew the question was coming. No need for me to ask again. He was unable to share a current screenshot of what the inserter looks like, but he is asking for feedback on what people expect of the user experience and interface.</p>\n\n\n\n<p>&ldquo;Earlier, I created a template inserter similar to other blocks plugins, but later I changed my mind and thought that I should integrate with the Gutenberg Patterns API and load the templates into the &lsquo;patterns&rsquo; panel in the block inserter,&rdquo; he said. &ldquo;But, I am having a few issues and thinking about going back to the original idea to have a Templates button on the top toolbar that opens a popup window to browse and filter templates that users can insert on a click.&rdquo;</p>\n\n\n\n<p>For now, it is still early. However, at least it is on the long-term roadmap and being worked on.</p>\n\n\n\n<h2>The Landing Page Templates</h2>\n\n\n\n<img />Testing the photography template (with minor adjustments).\n\n\n\n<p class=\"has-drop-cap\">At the moment, Gutenberg Hub offers <a href=\"https://gutenberghub.com/template-category/pages/\">22 landing page templates</a>. The &ldquo;page&rdquo; terminology may not mean &ldquo;full page.&rdquo; It simply depends on the active theme. Some themes have an open-canvas type of template that allows users to create the entire page via the editor. However, that is not a common feature, so these page templates will be confined to the post content area in most cases.</p>\n\n\n\n<p>The templates also work better with themes that have at least a full-width or no-sidebar option. End-users will want a lot of breathing room to use the templates and tinker with their designs.</p>\n\n\n\n<p>Kamal has built templates that stretch across a variety of industries. From restaurants to gyms to education to fashion, there is a lot to choose from right now. He promises more are on the way and at least a 23rd template in the next few days.</p>\n\n\n\n<p>&ldquo;For the niches, I did some research from the top WordPress and HTML marketplaces and found the following most common or popular niches,&rdquo; he said. &ldquo;I think I will stick with these niches unless I get some more recommendations.&rdquo;</p>\n\n\n\n<p>In comparison, <a href=\"https://wptavern.com/redux-framework-relaunches-focuses-efforts-on-gutenberg-templates\">Redux Templates</a> offers access to over 1,000 sections and templates. Of course, there are trade-offs, such as some of those being commercial and the plugin typically requiring other third-party plugins. While quantity is not the only thing to look at, it proves there are miles of landscape that Gutenberg Hub&rsquo;s templates have not yet explored. But, it is merely the beginning.</p>\n\n\n\n<p>Gutenberg Hub&rsquo;s full-page templates are not quite as plug-and-play as its blocks and section templates. This is not so much a fault from the developer&rsquo;s end. It is an issue of the platform, which is constantly being updated, and the range of support from current themes. End-users will start seeing some of the current limitations of the system when a layout does not quite look right with one theme but does with another. Or, if their theme has not been updated to support a new feature, such as the Social Links block, the typical horizontal menu design will likely be a normal vertical list of links instead.</p>\n\n\n\n<p>These are not insurmountable issues. Gutenberg and themes need more time to mature before projects like Gutenberg Hub&rsquo;s landing templates are perfect or at least as close to perfect as can be expected.</p>\n\n\n\n<p>There are some things that Gutenberg Hub could improve with its templates. With several that I tested, I needed to switch specific blocks to be full width. This should be set up as the default with templates that are clearly meant to be full width in the example screenshots available on the site. It is a minor issue, but correcting this in the editor fixed several layout issues I was having when using the templates.</p>\n\n\n\n<h2>Monetization Plans</h2>\n\n\n\n<p class=\"has-drop-cap\">The second question that Kamal has not been prepared to answer fully over the past several months is how he will monetize Gutenberg Hub. Eventually, developers need some return on their investment when building tons of free tools. Many would do it all for free as long as their bills somehow got paid, but the reality is that there will come a tipping point where their projects need funding for long-haul maintenance.</p>\n\n\n\n<p>Kamal said he has laid the groundwork for funding but has not finalized anything yet. Currently, he is working on three ideas:</p>\n\n\n\n<ul><li>Creating a pro version of his EditorPlus plugin.</li><li>Offering premium templates and blocks but is looking for a talented designer to work with.</li><li>Using ads specific to Gutenberg users, but he is not a fan of going this route or ads in general.</li></ul>\n\n\n\n<p>He is open to feedback on how to best monetize the website and its projects. However, he said he is unwilling to compromise on giving away current and future free templates and tools.</p>\n\n\n\n<h2>Future Gutenberg Projects</h2>\n\n\n\n<p class=\"has-drop-cap\">Kamal said he does not have any new Gutenberg-related projects in the pipeline. The current plan is to work on what he has already created, which is a large ecosystem of Gutenberg tools that somehow work together.</p>\n\n\n\n<p>Outside of blocks, templates, and plugins, he is beginning to write more free tutorials on the Gutenberg Hub blog and focusing on <a href=\"https://www.youtube.com/GutenbergHub\">creating videos</a> around the project, including a new tutorial <a href=\"https://www.youtube.com/playlist?list=PLfVnkTCddAJ2HMmjw1o12XP7TAEoOV5oE\">series for beginners</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 22 Sep 2020 21:05:19 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:44;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"WPTavern: WordPress Mobile Engineers Propose Dual Licensing Gutenberg under GPL v2.0 and MPL v2.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105025\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:239:\"https://wptavern.com/wordpress-mobile-engineers-propose-dual-licensing-gutenberg-under-gpl-v2-0-and-mpl-v2-0?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-mobile-engineers-propose-dual-licensing-gutenberg-under-gpl-v2-0-and-mpl-v2-0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6556:\"<p>During a Q&amp;A session at WordCamp Europe 2020 online, Matt Mullenweg mentioned that Gutenberg contributors were considering dual licensing for embedding Gutenberg in mobile apps, along with the requirement that they would need to get an agreement from all contributors. WordPress mobile engineer <a href=\"https://bia.is/\">Maxime Biais</a> has just published a <a href=\"https://make.wordpress.org/core/2020/09/21/proposal-dual-licensing-gutenberg-under-gpl-v2-0-and-mpl-v2-0/\">proposal</a> for discussion, recommending dual licensing the editor under GPL v2.0 and MPL v2.0.</p>\n\n\n\n<p>&ldquo;The GPL v2.0 license is a blocker for distributing the Gutenberg library in proprietary mobile apps,&rdquo; Biais said in the corresponding <a href=\"https://github.com/WordPress/gutenberg/issues/23651\">GitHub issue</a>. &ldquo;Currently the only known users of Gutenberg on mobile are the WordPress mobile apps which are under GPL v2.0 (<a href=\"https://github.com/wordpress-mobile/WordPress-Android\">WordPress for Android</a>,&nbsp;<a href=\"https://github.com/wordpress-mobile/WordPress-iOS\">WordPress for iOS</a>). Mobile apps under the GPL v2.0 are not common and this limits Gutenberg usage in many apps.</p>\n\n\n\n<p>&ldquo;Rich text editor libraries in the mobile space are lacking. There is no well known open source rich text editor for Android or iOS. We believe that Gutenberg could be a key library for many mobile apps, but that will never happen with the GPL v2.&rdquo;</p>\n\n\n\n<p>Mobile app developers are limited by the GPL, because it requires the entire app to be distributed under the same license. The team is proposing dual licensing under MPL v2.0, a weaker copyleft license that is often considered to be more &ldquo;business-friendly.&rdquo; It allows users to combine the software with proprietary code. MPL v2.0 requires the source code for any changes to be available under the MPL, ensuring improvements are shared back to the community. The rest of the app can be distributed under any terms with the MPL v2.0 code included as part of a &ldquo;larger work.&rdquo;</p>\n\n\n\n<p>&ldquo;The idea here is to keep some of the WordPress-specific modules under the GPL v2.0 only; some of them are not needed and not relevant for using Gutenberg in another software. Ideally, there would be a different way of bundling the project for being used in WordPress or in a non-GPL software,&rdquo; Biais said.</p>\n\n\n\n<p>The GitHub ticket has several comments from developers who hope to be able to use the editor in their own projects. Radek Pietruszewski, tech lead for a collaborative todo app called&nbsp;<a href=\"https://nozbe.com/\">Nozbe Teams</a>, has been requesting a relicensing of Gutenberg since October 2019.</p>\n\n\n\n<p>&ldquo;Our tech stack is essentially React on web and React Native on iOS and Android,&rdquo; Pietruszewski said. &ldquo;We&rsquo;re a tiny company, and so we share &gt;80% of app&rsquo;s codebase between these 3 platforms.</p>\n\n\n\n<p>&ldquo;Our app sorely lacks a WYSIWYG editor. We had a working implementation on web, but we decided to scrap it, because there was no way to port it on iOS and Android. There are pretty much no viable rich text editors for iOS or Android, yet alone both. But even then, shipping three completely separate, but somehow compatible editors would be a vast amount of work.&rdquo;</p>\n\n\n\n<p>When Peitruszewski originally made his case to the mobile team, he identified Gutenberg/Aztec as a basic infrastructure that has the potential to enable many different apps:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>And that infrastructure is sorely lacking. There are very few rich text editor libraries on both iOS and Android &mdash;&nbsp;and most of them suck. And if you want an editor that has a shared API for both platforms&hellip;&nbsp;you&rsquo;re stuck. There are no options &ndash; Gutenberg is the only game in town (and it&rsquo;s really good).</p><p>And it&rsquo;s very hard to create this infrastructure. WYSIWYG editors are very hard, and it takes entire teams years to develop them (and they still usually suck). Almost no-one has the resources to develop it just for themselves, and if they do, they&rsquo;re unwilling to open-source it.</p></blockquote>\n\n\n\n<p>Automattic&rsquo;s mobile app engineers have <a href=\"https://twitter.com/danroundhill/status/1296941098393190401\">struggled to get regular contributions to the apps</a>, despite them being open source. Dual licensing Gutenberg could open up a new world of contributors with the editor being used more widely across the industry.</p>\n\n\n\n<p>&ldquo;While we might not be big enough to be able to tackle a challenge of developing a rich text editor from scratch, we&rsquo;re big enough to contribute features and bug fixes to open source projects,&rdquo; Pietruszewski said.</p>\n\n\n\n<p>Matt Mullenweg was the first comment on Biais&rsquo; post in favor of the change: </p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>I think&nbsp;Gutenberg&nbsp;has a chance to become a cross-CMS standard, giving users a familiar interface any place they currently have a rich text box. There are hundreds and hundreds of engineers at other companies solving similar problems in a proprietary way, it would be amazing to get them working together but a huge barrier now is supporting Gutenberg in mobile apps, which every modern web service or CMS has. (Hypothetically, think of Mailchimp as a possible consumer and collaborator here, but it could be any company, SaaS, or other&nbsp;open source&nbsp;CMS.)</p></blockquote>\n\n\n\n<p>Unless any major blockers come up in further discussion, this dual licensing change appears to be on track to move forward. Biais noted that a&nbsp;<a href=\"https://github.com/wordpress-mobile/AztecEditor-Android/pull/922\">similar&nbsp;license change has already happened on Aztec-Android</a>&nbsp;and&nbsp;<a href=\"https://github.com/wordpress-mobile/AztecEditor-iOS/issues/1299\">Aztec-iOS</a>. The last hurdle is gaining the approval of all the original code contributors or rewriting the code for those who decline to give approval. </p>\n\n\n\n<p>Once Gutenberg can be used under the MPL v2.0, the editor will gain a broader reach, with people already on deck wanting to use it. Other companies and projects that are normally outside WordPress&rsquo; open source orbit will also have the opportunity to enrich Gutenberg&rsquo;s ecosystem with contributions back to the project. At the same time, the MPL 2.0 protects Gutenberg from companies that would try to re-release the code as a closed-source project.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 21 Sep 2020 22:59:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:45;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:124:\"WPTavern: GitHub to Use ‘Main’ Instead of ‘Master’ as the Default Branch on All New Repositories Starting Next Month\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105014\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:269:\"https://wptavern.com/github-to-use-main-instead-of-master-as-the-default-branch-on-all-new-repositories-starting-next-month?utm_source=rss&utm_medium=rss&utm_campaign=github-to-use-main-instead-of-master-as-the-default-branch-on-all-new-repositories-starting-next-month\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4844:\"<p class=\"has-drop-cap\">In August, GitHub <a href=\"https://github.blog/changelog/2020-08-26-set-the-default-branch-for-newly-created-repositories/\">announced that it would change</a> the &ldquo;master&rdquo; branch name for all new repositories created on the platform to &ldquo;main&rdquo; starting October 1. The date is less than two weeks away, and WordPress developers need to be prepared for the change if they use the service for version control or project management.</p>\n\n\n\n<p>The larger tech and web development community began conversations through various venues in June, a time in which the Black Lives Matter was gaining more traction in the U.S. and worldwide. The discussion centered on removing any terminology that could be discriminatory or oppressive to specific groups of people. This ongoing discussion has shown that there is a deep division over whether such changes are necessary or even helpful.</p>\n\n\n\n<p>The WordPress community is dealing with this division itself. Aaron Jorbin <a href=\"https://make.wordpress.org/core/2020/06/18/proposal-update-all-git-repositories-to-use-main-instead-of-master/\">proposed a change</a> at the same time to rename the default branch name on WordPress-owned repositories. Through discussion on his post and elsewhere, the community landed on &ldquo;trunk,&rdquo; which keeps WordPress projects in line with its SVN roots.</p>\n\n\n\n<p>&ldquo;To close the circle on this, a decision was made in June and earlier today (August 19),&rdquo; <a href=\"https://make.wordpress.org/core/2020/06/18/proposal-update-all-git-repositories-to-use-main-instead-of-master/#comment-39524\">wrote Helen Hou-Sand&iacute;</a>, a lead WordPress developer, in the comments of the original proposal. &ldquo;I updated the default branch name for new GitHub repositories under the WordPress organization to be trunk after GitHub enabled early access to that feature.&rdquo;</p>\n\n\n\n<p>As evidenced by the comments on the <a href=\"https://wptavern.com/proposal-to-rename-the-master-branch-from-wordpress-owned-git-repositories\">Tavern&rsquo;s coverage of the proposal</a> and those on the original post, the WordPress development community as a whole did not support this decision.</p>\n\n\n\n<p>Jorbin has updated several of WordPress&rsquo;s repositories and switched them to use <code>trunk</code> instead of <code>master</code>. However, there are still some lingering projects yet to be updated, including the primary <a href=\"https://github.com/WordPress/WordPress\">WordPress</a> and <a href=\"https://github.com/WordPress/wordpress-develop\">WordPress Develop</a> repositories. He left a <a href=\"https://make.wordpress.org/core/2020/06/18/proposal-update-all-git-repositories-to-use-main-instead-of-master/#comment-38817\">comment with an updated lis</a>t in June. There is no public word on whether the existing, leftover projects will be changed.</p>\n\n\n\n<h2>WordPress Developer Preparations</h2>\n\n\n\n<img />Customizing the default branch for a user&rsquo;s GitHub repositories.\n\n\n\n<p class=\"has-drop-cap\">GitHub is merely changing the default branch name for new repositories starting on October 1. This change does not affect existing repositories. Individual users, organization owners, and enterprise administrators can customize the default branch via their account settings now before the switch is made. Owners can also change the default branch name for individual repositories.</p>\n\n\n\n<p>The biggest thing that developers need to watch out for is their tooling or other integrations that might still require the master branch. There may be cases where an alternative default branch name will break workflows. If planning to use a different branch name, the best thing to do right now is to spin up the tools you use on a test repository. If something breaks, check to see whether the particular tool you are using will be getting an update. In most cases, this should not be a problem because customized default branch names will be an industry standard.</p>\n\n\n\n<p>The great thing about how GitHub is rolling out this feature is that it offers a choice. Those who believe that &ldquo;master&rdquo; is oppressive can change the branch name to something they feel is more inclusive. For those who believe otherwise, they can keep their master branch. But, everyone can use the branch name they prefer.</p>\n\n\n\n<p>For existing repositories, GitHub is asking that developers be patient for now. The company is investing in tools to make this a seamless experience <a href=\"https://github.com/github/renaming#later-this-year\">later this year</a>. There are a few technical hurdles to clear first.</p>\n\n\n\n<p>Developers should read the full GitHub guide on <a href=\"https://docs.github.com/en/github/administering-a-repository/setting-the-default-branch\">setting the default branch</a> for more information.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 21 Sep 2020 20:39:55 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:46;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:125:\"WPTavern: Matt Mullenweg and Jamstack Community Square Off, Making Long-Term Bets on the Predominant Architecture for the Web\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104428\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:293:\"https://wptavern.com/matt-mullenweg-and-jamstack-community-square-off-making-long-term-bets-on-the-predominant-architecture-for-the-web?utm_source=rss&utm_medium=rss&utm_campaign=matt-mullenweg-and-jamstack-community-square-off-making-long-term-bets-on-the-predominant-architecture-for-the-web\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:19953:\"<p>Over the past two weeks, Matt Mullenweg and Jamstack community leaders have forged a new rivalry, after Mullenweg told <a href=\"https://thenewstack.io/wordpress-co-founder-matt-mullenweg-is-not-a-fan-of-jamstack/\">The New Stack</a> that he sees Jamstack as &ldquo;a regression for the vast majority of the people adopting it.&rdquo;  </p>\n\n\n\n<p>&ldquo;The usability and functionality is actually lower,&rdquo; Mullenweg said to Richard MacManus in an email. &ldquo;Even rebuilding sites in Jamstack harkens back to the Movable Type days, where the bigger your site gets the slower it is to rebuild or update templates.&rdquo; </p>\n\n\n\n<p>Mullenweg also described a &ldquo;fragile&rdquo; chain of services required to run Jamstack sites.</p>\n\n\n\n<p>&ldquo;You can patch together a dozen services, each with its own account and billing, for hundreds of dollars a month, to get a similar result you&rsquo;d have for a few dollars a month using WordPress on shared hosting,&rdquo; he said. &ldquo;And it would be more fragile, because the chain is only as strong as its weakest link. You are chaining together different toolsets, logins, billing, hosting&hellip; any part of it going down can break the entire flow.&rdquo;</p>\n\n\n\n<p>Mullenweg has since further <a href=\"https://wptavern.com/matt-mullenweg-clarifies-jamstack-remarks\">clarified his comments</a> while also doubling down on his original premise, saying that &ldquo;there isn&rsquo;t a vast number of people adopting Jamstack in the first place, and those who do are probably fully aware of the tradeoffs.&rdquo; He outlined how he sees WordPress providing a better experience for users in terms of performance, security, scaling, and developer experience.&nbsp;</p>\n\n\n\n<p>Mullenweg&rsquo;s provocative remarks set off a chain of open letters from the CEO&rsquo;s of Jamstack-related services. They are convinced that the LAMP stack is on its way out and that Jamstack is on the precipice of replacing its incumbent as the most dominant architecture of the web. </p>\n\n\n\n<p>Ohad Eder-Pressman, co-founder and CEO of <a href=\"https://www.stackbit.com/\">Stackbit</a>, was the first to fire back. He believes that Jamstack is a &ldquo;disruptive innovation&rdquo; that may appear to be inferior now because it is still relatively low level and new when compared to a 17-year old product like WordPress.</p>\n\n\n\n<p>&ldquo;We should be asking whether Jamstack is a better architecture than LAMP and what gaps currently exist with products and solutions built on top of the Jamstack,&rdquo; Eder-Pressman said. He agreed that Jamstack tools are still largely focused on developers but makes a bold prediction on the stack&rsquo;s future reach:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>The achievements of WordPress in terms of market share and how it democratized early web publishing are amazing. When it comes to architecture I think it was best in class for the early 2000s but it&rsquo;s time to move forward. We already see cohorts of websites where Jamstack adoption crosses 20% &ndash; it&rsquo;s no longer a question of if the Jamstack becomes the predominant architecture for the web but a question of when. The cliche is a cliche but it also rings true &ndash;&nbsp;<strong>First, they ignore you, then they laugh at you (we are here), then you win</strong>.</p></blockquote>\n\n\n\n<p>Eder-Pressman agreed with Mullenweg regarding Jamstack&rsquo;s lower usability and functionality but touted the architecture as &ldquo;infinitely more resilient&rdquo; due to being hosted on a CDN. He admitted that rebuilding larger sites can be slow but cited developments like build parallelization, build cache, partial rebuild, and incremental static regeneration as&nbsp;optimizations as efforts the Jamstack ecosystem&nbsp;is exploring to solve this known issue.</p>\n\n\n\n<p>Netlify&nbsp;CEO Mathias Biilmann, who originally coined the term &ldquo;Jamstack,&rdquo; goes so far as to hail &ldquo;the end of the WordPress era&rdquo; in his <a href=\"https://www.netlify.com/blog/2020/09/15/on-mullenweg-and-the-jamstack-regression-or-future/\">article</a> refuting Mullenweg&rsquo;s remarks. </p>\n\n\n\n<p>&ldquo;There&rsquo;s often a moment right around the time when an old technology is about to be displaced by the next thing, where the main leader in the field goes out and makes a strong argument that absolutely nothing is happening,&rdquo; Biilmann said. &ldquo;A moment that ends up looking like a turning point where the new was undeniably present enough to be worth being in denial about.&rdquo;</p>\n\n\n\n<h2>The Bet: By September 2025, what will be the predominant architecture for the web?</h2>\n\n\n\n<p>In a brief exchange on Twitter, Mullenweg and Eder-Pressman made a wager for five years into the future, to see if Eder-Pressman&rsquo;s prediction will hold up, as measured by the Alexa top 10k. In order for Jamstack to become the predominant architecture for the web, it will need to surpass WordPress&rsquo; numbers, which are currently hovering at <a href=\"https://trends.builtwith.com/cms/WordPress\">39.75%</a> (via BuiltWith) and <a href=\"https://w3techs.com/technologies/details/cm-wordpress\">38.4%</a>&nbsp;(via w3techs).</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">They currently have us ~37% of top 10k. I wonder if you\'re undercounting us with YC companies too? <a href=\"https://t.co/ki9Ng3DGqI\">https://t.co/ki9Ng3DGqI</a></p>&mdash; Matt Mullenweg (@photomatt) <a href=\"https://twitter.com/photomatt/status/1302048647882784769?ref_src=twsrc%5Etfw\">September 5, 2020</a></blockquote>\n</div>\n\n\n\n<p>&ldquo;I&rsquo;m happy to make a long bet: 1 year, 5 years, 10 years,&rdquo; Mullenweg said in another <a href=\"https://twitter.com/photomatt/status/1306368508792504321\">thread</a> in response to Netlify&rsquo;s CEO. &ldquo;We&rsquo;re building and rebuilding WordPress to be generational. We&rsquo;ve navigated and created bigger architectural shifts in the past, and will do so in the future.&rdquo;</p>\n\n\n\n<p>&ldquo;I&rsquo;m a developer, founder, and investor in the space of web technologies &ndash; if I&rsquo;m not willing to engage in a public discussion and share my predictions for where the web is heading then what merit does my work have?&rdquo; Eder-Pressman said when I asked him why he was willing to make this public wager.</p>\n\n\n\n<p>&ldquo;I felt compelled given Mullenweg&rsquo;s comments and what I believe is the lack of appreciation for how much adoption and momentum Jamstack technologies already have. If anything I would say that my bet is actually pretty cautious.&rdquo;</p>\n\n\n\n<p>Eder-Pressman and his team at Stackbit are working on a tool to track Jamstack adoption across the web, as BuiltWith does not yet have a Jamstack stat panel that correctly aggregates all the technologies associated with this relatively new category of websites.</p>\n\n\n\n<p>&ldquo;We&rsquo;ve built an internal tool that tracks adoption of Jamstack technologies across different cohorts of websites which we find informative,&rdquo; he said. &ldquo;This isn&rsquo;t unlike what say Builtwith provides except that we track a few technologies that they don&rsquo;t and we bundle this into a Jamstack adoption indicator. We&rsquo;ve used this internally up until now and are planning to release some public facing version of it later this year.&rdquo;</p>\n\n\n\n<p>As the CEO of Stackbit, a service that cranks out Jamstack sites in 60 seconds while bypassing any requirement to use the command line or download npm packages, Eder-Pressman is actively engaged in trying to bring this technology stack to the masses. The company aims to solve the very problems that Mullenweg identified in his critical comments, as is evident in the marketing copy on the Stackbit website. It acknowledges that piecing together a Jamstack website can be challenging even for developers:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>&ldquo;In a fragmented Jamstack environment, developers struggle to glue products together when trying out the latest tech. Stackbit connects the best tools on the market, and helps them play together.&rdquo;</p></blockquote>\n\n\n\n<p>A year ago, Stackbit caught my attention and I contacted them to find out when WordPress would land among their list of CMS import options. At that time they said they were considering WordPress as a headless CMS option but did not have it on the immediate roadmap. One year later, Stackbit is no closer to building import capabilities for the most popular CMS on the web.</p>\n\n\n\n<p>&ldquo;It&rsquo;s on the horizon but its not something we&rsquo;ve prioritized,&rdquo; Eder-Pressman said. &ldquo;WordPress is a full blown monolithic CMS. It has been used before as a headless CMS but there are better headless CMS choices out there. Even Mullenweg <a href=\"https://twitter.com/photomatt/status/1302028302530404353\">agrees</a> it&rsquo;s a complicated premise.&rdquo;</p>\n\n\n\n<p>When asked if his recent conversations have changed the company&rsquo;s plans to support WordPress imports, he said, &ldquo;No, it doesn&rsquo;t make us want to do this any more or less. I really enjoyed the conversation and am glad that Mullenweg recognizes the rise of the Jamstack so much so that he found it necessary to take aim at it. We as a company are driven by the market, user demand, growth opportunities and a healthy vision for the future of the web.&rdquo;</p>\n\n\n\n<p>Jamstack will need to make itself accessible to the wide world of non-technical website owners if its advocates hope to capture any meaningful segment of the Alexa top 10k marketshare. Stackbit, for one, is still grossly underestimating WordPress&rsquo; ability to sustain its <a href=\"https://joost.blog/cms-market-share-june-2020-analysis/\">phenomenal growth</a>, and doesn&rsquo;t see the necessity for creating a simple path to convert WordPress users. Eder-Pressman believes that making Jamstack accessible starts with developers.</p>\n\n\n\n<p>&ldquo;The Jamstack is an architecture which is winning the minds of developers around the world and across the web development stack,&rdquo; he said. &ldquo;Adoption for new architectures often begins with developers so I&rsquo;m excited to see a company like say Netlify boast over 1 million developers on its Jamstack platform.&rdquo; </p>\n\n\n\n<p>Eder-Pressman&rsquo;s tool for measuring Jamstack adoption will need to produce some compelling data on the stack&rsquo;s growth, if his bet is going to materialize. While nearly every offering in the Jamstack ecosystem still falls squarely within the realm of experienced developers, it doesn&rsquo;t seem likely that five years is enough time for it to overtake WordPress as the predominant architecture for the web. WordPress hasn&rsquo;t achieved its dominance by prioritizing developer happiness over usability.</p>\n\n\n\n<p>Looking at the numbers five years from now, will we see Jamstack overtake WordPress as the most popular way to build a website? Will Jamstack grow with developer usage and then plateau once it fails to reach regular people who don&rsquo;t have a git-based workflow at the top of their wishlists? Are we going to find Jamstack and WordPress neck and neck in the battle for the predominant architecture for the web? Those who work with a hybrid of both technologies see no need for this kind of rivalry.</p>\n\n\n\n<h2>Shifting the conversation towards collaboration: &ldquo;Jamstack can be an opportunity for our industry, rather than a threat.&rdquo;</h2>\n\n\n\n<p>&ldquo;Reading Mullenweg&rsquo;s comments and the responses from CEOs in the Jamstack community make me feel caught in the middle and a bit frustrated,&rdquo; <a href=\"https://www.getshifter.io/\">Shifter</a> COO Daniel Olson said. &ldquo;I see friction between two communities that have so much in common.&rdquo;</p>\n\n\n\n<p>Olson has been a proponent of using Jamstack with WordPress for the past four years since launching Shifter, a static site generator and hosting company that supports headless WordPress sites on the Jamstack. </p>\n\n\n\n<p>&ldquo;If you look for the most secure, cost-effective way to build and host a high-traffic website today, the cross-section you&rsquo;ll arrive at is the Jamstack. Looking at how it offers each of those benefits, you will find inspiration and ways WordPress could do the same,&rdquo; Olson said. &ldquo;Rather than write something off wholesale, see what you can learn and apply it.&rdquo;</p>\n\n\n\n<p>Olson said his mission is to bridge the gaps between WordPress and the benefits Jamstack offers, while working through its early days and messy parts, innovating on the tools that work.</p>\n\n\n\n<p>&ldquo;We should be working together to address specific challenges and worry less about how we get there,&rdquo; Olson said. &ldquo;Some technologies are indeed a better fit for solving each of those challenges but you don&rsquo;t need to leave one ecosystem for the other to do it. You can share knowledge and best practices and discover what&rsquo;s possible. There&rsquo;s a good chance you&rsquo;ll end up creating something new, which is part of that innovation we need in our communities.&rdquo;</p>\n\n\n\n<p>Jamstack hosting services for WordPress are eager to remind users that they don&rsquo;t have to go all in on the technology. You can have your JAM and spread it on top of WordPress, accommodating developers&rsquo; love for experimenting with new frontend technologies, while preserving the dynamic publishing power that has been refined over the past 17 years. These hybrid hosting companies aim to enable this without leaving users behind. </p>\n\n\n\n<p>&ldquo;Matt is absolutely right that the usability and functionality of the Jamstack is lower,&rdquo; <a href=\"https://www.strattic.com/\">Strattic</a> co-founder and CEO Miriam Schwab said. &ldquo;The Jamstack is a great example of technology that is incredibly appealing to developers, but the actual end users &ndash; writers, marketers, business owners &ndash; cannot use it. I&rsquo;ve heard many stories of major companies that have come to the decision to adopt Jamstack for all web development as a company-wide policy, only to find that their marketing team has gone rogue and is installing WordPress sites in order to get their job done.</p>\n\n\n\n<p>&ldquo;The reason for this is like Matt said: every Jamstack site is a compilation of layers of services, and each layer has dozens of options available: you need a static site generator, a CMS, static hosting, and a CDN &ndash; and you need to tie it all together with version control. This is all cool and shiny, and the output is truly fantastic because when you have a site that&rsquo;s a collection of pre-rendered static files served up through a CDN it&rsquo;s fast, secure, scalable and stable. But then along comes marketing and they want to set up a landing page and they are totally dependent on their dev team and can&rsquo;t move forward without them. That defeats the purpose of a CMS-driven website! With WP, you get all the layers in one platform&hellip;but you don&rsquo;t get the awesome output.&rdquo;</p>\n\n\n\n<p>Schwab said she sees WordPress having its age work both for it and against it, but ultimately she believes in enabling real world users to manage their own websites without having to rely on developers. </p>\n\n\n\n<p>&ldquo;I&rsquo;ve seen many companies abandon WP for the shiny new stack, and then come back to it,&rdquo; Schwab said. &ldquo;Github is a good example of this &ndash; yes Github, the modern repository of cutting-edge code moved their blog off of WordPress, and then came back because it truly is the best tool for just getting your content out there. There aren&rsquo;t a zillion steps and integrations &ndash; you write content, click Publish, and that&rsquo;s it. It gets the job done, and the fanciest tools will never beat something that just gets the job done.&rdquo;</p>\n\n\n\n<p>At the same time, WordPress needs to be open to enabling diverse frontend implementations, if it wants to remain relevant for the next decade. &ldquo;WP is running on legacy architecture,&rdquo; Schwab said. &ldquo;It&rsquo;s showing its age, and it&rsquo;s not appealing to new generations of developers. We need to keep WordPress appealing and interesting to developers in order to secure its future for years to come. If we don&rsquo;t make developers excited, we will inevitably see a decline.&rdquo;&nbsp;She encourages the WordPress community to embrace Jamstack as &ldquo;a breath of fresh air.&rdquo; </p>\n\n\n\n<p>&ldquo;Jamstack can be an opportunity for our industry, rather than a threat,&rdquo; Schwab said. &ldquo;There are ways for the two industries to collaborate, like in the case of headless WP deployments using Gatsby.&rdquo;</p>\n\n\n\n<p>Unlike many other Jamstack service companies, the team behind Gatsby has <a href=\"https://wptavern.com/gatsby-raises-15m-plans-to-invest-more-heavily-in-wordpress-and-cms-integrations\">more readily embraced WordPress</a> as a data source and a critical component of its continued success. The company <a href=\"https://wptavern.com/jason-bahl-joins-the-gatsby-team-to-work-on-wpgraphql-full-time\">hired Jason Bahl</a>, creator of the GraphQL for WordPress project, to work on WPGraphQL (and its immediate ecosystem) full-time, while providing a bridge to the WordPress world.</p>\n\n\n\n<p>&ldquo;Maybe I&rsquo;m getting caught up in semantics, but the JAM in JAMStack means JavaScript, APIs and Markup,&rdquo; Bahl said. &ldquo;It wasn&rsquo;t long ago when Matt prescribed the WordPress ecosystem to &lsquo;Learn JavaScript Deeply,&rsquo; and not long after that when a Jamstack application called Gutenberg was merged into WordPress core, along with React. Gutenberg is the JavaScript, the WP REST API is the API and the end result is markup. Jamstack isn&rsquo;t a regression, it&rsquo;s a future that Automattic is helping drive WordPress toward.&rdquo;</p>\n\n\n\n<p>When Mullenweg says he is ready to build and rebuild WordPress to be generational, it&rsquo;s a promise he has already delivered on by introducing the React-based Gutenberg editor two years ago, successfully pushing past an enormous amount of resistance from the developer community.</p>\n\n\n\n<p>Bahl said he sees this continued legacy of improvement happening over and over again in various ways, made possible by WordPress&rsquo; pluggable system:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>WordPress ships with a lot of APIs, but often they are replaced with something newer and better. For example, it&rsquo;s common for sites to offload images to a CDN instead of use the built-in file system for media. Or instead of using built-in WordPress MySQL search, users will reach for ElasticSearch, Algolia or Solr. In the case of WordPress and the JAMStack, reaching for Next, Gatsby or Gridsome to replace the built-in Theme API isn&rsquo;t a regression, it&rsquo;s using newer technology to handle things that built-in parts of WordPress might not do as well. The Theme API of WordPress is just one API and replacing it with technology that does the job better isn&rsquo;t a regression.</p></blockquote>\n\n\n\n<p>Gatsby&rsquo;s build step, which has received <a href=\"https://twitter.com/tesseralis/status/1293649015020457984\">negative attention in the news</a> recently, is one example of what Bahl thinks Mullenweg was referring to as a regression for users. Bahl is working with Gatsby to reduce the friction associated with decoupled architectures when using WordPress as the API in Jamstack.</p>\n\n\n\n<p>&ldquo;I don&rsquo;t see Jamstack competing against WordPress,&rdquo; Bahl said. &ldquo;In my mind, Jamstack with WordPress as the API is the future of the web. WordPress is the best CMS. Gatsby specifically is trying to embrace this. This isn&rsquo;t a zero sum game. If the Gatsby + WordPress experience can allow users to use the best CMS in the world while using modern dev tooling, it&rsquo;s a win all around.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 19 Sep 2020 18:54:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:47;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:51:\"WPTavern: Matt Mullenweg Clarifies Jamstack Remarks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104883\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:147:\"https://wptavern.com/matt-mullenweg-clarifies-jamstack-remarks?utm_source=rss&utm_medium=rss&utm_campaign=matt-mullenweg-clarifies-jamstack-remarks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6205:\"<p>Two weeks ago, Matt Mullenweg made some pointed remarks in an article from <a href=\"https://thenewstack.io/wordpress-co-founder-matt-mullenweg-is-not-a-fan-of-jamstack/\">The New Stack</a>, calling Jamstack &ldquo;a regression for the vast majority of the people adopting it.&rdquo; In preparation for an upcoming article that will include comments from leaders across both the WordPress and Jamstack communities, I asked Mullenweg if he stands by his remarks characterizing Jamstack as a regression. His response was lengthy and is printed here in its entirety to preserve cohesion.</p>\n\n\n\n<p><strong>Q: Do you stand by your remarks that Jamstack is a regression for the vast majority of the people adopting it?</strong></p>\n\n\n\n<p><strong>Answer:</strong></p>\n\n\n\n<p>&ldquo;Vast majority of people adopting it&rdquo; was probably too harsh, because there isn&rsquo;t a vast number of people adopting Jamstack in the first place, and those who do are probably fully aware of the tradeoffs. There are some good reasons, for certain situations, to decouple and add complexity to your architecture, and WordPress&rsquo; REST API works fantastically as a backend there. But I worry they are over-selling the promise of what&rsquo;s really an architectural decision. If&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://jamstack.org/\">you look at the benefits they purport</a>,&nbsp;it&rsquo;s better performance, security, scaling, and developer experience:</p>\n\n\n\n<img />\n\n\n\n<p><strong>Better Performance:</strong> You can achieve the same performance by putting a great CDN like Cloudflare on top of WordPress, and your life will be infinitely easier when you want to add dynamic features like a store or comments. You can also easily find a static WordPress host like&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://www.strattic.com/\">Strattic</a>&nbsp;or&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://www.getshifter.io/\">Shifter</a>.</p>\n\n\n\n<p><strong>Higher security:</strong> I don&rsquo;t believe that introducing a number of proprietary and sub-scale SaaS services like Netlify into your stack will make your site more secure. I believe the most secure thing you can do is run fully open source code, as widely vetted and used as possible, on servers you control, or from the fewest number of vendors possible. WordPress securely runs some of the most attacked websites on the internet, including major media, Facebook, and&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"http://whitehouse.gov/\">WhiteHouse.gov</a>. Having this many moving parts doesn&rsquo;t inspire confidence:</p>\n\n\n\n<img />\n\n\n\n<p><strong>Cheaper, easier scaling:</strong> CDNs are more expensive than normal hosting accounts, and you can get WordPress running on a decent host for less than $5/mo. And there are even more powerful offerings: The personal plan on&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"http://wp.com/\">WP.com</a>&nbsp;can serve tens of millions of visitors per day, to the website or the headless API, includes a global CDN, and a domain name for $4/mo, and we still have a profit margin.&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://graphcms.com/pricing\">GraphCMS starts at $29/mo and only gives you &ldquo;5,000 entities,&rdquo;</a> whatever that means.&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://www.contentstack.com/pricing\">Contentstack is $3,500/mo</a>. And that&rsquo;s just for the headless CMS part! You still need to sign up and pay for a bunch of the other stuff in that graphic before you have a website a human can visit in a browser.</p>\n\n\n\n<p><strong>Better developer experience:</strong> If your developer wants to copy and paste updates from marketing to the website, sure, but if they want people to be able to update the website without their help, they should go with something easier for users like WordPress. If you&rsquo;re curious about the developer experience, or an investor thinking about this space, I really suggest you watch this three hour and thirty minute tutorial to really understand what is being sold under the premise of &ldquo;better&rdquo;:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<p>Have I ever built stuff like that? Totally! It can be a ton of fun, like building a rocket at home or fixing up an old car. I&rsquo;ve seen some awesome sites built on decoupled architectures or static publishing, using headless WordPress rather than the CMS&rsquo;s above, but still a similar idea. People are trying to paint me as being against Jamstack, but that is as foreign to me as being against duct tape &mdash; it&rsquo;s good for some things, bad for others, and it&rsquo;s not going away. I just wish they would be more intellectually rigorous and honest when marketing it. I expect a Jamstack-like approach to exist forever, just like the ideas behind Jamstack pre-date it getting jammed down our throats by Netlify&rsquo;s marketing team.</p>\n\n\n\n<p>Biilmann has got the Ballmer / iPhone story backwards &mdash;&nbsp;Microsoft&rsquo;s mistake there was they made something too complicated, and the iPhone simplified it. Jamstack introduces numerous vendors, build steps, network calls, interfaces, even billing relationships for something that&rsquo;s a single button press in WordPress.</p>\n\n\n\n<p>The reason services like&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"http://wordpress.com/\">WordPress.com</a>&nbsp;and Shopify are growing so much is they are taking things that were complicated and making them simpler and accessible to a much wider audience. My mission is to democratize publishing and commerce, to make it radically accessible to everyone regardless of technical or economic ability, and increase the freedom and openness on the internet.&nbsp;<a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://twitter.com/photomatt/status/1306368508792504321\">As I said on Twitter</a>, the first 15 years of WordPress were just the first few chapters. I&rsquo;m looking forward to building and rebuilding the platform the rest of my lifetime, and when that comes to an end I hope future generations will carry the torch.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 18 Sep 2020 22:49:44 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:48;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"WPTavern: Gutenberg’s Custom Spacing Should Be Theme Controlled\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104867\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:169:\"https://wptavern.com/gutenbergs-custom-spacing-should-be-theme-controlled?utm_source=rss&utm_medium=rss&utm_campaign=gutenbergs-custom-spacing-should-be-theme-controlled\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5679:\"<img />Adjusting padding on a Group block.\n\n\n\n<p class=\"has-drop-cap\">When <a href=\"https://wptavern.com/gutenberg-9-0-brings-major-improvements-to-navigation-screen-and-query-block\">Gutenberg 9.0 landed</a> earlier this week, it came with an experimental <a href=\"https://github.com/WordPress/gutenberg/pull/24966\">padding control</a> for the Group block. Most users will not see it unless their theme has opted into supporting the feature using the <code>experimental-custom-spacing</code> flag.</p>\n\n\n\n<p>This was not the first that we have seen of the padding option on a block. <a href=\"https://wptavern.com/gutenberg-8-3-updates-block-categories-includes-parent-block-selector-and-adds-new-design-controls\">Gutenberg 8.3</a> introduced it for the Cover block. Since then, nothing has changed with the implementation.</p>\n\n\n\n<p>The problem with the custom spacing/padding option is that it creates an inline style that does not adjust based on the design of the theme. Fortunately, the feature is still experimental. This means that we have time to reevaluate how it works.</p>\n\n\n\n<p>Unless we&rsquo;re doing away with any remaining illusion that themes will play an important aspect of WordPress&rsquo;s future and front-end design becomes fully entrenched within core, theme authors need some level of control. And, even if themes are going the way of the dinosaur, custom padding numbers on the block level will create design consistency issues down the road. Using 100 pixels of padding might make sense within a site&rsquo;s current design, but 96 pixels might make sense within a future design. When a user adds dozens or hundreds of blocks with custom padding today, it will wreak havoc on tomorrow&rsquo;s spacing and rhythm.</p>\n\n\n\n<p>Besides that, the average user has little concept of design rules. Having a standardized system for spacing would give theme authors control over the output while giving end-users the ability to customize the look.</p>\n\n\n\n<p>I have argued that WordPress needs some sort of <a href=\"https://wptavern.com/themes-of-the-future-a-design-framework-and-a-master-theme\">design framework</a>. For example, Tailwind CSS has specific padding classes. So does Bootstrap and nearly every other CSS framework. The web development community has been down this road. It is a well-trodden path, and WordPress is not innovating by using inline styles.</p>\n\n\n\n<p>If the WordPress platform is going to put this sort of power into the hands of its users, it should do so in a way that allows designers to do their thing and not push users toward semi-permanent, inline-style soup in their content.</p>\n\n\n\n<p>Pre-Gutenberg, I would have been entirely against the idea of WordPress introducing any sort of CSS or design framework. However, the platform is consistently moving toward becoming a UI-based design tool rather than simply a way to manage content. Users will have design-related options on a global scale all the way down to individual blocks. Users should absolutely have the ability to adjust a block&rsquo;s padding in such a system. They should not need an understanding of CSS to do so. Instead, for most use cases, users should be able to adjust padding based on whether they want larger or smaller spacing, not specific CSS values.</p>\n\n\n\n<p>I propose a full set of standardized padding classes. The same would go for margins or other design-related options down the road. Gutenberg/WordPress should create a set of default values for these classes, which theme authors could override based on their design.</p>\n\n\n\n<p>This is not a new concept. Dave Smith, a developer for Automattic, introduced a <a href=\"https://github.com/WordPress/gutenberg/pull/16730\">patch in 2019</a> that used named selectors for spacing on the Group block. He gave the following reasoning for choosing this approach over absolute values:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Imagine you are a Theme designer. You craft your CSS with spacing that is perfect for the design. You want to ensure that is consistent throughout your Theme, even if the page layout is being created by the end-user in the Block Editor.</p><p>With the approach I&rsquo;ve taken here, when a size is selected only classes are added to the Block in the DOM. This affords the Theme creator the opportunity to provide custom sizes in CSS that are suitable for their Theme. If they opt not to do this then sensible defaults are provided.</p><p>With the pixels approach, we&rsquo;re locking users of the Block into absolute values and asking them to make a lot of decisions that they&rsquo;d probably prefer not to have to make. It could also lead to an inconsistent visual experience.</p></blockquote>\n\n\n\n<p>This ship has already sailed and sunk with custom colors and font sizes. Gutenberg had an opportunity to standardize class names for these options but left it to theme authors. As a result, there is no standard across the theme market, which means that choosing the &ldquo;large&rdquo; font size or the &ldquo;blue&rdquo; text color provided by the theme will likely not carry across to the user&rsquo;s next theme. Now, we are on the cusp of far more design-related options as WordPress moves toward full-site editing. It is time to consider some standards on design-related class names and provide a framework that all themes can use.</p>\n\n\n\n<p>Gutenberg could still provide a <em>custom</em> padding option just like it does for colors and font sizes. Users who choose to go this route would be making an explicit choice to work outside of the standard. But, let&rsquo;s not go down this road of allowing users to set absolute spacing values as the default option.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 18 Sep 2020 18:49:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:49;a:6:{s:4:\"data\";s:13:\"\n	\n	\n	\n	\n	\n	\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"WPTavern: GoDaddy Acquires SkyVerge, Creator of Over 60 WooCommerce Add-Ons\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104658\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:193:\"https://wptavern.com/godaddy-acquires-skyverge-creator-of-over-60-woocommerce-add-ons?utm_source=rss&utm_medium=rss&utm_campaign=godaddy-acquires-skyverge-creator-of-over-60-woocommerce-add-ons\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4911:\"<p class=\"has-drop-cap\">On September 14, GoDaddy <a href=\"https://aboutus.godaddy.net/newsroom/news-releases/press-release-details/2020/GoDaddy-Acquires-SkyVerge-to-Help-Everyday-Entrepreneurs-Sell-Online-with-WordPress-and-WooCommerce/default.aspx\">announced it had acquired SkyVerge</a>, a major WooCommerce-focused development company, for an undisclosed amount. At the moment, GoDaddy is playing it close to the vest in terms of its future plans. It has not publicly announced anything beyond a continued commitment to current customers.</p>\n\n\n\n<p>The initial announcement makes note that SkyVerge&rsquo;s free plugins on WordPress.org have been downloaded more than 3.1 million times. However, the company&rsquo;s <a href=\"https://profiles.wordpress.org/skyverge/#content-plugins\">nine plugins in the directory</a> currently have over 155,000 active installs. Nevertheless, SkyVerge&rsquo;s real value is in its team and its impressive array of free and commercial add-on plugins available directly from its site.</p>\n\n\n\n<p>WooCommerce is a cash cow for companies with the right products and marketing at the moment. GoDaddy seems to be going all-in on the back of WordPress&rsquo;s most popular eCommerce solution. It launched a <a href=\"https://wptavern.com/godaddy-launches-ecommerce-hosting-plan-in-partnership-with-woocommerce\">managed WooCommerce hosting plan</a> in October 2019. The hosting company has now added over 60 WooCommerce extensions to its inventory in one swoop.</p>\n\n\n\n<p>&ldquo;As more small businesses and entrepreneurs go online, having a highly performant eCommerce experience is becoming more important than ever,&rdquo; said Rich Tabor, Senior Product Manager of WordPress Experience at GoDaddy. &ldquo;Late last year we launched a Managed WooCommerce offering, bundling many WooCommerce extensions in the Managed WordPress environment.&rdquo;</p>\n\n\n\n<p>SkyVerge has quietly become a massively successful WordPress and WooCommerce business. It was bringing in <a href=\"https://www.starterstory.com/develop-ecommerce-tools\">$350,000 per month</a> at the end of 2019. There was no response on how well the business has performed thus far in 2020.</p>\n\n\n\n<p>The entire SkyVerge team came along for the transition to GoDaddy. &ldquo;We&rsquo;re just beginning to deliver more capabilities and an even better setup and ongoing usage experience for our customers,&rdquo; said Tabor. &ldquo;The SkyVerge team will lead and accelerate those plans. They are an incredibly talented and innovative team that lives and breathes WooCommerce. Joining forces with them advances GoDaddy&rsquo;s WordPress strategy and enhances our ability to deliver intuitive eCommerce experiences that help everyday entrepreneurs sell online.&rdquo;</p>\n\n\n\n<p>With so many extensions in place, the big question for average users is whether those extensions will become a part of GoDaddy&rsquo;s eCommerce hosting bundle. Tabor either did not or could not let slip any plans in the works. &ldquo;We&rsquo;re just beginning to determine how to best deliver SkyVerge&rsquo;s wonderful products to GoDaddy customers. SkyVerge brings a lot of great software. It&rsquo;s reasonable to expect we&rsquo;ll be delivering that to our customers who are selling online.&rdquo;</p>\n\n\n\n<p>It is doubtful that GoDaddy went into this acquisition without at least some short-term plans or visions for how its managed hosting service would use these extensions. For now, we will have to wait and see.</p>\n\n\n\n<p>It seems that the immediate plan will be to maintain business as usual. Tabor said GoDaddy had no changes to announce related to SkyVerge&rsquo;s products and website. &ldquo;We are committed to continuing support of SkyVerge&rsquo;s customers and investing in the SkyVerge software,&rdquo; he said.</p>\n\n\n\n<p>SkyVerge also created <a href=\"https://jilt.com/\">Jilt</a>, which is an email marketing platform for eCommerce sites. The platform currently supports WooCommerce, Easy Digital Downloads, Shopify, and Shopify Plus. Tabor did not directly respond to what the future looked like for Jilt&rsquo;s non-WooCommerce customers nor did he give any indication of whether there were plans to expand Jilt to other eCommerce systems.</p>\n\n\n\n<p>He did say that GoDaddy would continue to invest in its priority eCommerce platforms, which are WooCommerce and GoDaddy Websites + Marketing.</p>\n\n\n\n<p>Max Rice, co-founder of SkyVerge, did leave some indication of Jilt&rsquo;s future in his <a href=\"https://www.skyverge.com/blog/skyverge-joins-godaddy/\">announcement post</a>. &ldquo;We made a commitment to be there for your business with software you can depend on, and we&rsquo;re sticking to it,&rdquo; he said. &ldquo;We&rsquo;ll continue to support our existing WooCommerce plugins and Jilt. While we&rsquo;ll be building something new at GoDaddy, everything we&rsquo;ve already built is a big part of that.&rdquo;</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 17 Sep 2020 20:59:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Wed, 21 Oct 2020 17:17:21 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Wed, 21 Oct 2020 17:00:08 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 2\";s:16:\"content-encoding\";s:4:\"gzip\";}}s:5:\"build\";s:14:\"20200723144942\";}', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(1163, '_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1603343841', 'no'),
(1164, '_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1603300641', 'no'),
(1165, '_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b', '1603343841', 'no'),
(1166, '_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b', '<div class=\"rss-widget\"><ul><li><a class=\'rsswidget\' href=\'https://wordpress.org/news/2020/10/wordpress-5-6-beta-1/\'>WordPress 5.6 Beta 1</a></li></ul></div><div class=\"rss-widget\"><ul><li><a class=\'rsswidget\' href=\'https://wordpress.org/news/2020/10/wordpress-5-6-beta-1/\'>WordPress.org blog: WordPress 5.6 Beta 1</a></li><li><a class=\'rsswidget\' href=\'https://wptavern.com/wordpress-5-6-release-team-pulls-the-plug-on-block-based-widgets?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=wordpress-5-6-release-team-pulls-the-plug-on-block-based-widgets\'>WPTavern: WordPress 5.6 Release Team Pulls the Plug on Block-Based Widgets</a></li><li><a class=\'rsswidget\' href=\'https://wptavern.com/woocommerce-tests-new-instagram-shopping-checkout-feature-now-in-closed-beta?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=woocommerce-tests-new-instagram-shopping-checkout-feature-now-in-closed-beta\'>WPTavern: WooCommerce Tests New Instagram Shopping Checkout Feature, Now in Closed Beta</a></li></ul></div>', 'no'),
(1168, '_site_transient_update_themes', 'O:8:\"stdClass\":4:{s:12:\"last_checked\";i:1605054094;s:7:\"checked\";a:11:{s:5:\"astra\";s:5:\"2.4.5\";s:12:\"bfastmag_pro\";s:5:\"2.7.0\";s:13:\"education-hub\";s:5:\"2.2.3\";s:14:\"education-soul\";s:5:\"1.0.6\";s:8:\"edupress\";s:5:\"1.4.1\";s:15:\"hello-elementor\";s:5:\"2.3.0\";s:7:\"oceanwp\";s:5:\"1.8.6\";s:22:\"page-builder-framework\";s:5:\"2.5.1\";s:14:\"twentynineteen\";s:3:\"1.5\";s:15:\"twentyseventeen\";s:3:\"2.3\";s:12:\"twentytwenty\";s:3:\"1.2\";}s:8:\"response\";a:9:{s:5:\"astra\";a:6:{s:5:\"theme\";s:5:\"astra\";s:11:\"new_version\";s:5:\"2.6.0\";s:3:\"url\";s:35:\"https://wordpress.org/themes/astra/\";s:7:\"package\";s:53:\"https://downloads.wordpress.org/theme/astra.2.6.0.zip\";s:8:\"requires\";s:3:\"5.3\";s:12:\"requires_php\";s:3:\"5.3\";}s:13:\"education-hub\";a:6:{s:5:\"theme\";s:13:\"education-hub\";s:11:\"new_version\";s:5:\"2.2.4\";s:3:\"url\";s:43:\"https://wordpress.org/themes/education-hub/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/education-hub.2.2.4.zip\";s:8:\"requires\";s:3:\"5.1\";s:12:\"requires_php\";s:3:\"5.6\";}s:14:\"education-soul\";a:6:{s:5:\"theme\";s:14:\"education-soul\";s:11:\"new_version\";s:5:\"1.0.7\";s:3:\"url\";s:44:\"https://wordpress.org/themes/education-soul/\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/theme/education-soul.1.0.7.zip\";s:8:\"requires\";s:3:\"5.1\";s:12:\"requires_php\";s:3:\"5.6\";}s:8:\"edupress\";a:6:{s:5:\"theme\";s:8:\"edupress\";s:11:\"new_version\";s:5:\"1.5.1\";s:3:\"url\";s:38:\"https://wordpress.org/themes/edupress/\";s:7:\"package\";s:56:\"https://downloads.wordpress.org/theme/edupress.1.5.1.zip\";s:8:\"requires\";b:0;s:12:\"requires_php\";s:3:\"7.0\";}s:7:\"oceanwp\";a:6:{s:5:\"theme\";s:7:\"oceanwp\";s:11:\"new_version\";s:5:\"1.9.0\";s:3:\"url\";s:37:\"https://wordpress.org/themes/oceanwp/\";s:7:\"package\";s:55:\"https://downloads.wordpress.org/theme/oceanwp.1.9.0.zip\";s:8:\"requires\";s:3:\"5.3\";s:12:\"requires_php\";s:3:\"7.2\";}s:22:\"page-builder-framework\";a:6:{s:5:\"theme\";s:22:\"page-builder-framework\";s:11:\"new_version\";s:5:\"2.5.9\";s:3:\"url\";s:52:\"https://wordpress.org/themes/page-builder-framework/\";s:7:\"package\";s:70:\"https://downloads.wordpress.org/theme/page-builder-framework.2.5.9.zip\";s:8:\"requires\";b:0;s:12:\"requires_php\";s:3:\"5.6\";}s:14:\"twentynineteen\";a:6:{s:5:\"theme\";s:14:\"twentynineteen\";s:11:\"new_version\";s:3:\"1.7\";s:3:\"url\";s:44:\"https://wordpress.org/themes/twentynineteen/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/theme/twentynineteen.1.7.zip\";s:8:\"requires\";s:5:\"4.9.6\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:15:\"twentyseventeen\";a:6:{s:5:\"theme\";s:15:\"twentyseventeen\";s:11:\"new_version\";s:3:\"2.4\";s:3:\"url\";s:45:\"https://wordpress.org/themes/twentyseventeen/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/theme/twentyseventeen.2.4.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}s:12:\"twentytwenty\";a:6:{s:5:\"theme\";s:12:\"twentytwenty\";s:11:\"new_version\";s:3:\"1.5\";s:3:\"url\";s:42:\"https://wordpress.org/themes/twentytwenty/\";s:7:\"package\";s:58:\"https://downloads.wordpress.org/theme/twentytwenty.1.5.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}}s:12:\"translations\";a:0:{}}', 'no'),
(1170, 'theme_mods_hello-elementor', 'a:5:{i:0;b:0;s:18:\"nav_menu_locations\";a:1:{s:6:\"menu-1\";i:2;}s:18:\"custom_css_post_id\";i:-1;s:11:\"custom_logo\";i:108;s:16:\"sidebars_widgets\";a:2:{s:4:\"time\";i:1603301144;s:4:\"data\";a:2:{s:19:\"wp_inactive_widgets\";a:6:{i:0;s:10:\"archives-2\";i:1;s:6:\"meta-2\";i:2;s:8:\"search-2\";i:3;s:12:\"categories-2\";i:4;s:14:\"recent-posts-2\";i:5;s:17:\"recent-comments-2\";}s:18:\"smartslider_area_1\";a:0:{}}}}', 'yes'),
(1171, 'elementor_pro_theme_builder_conditions', 'a:0:{}', 'yes'),
(1173, '_transient_is_multi_author', '0', 'yes'),
(1174, '_site_transient_timeout_elementor_pro_remote_info_api_data_3.0.5', '1605097225', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(1175, '_site_transient_elementor_pro_remote_info_api_data_3.0.5', 'a:16:{s:14:\"stable_version\";s:5:\"3.0.6\";s:12:\"last_updated\";s:19:\"2020-11-04 14:36:18\";s:8:\"sections\";s:109799:\"a:2:{s:11:\"description\";s:161:\"Elementor Pro adds new features to the Elementor Page Builder plugin. Control your conversions, your user engagement, your entire website, from one page builder.\";s:9:\"changelog\";s:109576:\"<h4>3.0.6 - 2020-11-04</h4>\n<ul>\n<li>Tweak: Updated the embedded post in Facebook Embed widget</li>\n<li>Fix: Minor UI glitches in Theme Builder\'s conditions screen footer</li>\n<li>Fix: Template type changes into Single Page after conditions change in Theme Builder</li>\n<li>Fix: Redundant Custom Caption option in Site Logo widget</li>\n<li>Fix: Removed unused code in Drip integration</li>\n<li>Fix: Removed Weibo and WeChat social networks due to website and links inactivity from Share Buttons widget</li>\n<li>Fix: Removed redundant code from Portfolio and Post Navigation widgets</li>\n</ul>\n<h4>3.0.5 - 2020-09-23</h4>\n<ul>\n<li>Fix: If the default page layout is set to &quot;Canvas&quot; Headers and Footers cannot be edited</li>\n<li>Fix: Product Image Dynamic Tag throws an error when no image is set</li>\n<li>Fix: Missing Single document placeholder in Theme Builder</li>\n<li>Fix: Document editing handles inherit the <code>font-family</code> from 3rd party source</li>\n<li>Fix: Can\'t add linebreaks to Textarea input when used as Multi Step Form</li>\n<li>Fix: Incorrect width in Facebook Page widget</li>\n<li>Fix: Added compatibility to allow the use of \'get_create_url\' in Theme Builder</li>\n</ul>\n<h4>3.0.4 - 2020-09-09</h4>\n<ul>\n<li>Fix: Autogenerated screenshots appear in WP Media Library modal (<a href=\"https://github.com/elementor/elementor/issues/12304\">#12304</a>)</li>\n<li>Fix: Make sure Elementor Posts widget Pagination doesn\'t interfere with 3rd party plugins (<a href=\"https://github.com/elementor/elementor/issues/12126\">#12126</a>, <a href=\"https://github.com/elementor/elementor/issues/12127\">#12127</a>)</li>\n<li>Fix: Shrinking conditions indicator in Theme Builder</li>\n<li>Fix: Column can\'t be dragged and dropped if it populates a Global widget</li>\n<li>Fix: Styles are missing from Single templates in some edge cases</li>\n</ul>\n<h4>3.0.3 - 2020-09-02</h4>\n<ul>\n<li>Fix: Pagination doesn\'t work in WordPress 5.5 (<a href=\"https://github.com/elementor/elementor/issues/12126\">#12126</a>, <a href=\"https://github.com/elementor/elementor/issues/12127\">#12127</a>)</li>\n<li>Fix: Change delete template action to &quot;Move to Trash&quot; in the new Theme Builder view</li>\n</ul>\n<h4>3.0.2 - 2020-08-31</h4>\n<ul>\n<li>Tweak: Replaced WordPress &quot;Learn More&quot; links with dynamic links for better control over time (<a href=\"https://github.com/elementor/elementor/issues/12312\">#12312</a>)</li>\n<li>Tweak: UI tweaks to the Conditions screen In the new Theme Builder</li>\n<li>Fix: Motion Effects not working when assigned to a column and throws JS error when DOM optimization is disabled (<a href=\"https://github.com/elementor/elementor/issues/12299\">#12299</a>, <a href=\"https://github.com/elementor/elementor/issues/12275\">#12275</a>)</li>\n<li>Fix: Multiple Galleries display all the images in the Lightbox slideshow (<a href=\"https://github.com/elementor/elementor/issues/11809\">#11809</a>)</li>\n<li>Fix: Old Theme Builder is being opened when accessing through the Finder</li>\n<li>Fix: Mixed templates import glitch in Theme Builder</li>\n<li>Fix: Card icon sizes in Theme Builder</li>\n<li>Fix: Preview button leads to <code>render_mode</code> instead of preview when importing a template from the new Theme Builder</li>\n</ul>\n<h4>3.0.1 - 2020-08-26</h4>\n<ul>\n<li>Tweak: Keep previous Theme Builder when accessing from the WP Dashboard for legacy support</li>\n<li>Tweak: Updated video tutorials in Theme Builder</li>\n<li>Tweak: Don\'t show auto-screenshots in the Media Library (Props <a href=\"https://github.com/black-eye\">@black-eye</a>)</li>\n<li>Fix: Repeater items throws <code>childView</code> is undefined message in Forms widget (<a href=\"https://github.com/elementor/elementor/issues/12239\">#12239</a>, <a href=\"https://github.com/elementor/elementor/issues/12221\">#12221</a>)</li>\n<li>Fix: Misspelling of the word &quot;occurred&quot; in Form widget default error message (<a href=\"https://github.com/elementor/elementor/issues/12137\">#12137</a>)</li>\n<li>Fix: Facebook comments not showing up (<a href=\"https://github.com/elementor/elementor/issues/12157\">#12157</a>)</li>\n<li>Fix: Check for conflicts in Theme Builder doesn\'t work properly</li>\n<li>Fix: Minor UI fixes in Theme Builder</li>\n<li>Fix: Dark mode glitches in Theme Builder</li>\n<li>Fix: Global Site Part toaster appears when you publish a Popup</li>\n<li>Fix: Site Parts aren\'t in the correct order in Theme Builder</li>\n<li>Fix: Date field caused forms to get corrupted in Forms widget</li>\n<li>Fix: Theme Builder application page is forbidden</li>\n</ul>\n<h4>3.0.0 - 2020-08-23</h4>\n<ul>\n<li>New: Introducing the new and improved Theme Builder</li>\n<li>Tweak: Removed <code>.elementor-inner</code> and <code>.elementor-column-wrap</code> from DOM output to improve performance (<a href=\"https://github.com/elementor/elementor/issues/7351\">#7351</a>, <a href=\"https://github.com/elementor/elementor/issues/7817\">#7817</a>, <a href=\"https://developers.elementor.com/dom-improvements-ahead-html-wrappers-removal-from-v3-0/\">Developers Blog Post</a>)</li>\n<li>Tweak: Added contextual anchors ID support to Table of Contents widgets (<a href=\"https://github.com/elementor/elementor/issues/10052\">#10052</a>)</li>\n<li>Tweak: Added WeChat and Weibo social networks to Share Buttons widget (<a href=\"https://github.com/elementor/elementor/issues/11554\">#11554</a>)</li>\n<li>Tweak: Added Dynamic capabilities for Redirect after Login/Logout in Login widget (<a href=\"https://github.com/elementor/elementor/issues/11343\">#11343</a>)</li>\n<li>Tweak: Added Blend Mode and CSS Filters controls to adjust the Background Overlay in Flipbox widget (<a href=\"https://github.com/elementor/elementor/issues/11653\">#11653</a>)</li>\n<li>Tweak: Added responsive capabilities to Toggle Button styling in Nav Menu widget (<a href=\"https://github.com/elementor/elementor/issues/8269\">#8269</a>)</li>\n<li>Tweak: Added responsive Text Alignment control in Call to Action widget (<a href=\"https://github.com/elementor/elementor/issues/11968\">#11968</a>)</li>\n<li>Tweak: Added dynamic content to Ribbon element in Call to Action widget (<a href=\"https://github.com/elementor/elementor/issues/10364\">#10364</a>)</li>\n<li>Tweak: Converted uses of Color and Typography Schemes to Global Colors and Fonts</li>\n<li>Tweak: Separated Title and Description control fields labels in Call to Action widget</li>\n<li>Tweak: Removed unnecessary style in WC Product with variations</li>\n<li>Tweak: Converted Portfolio, Posts and Share Buttons widgets to use CSS Variable-based Elementor Grid (<a href=\"https://developers.elementor.com/elementor-dropping-support-ie/\">Developers Blog Post</a>)</li>\n<li>Tweak: Added Date Modified option to Posts widget metadata</li>\n<li>Fix: PHP 7.4 compatibility to Media Carousel widget (<a href=\"https://github.com/elementor/elementor/issues/11355\">#11355</a>)</li>\n<li>Fix: Divider alignment issue in Post Info widget (<a href=\"https://github.com/elementor/elementor/issues/11628\">#11628</a>)</li>\n<li>Fix: Color doesn’t change in Products Archive Description widget</li>\n<li>Fix: WC Product variations layout breaks when using Variation Swatches plugin</li>\n<li>Fix: WC Product variations layout issue</li>\n<li>Fix: WC Product variations mobile zoom-in glitch</li>\n<li>Fix: Can\'t edit a Popup after accessing Theme Style</li>\n<li>Fix: Twitter icon missing in Blockquote widget</li>\n<li>Fix: Removed redundant default text color from Share Buttons minimal skin</li>\n<li>Fix: UI glitch in Display Conditions modal</li>\n<li>Fix: Insert template button UI glitch in Templates Library</li>\n<li>Fix: Added sanitization to post titles in WordPress dashboard for better security</li>\n<li>Fix: Show when arriving from search engines rule doesn\'t work in Popup</li>\n<li>Fix: Child categories are shown with a different parent category in Query control</li>\n<li>Deprecated: See all deprecations to this version in our <a href=\"https://developers.elementor.com/v3-0-planned-deprecations/\">Developers Deprecations Post</a></li>\n</ul>\n<h4>2.10.3 - 2020-06-29</h4>\n<ul>\n<li>Fix: Form not being submitted when using &quot;Progress Bar&quot; and &quot;None&quot; view types in Multi Step Form (<a href=\"https://github.com/elementor/elementor/issues/11596\">#11596</a>, <a href=\"https://github.com/elementor/elementor/issues/11610\">#11610</a>)</li>\n<li>Fix: Missing &quot;for&quot; attribute in Password field label in Login widget (<a href=\"https://github.com/elementor/elementor/issues/8646\">#8646</a>)</li>\n</ul>\n<h4>2.10.2 - 2020-06-16</h4>\n<ul>\n<li>Fix: Run step events only when in Multi Step Form mode (<a href=\"https://github.com/elementor/elementor/issues/11644\">#11644</a>)</li>\n</ul>\n<h4>2.10.1 - 2020-06-16</h4>\n<ul>\n<li>Tweak: Improved License validation mechanism to avoid limitations</li>\n<li>Tweak: Changed control labels and ordering in Price Table, Lottie and Form widgets</li>\n<li>Fix: Popup close button vertical position glitch (<a href=\"https://github.com/elementor/elementor/issues/10921\">#10921</a>)</li>\n<li>Fix: Radio field placement glitch when in Multi Step mode in Form widget</li>\n<li>Fix: Clicking <code>Enter</code> key submits the form in Multi Step Form</li>\n<li>Fix: Hardened sanitization in Custom Attributes to avoid security issues</li>\n</ul>\n<h4>2.10.0 - 2020-06-07</h4>\n<ul>\n<li>New: Introducing Multi-Step Forms - Breakdown long forms into simple steps (<a href=\"https://github.com/elementor/elementor/issues/5975\">#5975</a>, <a href=\"https://github.com/elementor/elementor/issues/3911\">#3911</a>)</li>\n<li>New: Introducing Lottie widget - easily add Lottie animations to your site, no coding needed (<a href=\"https://github.com/elementor/elementor/issues/11026\">#11026</a>)</li>\n<li>Tweak: Added spacing option to Posts widget pagination (<a href=\"https://github.com/elementor/elementor/issues/5682\">#5682</a>)</li>\n<li>Tweak: Changed texts and logic for administrator plugin renewal notices</li>\n<li>Tweak: Added new Scroll Util for improved scrolling handling</li>\n<li>Tweak: Improved Motion Effects animation performance</li>\n</ul>\n<h4>2.9.5 - 2020-05-24</h4>\n<ul>\n<li>Fix: Added sanitization to Custom Attributes control to avoid security issue</li>\n</ul>\n<h4>2.9.4 - 2020-05-07</h4>\n<ul>\n<li>Fix: Hardened user role that is allowed to upload icon sets and unzip only allowed files in Custom Icons to prevent security vulnerability</li>\n</ul>\n<h4>2.9.3 - 2020-04-19</h4>\n<ul>\n<li>Fix: Form shortcode IDs are not wrapped in double-quotes (<a href=\"https://github.com/elementor/elementor/issues/11023\">#11023</a>, <a href=\"https://github.com/elementor/elementor/issues/10932\">#10932</a>, <a href=\"https://github.com/elementor/elementor/issues/10967\">#10967</a>, <a href=\"https://github.com/elementor/elementor/issues/11000\">#11000</a>, <a href=\"https://github.com/elementor/elementor/issues/11049\">#11049</a>)</li>\n<li>Fix: Escaped Form records metadata to prevent security vulnerability</li>\n<li>Fix: Closing &quot;Save Changes&quot; document confirmation modal causes Panel infinite loading</li>\n<li>Fix: Ken Burns effect not working when there is only one slide in Slides widget</li>\n<li>Fix: Document handles UI glitch</li>\n</ul>\n<h4>2.9.2 - 2020-03-25</h4>\n<ul>\n<li>Tweak: Added compatibility with WordPress v5.4 (<a href=\"https://github.com/elementor/elementor/issues/10745\">#10745</a>)</li>\n<li>Fix: Image ratio number is displayed under the Archive Posts widget (<a href=\"https://github.com/elementor/elementor/issues/10874\">#10874</a>)</li>\n<li>Fix: Theme Style Link color setting overrides the Table of Content list style</li>\n<li>Fix: PHP notice when using dynamic user info <code>id</code></li>\n<li>Fix: Navigation arrows direction is crossed on first drag in Slides Widget</li>\n<li>Fix: &quot;No headings were found on this page&quot; message was not displayed in the frontend in Table of Contents widget</li>\n<li>Fix: Container includes Popup tags by default in Table of Contents widget</li>\n<li>Fix: Twitter icon display issue when Font Awesome 4 support is disabled in Blockquote widget</li>\n<li>Fix: ACF Dynamic tag not working in Form widget Redirect action</li>\n</ul>\n<h4>2.9.1 - 2020-03-16</h4>\n<ul>\n<li>Fix: Can\'t access Elementor Editor when there is Page Title widget in the page</li>\n<li>Fix: Applying styling to Post Content widget affects the Page and Post editing handles</li>\n</ul>\n<h4>2.9.0 - 2020-03-15</h4>\n<ul>\n<li>New: Introducing Full Site Editing: Design header, footer, and content all in one place! (<a href=\"https://github.com/elementor/elementor/issues/4985\">#4985</a>)</li>\n<li>New: Added Global Custom CSS for Your Entire Site in Theme Style (<a href=\"https://github.com/elementor/elementor/issues/3345\">#3345</a>)</li>\n<li>New: Added Dynamic Colors tag (<a href=\"https://github.com/elementor/elementor/issues/6485\">#6485</a>)</li>\n<li>Tweak: Added option to set the Site Part HTML Wrapper Tags (<a href=\"https://github.com/elementor/elementor/issues/9293\">#9293</a>)</li>\n<li>Tweak: Added Link Attributes support to Pro widgets (<a href=\"https://github.com/elementor/elementor/issues/5716\">#5716</a>, <a href=\"https://github.com/elementor/elementor/issues/3642\">#3642</a>, <a href=\"https://github.com/elementor/elementor/issues/9225\">#9225</a>, <a href=\"https://github.com/elementor/elementor/issues/9079\">#9079</a>)</li>\n<li>Tweak: Added Theme Style support in Theme Builder parts (<a href=\"https://github.com/elementor/elementor/issues/10564\">#10564</a>)</li>\n<li>Tweak: Avoid creating empty Custom Font</li>\n<li>Tweak: Added <code>aria-expanded</code> attribute to Menu Cart widget</li>\n<li>Tweak: Moved Link Actions module to Core plugin</li>\n<li>Tweak: Changed the name of “TypeKit Web Fonts by Adobe” to “Adobe Fonts”</li>\n<li>Tweak: Removed redundant display conditions from Blockquote, Flipbox, Price Table, and Search Form widgets</li>\n<li>Tweak: Pro widgets are not draggable unless Elementor license has been activated</li>\n<li>Tweak: Remove redundant <code>label_block</code> parameters from several controls</li>\n<li>Tweak: Converted controls selectors to CSS variables in Gallery widget</li>\n<li>Tweak: Replaced Stumbleupon with Mix in Reviews widget recommended icons (<a href=\"https://github.com/elementor/elementor/issues/10099\">#10099</a>)</li>\n<li>Tweak: Added Mix to the Share Buttons network list (<a href=\"https://github.com/elementor/elementor/issues/10099\">#10099</a>)</li>\n<li>Tweak: Added &quot;Open in new tab&quot; option to Posts widget (<a href=\"https://github.com/elementor/elementor/issues/7924\">#7924</a>)</li>\n<li>Tweak: Upgraded Font Awesome Pro library to v5.12.0</li>\n<li>Tweak: Added new Lightbox compatibility for Gallery and Media Carousel widgets</li>\n<li>Tweak: Expose external API for Swiper instances</li>\n<li>Tweak: Added compatibility to JS API in Theme Builder, Popups, Form widget and Global widget</li>\n<li>Tweak: Replaced nerd icons with new Elementor emojis</li>\n<li>Tweak: Added specific <code>color</code> attribute to header title in Table of Contents widget</li>\n<li>Fix: Line break issues in Animated Headline widget (<a href=\"https://github.com/elementor/elementor/issues/10585\">#10585</a>)</li>\n<li>Fix: Theme Style Link color overrides the Table of Content list style</li>\n<li>Fix: Active state glitches when using Table of contents widget with Sticky mode</li>\n<li>Fix: &quot;Graphic Element&quot; section appears as empty in case of unmarked Graphic Element in Call to Action widget</li>\n<li>Fix: Page Title widget render glitches in the Editor</li>\n<li>Fix: Image ratio parameter visible in some edge cases in Posts widget</li>\n<li>Fix: Image missing when sharing to Pinterest using Share Buttons widget</li>\n<li>Fix: Theme Style Link color setting override the list style in Table of Contents widget</li>\n<li>Deprecated: See all deprecations to this version in our <a href=\"https://developers.elementor.com/v2-9-0-planned-deprecations/\">Developers Deprecations Post</a></li>\n</ul>\n<h4>2.8.5 - 2020-03-08</h4>\n<ul>\n<li>Tweak: Added new Swiper parameter to all Pro carousels to allow 3rd party integration</li>\n<li>Fix: Missing closing bracket in Animated Headline widget</li>\n<li>Fix: Share buttons widgets show Font Awesome 4 icons on first drag in Editor</li>\n</ul>\n<h4>2.8.4 - 2020-02-16</h4>\n<ul>\n<li>Tweak: Added Lightbox Title &amp; Description support to Gallery widget</li>\n<li>Tweak: Added RTL support for Slides widget</li>\n<li>Tweak: Display Lightbox images in Full size in Gallery widget</li>\n<li>Fix: Template with Slides widget not working properly when placed inside Tabs, Accordion and Toggle widget</li>\n<li>Fix: Dropdown menu lost styling after Elementor Pro v2.8 upgrade in Nav Menu widget</li>\n<li>Fix: Indent doesn\'t work on RTL websites in Table of Contents widget</li>\n<li>Fix: Query Control throws <code>Undefined index: q</code> error</li>\n<li>Fix: Typography control not affecting dropdown menu in Nav Menu widget</li>\n<li>Fix: Discord forms integration fails to send submissions in some server configurations</li>\n<li>Fix: Rotating headlines don\'t align center in Animated Headline widget</li>\n<li>Fix: Custom secondary color displayed when not needed in Share buttons widget</li>\n<li>Fix: Motion Effects of certain objects are not functioning properly on Safari browser</li>\n<li>Fix: Missing eye icon in Single template footer preview button</li>\n</ul>\n<h4>2.8.3 - 2020-01-01</h4>\n<ul>\n<li>Tweak: Updated Table of Contents widget panel location</li>\n<li>Fix: ACF URL Dynamic field throws <code>undefined index</code> PHP notice (<a href=\"https://github.com/elementor/elementor/issues/9929\">#9929</a>)</li>\n<li>Fix: Gallery lightbox pagination shows images from all tabs</li>\n<li>Fix: &quot;Reply To&quot; option not working in Form widget &quot;Email 2&quot; Action</li>\n<li>Fix: ACF Dynamic tag not working in Form widget Redirect action</li>\n<li>Fix: Underline option not working in Table of Contents widget Normal state</li>\n<li>Fix: Query Control <code>Undefined index: autocomplete</code> notice in some cases</li>\n<li>Fix: Missing display condition to Read More Spacing control in Posts widget</li>\n</ul>\n<h4>2.8.2 - 2019-12-19</h4>\n<ul>\n<li>Tweak: Improved scroll-spy and collapsing functionality in Table of Contents widget</li>\n<li>Fix: &quot;No products were found&quot; message not being displayed in an empty Products Archive</li>\n<li>Fix: Redundant <code>&lt;br&gt;</code> tags in Single theme template (<a href=\"https://github.com/elementor/elementor/issues/9927\">#9927</a>, <a href=\"https://github.com/elementor/elementor/issues/9928\">#9928</a>)</li>\n<li>Fix: Draft Popup shows up in Dynamic tag dropdown</li>\n</ul>\n<h4>2.8.1 - 2019-12-18</h4>\n<ul>\n<li>Fix: Share Buttons widget not working (<a href=\"https://github.com/elementor/elementor/issues/9920\">#9920</a>)</li>\n<li>Fix: Redundant <code>&lt;p&gt;</code> tags added to Single Template posts</li>\n</ul>\n<h4>2.8.0 - 2019-12-18</h4>\n<ul>\n<li>New: Table of Contents Widget (<a href=\"https://github.com/elementor/elementor/issues/5171\">#5171</a>)</li>\n<li>New: Added Font Awesome Pro Duotone font family support (<a href=\"https://github.com/elementor/elementor/issues/9578\">#9578</a>)</li>\n<li>Tweak: Added Lazy Load option to Gallery widget (<a href=\"https://github.com/elementor/elementor/issues/9763\">#9763</a>)</li>\n<li>Tweak: Added Random order option to Gallery widget (<a href=\"https://github.com/elementor/elementor/issues/9269\">#9269</a>)</li>\n<li>Tweak: Updated Font Awesome Pro to v5.11.2 (<a href=\"https://github.com/elementor/elementor/issues/9578\">#9578</a>)</li>\n<li>Tweak: Added preselect support for multiple default select values in Forms Widget (<a href=\"https://github.com/elementor/elementor/issues/9324\">#9324</a>)</li>\n<li>Tweak: Avoid duplicate queries for Custom Icons (<a href=\"https://github.com/elementor/elementor/issues/9579\">#9579</a>)</li>\n<li>Tweak: Major performance improvements to Gallery widget</li>\n<li>Tweak: Avoid non-existing images in Gallery widget</li>\n<li>Tweak: Added <code>tabindex</code>, <code>aria-expanded</code>, <code>aria-hidden</code> and <code>role=\"navigation\"</code> accessibility attributes to Nav Menu widget</li>\n<li>Tweak: Changed button HTML tag from <code>button</code> to <code>span</code> in Call to Action and Flip Box widgets for better W3C compliance and accessibility</li>\n<li>Tweak: Removed Google+ from default networks in Share Buttons widget</li>\n<li>Tweak: Added compatibility for Library Connect</li>\n<li>Tweak: Added i18n to Toolset date dynamic tag</li>\n<li>Tweak: Added external link support to Gallery widget</li>\n<li>Tweak: Changed the link external attributes implementation to use <code>add_link_attributes()</code> in Gallery widget</li>\n<li>Tweak: Updated references to the new Schemes system location</li>\n<li>Tweak: Avoid running Gallery handler when the gallery is empty</li>\n<li>Tweak: UI Tweaks in Editor Panel</li>\n<li>Tweak: Added responsive capabilities to Pointer Width control in Nav Menu widget</li>\n<li>Tweak: Added mobile support for responsive controls in Nav Menu widget</li>\n<li>Tweak: Refactor <code>register_controls()</code> method in Posts widget skin trait</li>\n<li>Fix: ACF URL &quot;undefined Index&quot; notice (<a href=\"https://github.com/elementor/elementor/issues/7646\">#7646</a>)</li>\n<li>Fix: WooCommerce Mini-Cart widget causes fatal error in edge cases (<a href=\"https://github.com/elementor/elementor/issues/9304\">#9304</a>)</li>\n<li>Fix: <code>PHP Notice: Undefined index</code> display for Author query (<a href=\"https://github.com/elementor/elementor/issues/9864\">#9864</a>)</li>\n<li>Fix: Added compatibility for Button widget placed inside Swiper carousel (<a href=\"https://wordpress.org/support/topic/broken-buttons-since-elementor-2-8/\">Topic</a>)</li>\n<li>Fix: Avoid empty spaces in Post info widget</li>\n<li>Tweak: Always show &quot;Custom label&quot; control in Login widget</li>\n<li>Fix: Nav Menu item typography selector in Nav Menu widget</li>\n<li>Fix: Facebook Like Button widget causes flickering</li>\n<li>Fix: WooCommerce mini-cart behaviour when using <code>plain</code> permalinks format</li>\n<li>Fix: Avoid running Popup triggers when set without conditions</li>\n<li>Fix: Removed &quot;Date&quot; query from Products widget</li>\n<li>Fix: Slides widget when used as a Shortcode and is hidden</li>\n<li>Fix: Custom URL being accessed on swipe in Media Carousel</li>\n<li>Fix: Media Carousel widget Cube effect glitch</li>\n<li>Fix: Lightbox shows images from multiple Gallery widgets in the same page</li>\n<li>Fix: Image <code>alt</code> Text not displayed on overlay in Gallery widget</li>\n<li>Fix: Gallery widget not visible in Posts widget Full Content skin</li>\n<li>Fix: WooCommerce mini-cart remove unnecessary hooks registration when WooCommerce integration set to <code>Disable</code></li>\n<li>Fix: Slides widget button wrapping breaks in mobile view</li>\n<li>Fix: Dynamic capabilities with the Reviews widget</li>\n<li>Fix: Disabling autoplay doesn\'t work in Slides widget</li>\n<li>Fix: Posts widget Full Content skin not working on Single template</li>\n<li>Fix: Autocomplete not working for &quot;By Author&quot; condition in Display Conditions screen</li>\n<li>Fix: Posts widget alignment issue</li>\n<li>Fix: Product Variations Clear button not working in edge cases</li>\n<li>Fix: Styling issues in Form widget submit button</li>\n</ul>\n<h4>2.7.3 - 2019-10-28</h4>\n<ul>\n<li>Tweak: Added RTL support to Galleries widget (<a href=\"https://github.com/elementor/elementor/issues/9213\">#9213</a>)</li>\n<li>Tweak: Added Custom Icons compatibility for WordPress 5.3</li>\n<li>Fix: Missing template function declaration causes fatal error in WC mini-cart widget</li>\n<li>Fix: Pause on hover doesn\'t work in Carousel widgets</li>\n<li>Fix: Link-actions conflict with <code>?action=</code> parameter in the URL</li>\n<li>Fix: Lightbox navigation not working in Gallery widget Single mode</li>\n<li>Fix: Ken burns effect not working on the 1st slide if Infinite Loop option is turned off in Carousel widgets</li>\n<li>Fix: Popup Advanced Rules detects internal links as external if current URL starts with <code>www</code></li>\n</ul>\n<h4>2.7.2 - 2019-10-06</h4>\n<ul>\n<li>Fix: Slide Overlay not working when applying Ken burns effect in Slides widget (<a href=\"https://github.com/elementor/elementor/issues/9209\">#9209</a>)</li>\n<li>Fix: Content width glitch in Slides widget (<a href=\"https://github.com/elementor/elementor/issues/9180\">#9180</a>)</li>\n<li>Fix: Horizontal Alignment not working when applying custom style per slide in Slides widget (<a href=\"https://github.com/elementor/elementor/issues/9180\">#9180</a>)</li>\n<li>Fix: Missing semicolon in Custom Fonts <code>font-display</code> CSS</li>\n</ul>\n<h4>2.7.1 - 2019-09-26</h4>\n<ul>\n<li>Fix: Background Overlay layer is over the slide content in Slides widget (<a href=\"https://github.com/elementor/elementor/issues/9180\">#9180</a>)</li>\n<li>Fix: Duplicate images under &quot;All&quot; filter in Multiple Gallery</li>\n</ul>\n<h4>2.7.0 - 2019-09-24</h4>\n<ul>\n<li>New: Enhanced Galleries widget (<a href=\"https://github.com/elementor/elementor/issues/1898\">#1898</a>, <a href=\"https://github.com/elementor/elementor/issues/3103\">#3103</a>, <a href=\"https://github.com/elementor/elementor/issues/4279\">#4279</a>, <a href=\"https://github.com/elementor/elementor/issues/7631\">#7631</a>)</li>\n<li>New: Dynamic Number (<a href=\"https://github.com/elementor/elementor/issues/5952\">#5952</a>)</li>\n<li>New: Full content skin for Posts and Archive-posts widgets (<a href=\"https://github.com/elementor/elementor/issues/4617\">#4617</a>)</li>\n<li>Tweak: Added dynamic number capability to Price List, Price Table, Counter, Star Rating, Progress Bar widgets</li>\n<li>Tweak: Added tags support to forms Mailchimp action (<a href=\"https://github.com/elementor/elementor/issues/5418\">#5418</a>)</li>\n<li>Tweak: User Profile Picture Dynamic Tag (<a href=\"https://github.com/elementor/elementor/issues/7947\">#7947</a>, <a href=\"https://github.com/elementor/elementor/issues/8740\">#8740</a>)</li>\n<li>Tweak: Added <code>font-display</code> support to custom fonts (<a href=\"https://github.com/elementor/elementor/issues/5993\">#5993</a>, <a href=\"https://developers.elementor.com/elementor-pro-2-7-custom-fonts-font-display-support/\">Developers Blog Post</a>)</li>\n<li>Tweak: Added Text Shadow control to Slides widget (<a href=\"https://github.com/elementor/elementor/issues/8800\">#8800</a>)</li>\n<li>Tweak: Added Re-subscribe support to MailerLite (<a href=\"https://github.com/elementor/elementor/issues/8799\">#8799</a>)</li>\n<li>Tweak: Added Dynamic capabilities to Facebook Embed widget (<a href=\"https://github.com/elementor/elementor/issues/9030\">#9030</a>)</li>\n<li>Tweak: Use <code>swiper.js</code> instead of <code>slick.js</code> in Slides widget (<a href=\"https://developers.elementor.com/elementor-2-7-moving-sliders-from-slick-to-swiper/\">Developers Blog Post</a>)</li>\n<li>Tweak: Added <code>elementor_pro/search_form/before_input</code> action hook to Search Form widget (<a href=\"https://github.com/elementor/elementor/issues/5598\">#5598</a>)</li>\n<li>Tweak: Added <code>elementor_pro/search_form/after_input</code> action hook to Search Form widget (<a href=\"https://github.com/elementor/elementor/issues/5598\">#5598</a>)</li>\n<li>Tweak: Added dynamic support for Custom field key (<a href=\"https://github.com/elementor/elementor/issues/7789\">#7789</a>)</li>\n<li>Tweak: Increased expired license notice bar frequency</li>\n<li>Tweak: Changed the icon name of Slides widget</li>\n<li>Tweak: Added designated Finder\'s Icons for Custom icons &amp; Custom fonts</li>\n<li>Tweak: Use Ken Burns Effect as an external module</li>\n<li>Tweak: Remove Fontello conflicting CSS on import to Custom Icons sets</li>\n<li>Tweak: Editor Panel UI tweaks</li>\n<li>Tweak: Added DOM events on Popup show/hide (<a href=\"https://developers.elementor.com/elementor-pro-2-7-popup-events/\">Developers Blog Post</a>)</li>\n<li>Tweak: Added option to change the variations field width in Add to Cart widget</li>\n<li>Tweak: Use select control instead of select2 in Menu Cart widget</li>\n<li>Tweak: Added conditions to the tabs instead of to each control in Share Buttons widget</li>\n<li>Tweak: Added Typography controls to HTML field in Forms widget</li>\n<li>Tweak: Allow edit selected Font file in Custom Font</li>\n<li>Tweak: Changed reCAPTCHA v3 error message</li>\n<li>Tweak: Remove the &quot;Save as Global&quot; option on Global widget context menu</li>\n<li>Fix: Corrected selector for <code>removeControlSpinner()</code> (<a href=\"https://github.com/elementor/elementor/issues/8790\">#8790</a>)</li>\n<li>Fix: Slides widget navigation icons misplacement (<a href=\"https://github.com/elementor/elementor/issues/8533\">#8533</a>)</li>\n<li>Fix: Horizontal Scrollbar when Slider widget is set to Full Width (<a href=\"https://github.com/elementor/elementor/issues/8527\">#8527</a>)</li>\n<li>Fix: Inconsistent behavior when &quot;Infinite Loop&quot; enabled with &quot;Autoplay&quot; in Slides widget (<a href=\"https://github.com/elementor/elementor/issues/6726\">#6726</a>)</li>\n<li>Fix: Ken Burns effect on Chrome transition glitches (<a href=\"https://github.com/elementor/elementor/issues/1671\">#1671</a>)</li>\n<li>Fix: Nothing found message shows up inside the columns set in Posts Archive widget (<a href=\"https://github.com/elementor/elementor/issues/7347\">#7347</a>)</li>\n<li>Fix: Responsive UI glitch in Popup Conditions modal tabs</li>\n<li>Fix: Removed unnecessary divider in Call to Action widget</li>\n<li>Fix: Custom Add To Cart * button style (size, position and background color) when <code>quantity</code> is enabled.</li>\n<li>Fix: Add support for Document/PageBase in Theme Builder (Core &gt;=2.7.0)</li>\n<li>Fix: Ampersand character breaks email link in Share Buttons widget</li>\n<li>Fix: Correct custom font attachment <code>mime-type</code> to show uploaded Custom Fonts</li>\n<li>Fix: Mini-Cart not refreshing in Menu Cart widget</li>\n<li>Fix: Cart drawer not working when WC Subscriptions plugin is activated</li>\n<li>Fix:  Querying CPT with custom taxonomies does not show the taxonomies before saving</li>\n<li>Fix: Double rendering on change caused console error in Theme Builder\'s conditions screen</li>\n<li>Fix: Translations and Strings in Share Buttons widget</li>\n<li>Fix: Avoid using offset if the source is Manual selection in Query Control</li>\n<li>Fix: Form being submitted although reCAPTCHA v3 validation failed in Forms widget</li>\n</ul>\n<h4>2.6.5 - 2019-08-26</h4>\n<ul>\n<li>Tweak: Added compatibility for the upcoming release of Elementor v2.7</li>\n<li>Fix: Button style not working when <code>quantity</code> is enabled in Custom Add To Cart widget</li>\n<li>Fix: Updated minified JS file fixed WhatsApp base URL in Share Buttons widget</li>\n</ul>\n<h4>2.6.4 - 2019-08-21</h4>\n<ul>\n<li>Tweak: Added compatibility for the upcoming release of Elementor v2.7</li>\n<li>Fix: Changed WhatsApp base URL in Share Buttons widget for cross-device compatibility</li>\n<li>Fix: Random slides order after several clicks on pagination in Testimonial Carousel widget</li>\n</ul>\n<h4>2.6.3 - 2019-08-18</h4>\n<ul>\n<li>Fix: Core version rollback to <code>&gt;2.6.0</code> causes a fatal error</li>\n<li>Fix: Duplicate images when slideshow skin is selected in Media Carousel lightbox</li>\n<li>Fix: Default bottom margin added to reCAPTCHA V3 badge</li>\n<li>Fix: Input glitch in reCAPTCHA V3 threshold settings</li>\n</ul>\n<h4>2.6.2 - 2019-07-30</h4>\n<ul>\n<li>Tweak: Better accessibility support in Search Form widget</li>\n<li>Fix: UI glitched in Popup publish screen (<a href=\"https://github.com/elementor/elementor/issues/8616\">#8616</a>)</li>\n<li>Fix: &quot;Child of Term&quot; and &quot;Any child of term&quot; conditions (<a href=\"https://github.com/elementor/elementor/issues/8695\">#8695</a>)</li>\n<li>Fix: Restored <code>library_widget_templates</code> action hook for 3rd party compatibility (<a href=\"https://github.com/elementor/elementor/issues/8687\">#8687</a>)</li>\n<li>Fix: Twitter Icon missing in Blockquote widget</li>\n<li>Fix: Form reCAPTCHA v3 badge position not working</li>\n<li>Fix: Renewal notice bar appears in wrong situations</li>\n<li>Fix: Draft Icon Set loads empty Icon Library</li>\n</ul>\n<h4>2.6.1 - 2019-07-24</h4>\n<ul>\n<li>Fix: Query Control autocomplete not retrieving results (<a href=\"https://github.com/elementor/elementor/issues/8672\">#8672</a>, <a href=\"https://github.com/elementor/elementor/issues/8661\">#8661</a>)</li>\n<li>Fix: Price Table features section not working (<a href=\"https://github.com/elementor/elementor/issues/8660\">#8660</a>)</li>\n</ul>\n<h4>2.6.0 - 2019-07-23</h4>\n<ul>\n<li>New: Introducing Custom Icon sets - including Fontello, IcoMoon and Fontastic support (<a href=\"https://github.com/elementor/elementor/issues/110\">#110</a>)</li>\n<li>New: Added Font Awesome 5 Pro integration including 5,300+ icons (<a href=\"https://github.com/elementor/elementor/issues/4430\">#4430</a>)</li>\n<li>New: Added reCAPTCHA v3 integration to Form widget (<a href=\"https://github.com/elementor/elementor/issues/8213\">#8213</a>, <a href=\"https://github.com/elementor/elementor/issues/6039\">#6039</a>, <a href=\"https://github.com/elementor/elementor/issues/7165\">#7165</a>)</li>\n<li>Tweak: Added Exit Animation for Popups (<a href=\"https://github.com/elementor/elementor/issues/7063\">#7063</a>)</li>\n<li>Tweak: Added ACF Dynamic tag support for archive pages (<a href=\"https://github.com/elementor/elementor/issues/5147\">#5147</a>)</li>\n<li>Tweak: Added Navigator Indicators for Custom CSS &amp; Motion Effects (<a href=\"https://github.com/elementor/elementor/issues/2180\">#2180</a>)</li>\n<li>Tweak: Added Dynamic capabilities for Form Redirect action (<a href=\"https://github.com/elementor/elementor/issues/7552\">#7552</a>)</li>\n<li>Tweak: Added Logged In Message styling options for Login widget (<a href=\"https://github.com/elementor/elementor/issues/7928\">#7928</a>)</li>\n<li>Tweak: Added <code>none</code> breakpoint option to Nav Menu widget (<a href=\"https://github.com/elementor/elementor/issues/7916\">#7916</a>)</li>\n<li>Tweak: Added option to place Post Terms dynamic tag without links (<a href=\"https://github.com/elementor/elementor/issues/8366\">#8366</a>)</li>\n<li>Tweak: Added <code>elementor/query/query_results</code> hook to Query Control to allow full control over results (<a href=\"https://github.com/elementor/elementor/issues/7912\">#7912</a>)</li>\n<li>Tweak: Allow choosing Heading HTML tag in Price Table widget (<a href=\"https://github.com/elementor/elementor/issues/8090\">#8090</a>)</li>\n<li>Tweak: Show popup on dynamic click even when <code>Avoid Multiple Popups</code> option is selected (<a href=\"https://github.com/elementor/elementor/issues/8189\">#8189</a>)</li>\n<li>Tweak: Added condition option to all of archive child pages (<a href=\"https://github.com/elementor/elementor/issues/8256\">#8256</a>)</li>\n<li>Tweak: Added <code>Effects Relative To</code> control to Scrolling Effects</li>\n<li>Tweak: Allow shortcodes in HTML Form field</li>\n<li>Tweak: Removed donReach integration from Share Buttons widget due to service inconsistent stability</li>\n<li>Tweak: Changed MailChimp <code>List</code> label to <code>Audience</code></li>\n<li>Tweak: Improved Entrance and Exit animation behavior in Popup</li>\n<li>Tweak: Added <code>Deprecated Notice</code> control to <code>Archive Products</code> and <code>Woo Products</code> widgets</li>\n<li>Tweak: Added default dynamic title for archives in Theme Builder</li>\n<li>Tweak: Added condition to show <code>Centered Slides</code> control in Media Carousel widget</li>\n<li>Tweak: Added notice bar in the Editor when the license is expired or not activated</li>\n<li>Tweak: Replaced <code>select</code> control with <code>choose</code> control in Price List widget</li>\n<li>Tweak: Removed Font Awesome 4 dependencies from the Editor</li>\n<li>Tweak: Minor styling tweaks in the Popup publish modal</li>\n<li>Tweak: Hide ordering form in Products widget on front page</li>\n<li>Tweak: Removed page title markup when \'Hide Title\' is active</li>\n<li>Tweak: Added style controls for HTML field in Form widget</li>\n<li>Fix: Form widget Date picker makes the Popup builder disappear (<a href=\"https://github.com/elementor/elementor/issues/7240\">#7240</a>)</li>\n<li>Fix: Sticky element stop point stops working on viewport resize (<a href=\"https://github.com/elementor/elementor/issues/7884\">#7884</a>)</li>\n<li>Fix: Copy-Paste style not pasting the Pointer option in Nav Menu widget (<a href=\"https://github.com/elementor/elementor/issues/8497\">#8497</a>)</li>\n<li>Fix: Missing Print icon in Share Buttons (<a href=\"https://github.com/elementor/elementor/issues/8506\">#8506</a>)</li>\n<li>Fix: UI style glitch in Blockquote widget when viewing from iPad</li>\n<li>Deprecated: <code>DB::save_editor()</code> - Remove usage of this method (<a href=\"https://developers.elementor.com/v2-6-0-planned-deprecations/\">Deprecation Post</a>)</li>\n<li>Deprecated: <code>DB::get_plain_editor()</code> - Remove usage of this method (<a href=\"https://developers.elementor.com/v2-6-0-planned-deprecations/\">Deprecation Post</a>)</li>\n</ul>\n<h4>2.5.14 - 2019-07-14</h4>\n<ul>\n<li>Fix: Better WC Related Product grid support to various themes (<a href=\"https://github.com/elementor/elementor/issues/8555\">#8555</a>)</li>\n</ul>\n<h4>2.5.13 - 2019-07-11</h4>\n<ul>\n<li>Fix: Better WC grid support to various themes</li>\n</ul>\n<h4>2.5.12 - 2019-07-10</h4>\n<ul>\n<li>Fix: Grid for WooCommerce Archive Product widget</li>\n<li>Fix: Remove redundant <code>whitespace</code> CSS property causes style glitch in iPad</li>\n<li>Tweak: Added more compatibility for Elementor v2.6</li>\n</ul>\n<h4>2.5.11 - 2019-07-02</h4>\n<ul>\n<li>Fix: Close icon missing from Nav Menu widget (<a href=\"https://github.com/elementor/elementor/issues/8460\">#8460</a>)</li>\n<li>Fix: Elementor Pro v2.5.10 shows PHP notice regarding notice bar (<a href=\"https://github.com/elementor/elementor/issues/8461\">#8461</a>)</li>\n<li>Fix: Fatal error when deleting used Pods fields (<a href=\"https://github.com/elementor/elementor/issues/8396\">#8396</a>)</li>\n<li>Fix: Missing dropdown icon in conditions screen</li>\n</ul>\n<h4>2.5.10 - 2019-05-28</h4>\n<ul>\n<li>Tweak: Added compatibility for the upcoming release of Elementor v2.6</li>\n<li>Tweak: Error caused by empty Rows &amp; Columns values in Products widget (<a href=\"https://github.com/elementor/elementor/issues/8261\">#8261</a>)</li>\n<li>Fix: Do not unset <code>product</code> CPT if it\'s not from WooCommerce (<a href=\"https://github.com/elementor/elementor/issues/8160\">#8160</a>)</li>\n<li>Fix: Column Spacing not working in WooCommerce Archive Products widget (<a href=\"https://github.com/elementor/elementor/issues/8285\">#8285</a>)</li>\n<li>Fix: Title styling not working in Products Categories widget</li>\n<li>Fix: Empty value in Dynamic Pods Gallery dropdown using Safari browser</li>\n<li>Fix: WooCommerce archives included in &quot;All Archives&quot; condition</li>\n</ul>\n<h4>2.5.9 - 2019-05-28</h4>\n<ul>\n<li>Tweak: Removed <code>auto-confirm</code> control from MailPoet to support new version of MailPoet</li>\n<li>Fix: Multiple Custom Fonts not rendered in the editor</li>\n<li>Fix: Products <code>sale</code> query - handle exclude by manual selection.</li>\n<li>Fix: Product Categories grid row &amp; column style</li>\n<li>Fix: Form integration AJAX cache override</li>\n<li>Fix: Removed redundant CSS on Canvas &amp; Header-Footer page templates</li>\n</ul>\n<h4>2.5.8 - 2019-05-06</h4>\n<ul>\n<li>Fix: Popup entrance animation not working in frontend</li>\n<li>Fix: Popup Exit Intent trigger activated multiple times</li>\n</ul>\n<h4>2.5.7 - 2019-05-05</h4>\n<ul>\n<li>Fix: Embedded video keeps playing after a Popup is closed (<a href=\"https://github.com/elementor/elementor/issues/7875\">#7875</a>)</li>\n<li>Fix: Maximum call stack size exceeded error in Safari (<a href=\"https://github.com/elementor/elementor/issues/7824\">#7824</a>)</li>\n<li>Fix: Entrance animations not appearing on Popup reopen (<a href=\"https://github.com/elementor/elementor/issues/7395\">#7395</a>)</li>\n<li>Fix: WC variations select style glitch in several themes (<a href=\"https://github.com/elementor/elementor/issues/8008\">#8008</a>)</li>\n<li>Fix: Theme Builder taxonomy conditions not retrieving proper results in edge cases</li>\n</ul>\n<h4>2.5.6 - 2019-04-29</h4>\n<ul>\n<li>Tweak: Removed <code>Shortcode</code> dynamic from Image, Gallery and Media control</li>\n<li>Fix: Popup not inheriting entrance animation in responsive mode (<a href=\"https://github.com/elementor/elementor/issues/7809\">#7809</a>)</li>\n<li>Fix: Terms autocomplete retrieves wrong results in Query Control</li>\n<li>Fix: Query Control Related by author glitches in edge cases</li>\n<li>Fix: Query Control using terms for Products widget</li>\n<li>Fix: Posts cards style glitch in small screens</li>\n<li>Fix: Display conditions delete icon missing in small screens</li>\n<li>Fix: Avoid rendering Menu Cart widget in WordPress native editor</li>\n</ul>\n<h4>2.5.5 - 2019-04-08</h4>\n<ul>\n<li>Tweak: Allow text selection inside a Popup</li>\n<li>Fix: Added backwards compatibility for <code>tax_query</code> in Query Control (<a href=\"https://github.com/elementor/elementor/issues/7751\">#7751</a>)</li>\n<li>Fix: Missing arguments for <code>widget_title</code> filter (<a href=\"https://github.com/elementor/elementor/issues/7745\">#7745</a>)</li>\n</ul>\n<h4>2.5.4 - 2019-04-03</h4>\n<ul>\n<li>Fix: Move Query from using <code>term_id</code> to <code>term_taxonomy_id</code> (<a href=\"https://github.com/elementor/elementor/issues/7653\">#7653</a>)</li>\n<li>Fix: Offset manipulation hook removal in Query control</li>\n<li>Fix: Missing form field <code>ID</code> in some edge cases (<a href=\"https://github.com/elementor/elementor/issues/7711\">#7711</a>, <a href=\"https://github.com/elementor/elementor/issues/7660\">#7660</a>)</li>\n</ul>\n<h4>2.5.3 - 2019-03-31</h4>\n<ul>\n<li>Tweak: Updated Google Calendar dynamic tag URL (<a href=\"https://github.com/elementor/elementor/issues/7673\">#7673</a>)</li>\n<li>Fix: Missing form field names (<a href=\"https://github.com/elementor/elementor/issues/7651\">#7651</a>)</li>\n<li>Fix: PHP 5.4 backward compatibility in Query Control (<a href=\"https://github.com/elementor/elementor/issues/7633\">#7633</a>)</li>\n<li>Fix: <code>products_deprecated</code> Query Control module compatibility (<a href=\"https://github.com/elementor/elementor/issues/7654\">#7654</a>)</li>\n<li>Fix: Changed query method from <code>term_id</code> to <code>term_taxonomy_id</code> (<a href=\"https://github.com/elementor/elementor/issues/7653\">#7653</a>)</li>\n</ul>\n<h4>2.5.2 - 2019-03-27</h4>\n<ul>\n<li>Fix: Overwrite parent widget type in Global Widget (<a href=\"https://github.com/elementor/elementor/issues/7632\">#7632</a>)</li>\n<li>Fix: Avoid Duplicates option not working in Query Control (<a href=\"https://github.com/elementor/elementor/issues/7635\">#7635</a>)</li>\n<li>Fix: Manual Selection option not working in Query Control (<a href=\"https://github.com/elementor/elementor/issues/7634\">#7634</a>)</li>\n<li>Fix: Incorrect condition caused handlers issues inside popup</li>\n</ul>\n<h4>2.5.1 - 2019-03-26</h4>\n<ul>\n<li>Fix: Query Control invalid call to deprecated action (<a href=\"https://github.com/elementor/elementor/issues/7619\">#7619</a>)</li>\n<li>Tweak: Renamed action hook from <code>elementor_pro/{$widget_name}/query/{$query_id}</code> to <code>elementor/query/{$query_id}</code></li>\n<li>Tweak: Renamed filter hook from <code>elementor_pro/query_control/get_query_args/current_query</code> to <code>elementor/query/get_query_args/current_query</code></li>\n</ul>\n<h4>2.5.0 - 2019-03-26</h4>\n<ul>\n<li>New: Introducing Motion Effects including Scrolling &amp; Mouse effects (<a href=\"https://github.com/elementor/elementor/issues/72\">#72</a>)</li>\n<li>New: Introducing Related Posts for Query Control (<a href=\"https://github.com/elementor/elementor/issues/7306\">#7306</a>, <a href=\"https://github.com/elementor/elementor/issues/7490\">#7490</a>)</li>\n<li>New: Introducing Date query for Query Control</li>\n<li>New: Introducing Sticky Posts support for Query Control (<a href=\"https://github.com/elementor/elementor/issues/2501\">#2501</a>)</li>\n<li>Tweak: Added option to open a Popup by a custom selector (<a href=\"https://github.com/elementor/elementor/issues/6871\">#6871</a>, <a href=\"https://github.com/elementor/elementor/issues/6876\">#6876</a>, <a href=\"https://github.com/elementor/elementor/issues/7258\">#7258</a>)</li>\n<li>Tweak: Option to count when Popup is closed in &quot;Show up to X times&quot; Advanced Rule</li>\n<li>Tweak: Added full border radius control options inside Popup</li>\n<li>Tweak: Changed exit intent icon in Popups</li>\n<li>Tweak: Show only one popup in its own preview</li>\n<li>Tweak: Added responsive support to Popup entrance animation control</li>\n<li>Tweak: Conditions - Singular <code>All Pages</code> string changed to <code>Pages</code></li>\n<li>Tweak: Added form field shortcode support for Drip tags (<a href=\"https://github.com/elementor/elementor/issues/7000\">#7000</a>)</li>\n<li>Tweak: Added dynamic capabilities to Price List widget (<a href=\"https://github.com/elementor/elementor/issues/7258\">#7258</a>)</li>\n<li>Tweak: Added Dynamic capabilities to Custom Attributes (<a href=\"https://github.com/elementor/elementor/issues/6779\">#6779</a>)</li>\n<li>Tweak: Added dynamic capabilities to Flip Box widget (<a href=\"https://github.com/elementor/elementor/issues/6986\">#6986</a>)</li>\n<li>Tweak: Decrease <code>z-index</code> for Nav Menu (<a href=\"https://github.com/elementor/elementor/issues/6869\">#6869</a>)</li>\n<li>Tweak: Changed &quot;Scrolling Effects&quot; section label to &quot;Motion Effects&quot;</li>\n<li>Tweak: Use filter <code>get_meta_viewport</code> for header templates (<a href=\"https://github.com/elementor/elementor/issues/7043\">#7043</a>)</li>\n<li>Tweak: use filterable <code>Util::get_public_post_types()</code> in Theme Builder (<a href=\"https://github.com/elementor/elementor/issues/7172\">#7172</a>)</li>\n<li>Tweak: Added Cloudflare rocket-loader support (<a href=\"https://github.com/elementor/elementor/issues/7443\">#7443</a>)</li>\n<li>Tweak: Added responsive support to WC Products Columns &amp; Rows Gap controls (<a href=\"https://github.com/elementor/elementor/issues/6913\">#6913</a>)</li>\n<li>Tweak: WC Menu cart &quot;View Cart&quot; &amp; &quot;Checkout&quot; buttons styling</li>\n<li>Fix: Custom ID reset to default when dragging repeater</li>\n<li>Fix: Conflict between archive-products widget and WC customizer</li>\n<li>Fix: Add to Cart widget <code>spacing</code> and <code>space-between</code></li>\n<li>Fix: Library view when creating a new Header or Footer</li>\n<li>Fix: Post types labels missing on Add New Template modal</li>\n</ul>\n<h4>2.4.8 - 2019-03-11</h4>\n<ul>\n<li>Fix: Missing query section in Products widget</li>\n<li>Fix: Missing Taxonomy controls in Products widget in edge cases</li>\n</ul>\n<h4>2.4.7 - 2019-03-06</h4>\n<ul>\n<li>Fix: Compatibility Global Widget with Elementor v2.5.0+</li>\n</ul>\n<h4>2.4.6 - 2019-03-04</h4>\n<ul>\n<li>Fix: Pods gallery dynamic when empty (<a href=\"https://github.com/elementor/elementor/issues/7127\">#7127</a>)</li>\n<li>Fix: Duplicate call for conditions screen issue</li>\n<li>Fix: Compatibility with Elementor v2.5.0</li>\n</ul>\n<h4>2.4.5 - 2019-02-18</h4>\n<ul>\n<li>Fix: Image size issue in Testimonial Carousel (<a href=\"https://github.com/elementor/elementor/issues/7058\">#7058</a>)</li>\n<li>Fix: MailChimp groups not saved in a form integration (<a href=\"https://github.com/elementor/elementor/issues/7083\">#7083</a>)</li>\n<li>Fix: Show popup preview only on it\'s own preview</li>\n<li>Fix: Elementor dashboard templates URL corrupted links in edge cases</li>\n</ul>\n<h4>2.4.4 - 2019-02-11</h4>\n<ul>\n<li>Tweak: Added ACF Date Time Picker field support (<a href=\"https://github.com/elementor/elementor/issues/6690\">#6690</a>)</li>\n<li>Tweak: Changed the term of <code>All Posts</code> condition to <code>Posts</code></li>\n<li>Fix: Added <code>&lt;IfModule&gt;</code> to avoid 500 error when <code>mod-headers</code> is missing (<a href=\"https://github.com/elementor/elementor/issues/7034\">#7034</a>)</li>\n<li>Fix: Include post CSS deletion in Global Widget update (<a href=\"https://github.com/elementor/elementor/issues/6856\">#6856</a>)</li>\n<li>Fix: <code>Textarea</code> default value in Forms Widget (<a href=\"https://github.com/elementor/elementor/issues/6934\">#6934</a>)</li>\n<li>Fix: MailPoet latest version caused fatal error (<a href=\"https://github.com/elementor/elementor/issues/6996\">#6996</a>)</li>\n<li>Fix: Fatal Error caused by calling MailPoet deleted method</li>\n<li>Notice: MailPoet <code>Auto Confirm</code> option will now default to &quot;On&quot;</li>\n</ul>\n<h4>2.4.3 - 2019-01-30</h4>\n<ul>\n<li>Fix: Custom Add to Cart widget responsive alignment settings</li>\n<li>Fix: Links in Post Info widget</li>\n<li>Fix: WooCommerce <code>View Cart</code> string translate</li>\n<li>Fix: Wrapper classes for header/footer templates (<a href=\"https://github.com/elementor/elementor/issues/6884\">#6884</a>)</li>\n</ul>\n<h4>2.4.2 - 2019-01-25</h4>\n<ul>\n<li>Tweak: Added pixel units to Close Button position control in Popups</li>\n<li>Fix: Exclude error in WC Products widget</li>\n</ul>\n<h4>2.4.1 - 2019-01-24</h4>\n<ul>\n<li>Tweak: Added CSS classes control to Popup (<a href=\"https://github.com/elementor/elementor/issues/6826\">#6826</a>)</li>\n<li>Tweak: Added responsive image size to Testimonial Carousel widget</li>\n<li>Fix: PHP warning when Toolset Date dynamic is empty (<a href=\"https://github.com/elementor/elementor/issues/6842\">#6842</a>)</li>\n<li>Fix: Support of exclude-ids in WC Products widget</li>\n<li>Fix: Popup close button not clickable</li>\n<li>Fix: Alignment justify issue of Add to Cart widget (<a href=\"https://github.com/elementor/elementor/issues/6749\">#6749</a>)</li>\n<li>Fix: Bad anchors breaks the page JS</li>\n<li>Fix: Popup overlay shown when turned off</li>\n</ul>\n<h4>2.4.0 - 2019-01-21</h4>\n<ul>\n<li>New: Introducing Popup Builder (<a href=\"https://github.com/elementor/elementor/issues/628\">#628</a>)</li>\n<li>New: Added <code>Popup</code> Dynamic Tag</li>\n<li>New: Added <code>Popup</code> forms action after submit</li>\n<li>New: Added User Info dynamic tag (<a href=\"https://github.com/elementor/elementor/issues/6322\">#6322</a>)</li>\n<li>Tweak: Added dynamic capabilities for &quot;Nothing Found&quot; message</li>\n<li>Tweak: Added <code>elementor_pro/theme_builder/archive/escape_nothing_found_message</code> Filter to avoid HTML escaping in &quot;Nothing Found&quot; message (<a href=\"https://github.com/elementor/elementor/issues/6053\">#6053</a>)</li>\n<li>Tweak: Added <code>add_doc_to_location</code> method to Allow insertion of a document to a location</li>\n<li>Fix: <code>z-index</code> issue with CTA widget (<a href=\"https://github.com/elementor/elementor/issues/6486\">#6486</a>)</li>\n<li>Fix: Hide the Post Content widget and show it only in a Single document</li>\n<li>Fix: <code>selector</code> replacement in Custom CSS</li>\n<li>Fix: Apply <code>the_content</code> on the real content only</li>\n<li>Fix: CSS for WC products selector (<a href=\"https://github.com/elementor/elementor/issues/6559\">#6559</a>)</li>\n<li>Fix: Odnoklassniki share URL (<a href=\"https://github.com/elementor/elementor/issues/6638\">#6638</a>)</li>\n<li>Fix: Custom link new tab in Post Info widget (<a href=\"https://github.com/elementor/elementor/issues/5766\">#5766</a>)</li>\n<li>Fix: <code>nofollow</code> link in Flip Box &amp; CTA widgets</li>\n<li>Fix: Post Terms in Post Info widget</li>\n<li>Fix: Added screen reader to some icons &amp; buttons for better accessibility (<a href=\"https://github.com/elementor/elementor/issues/5386\">#5386</a>)</li>\n<li>Fix: Accessibility labels in Reviews widget (<a href=\"https://github.com/elementor/elementor/issues/6630\">#6630</a>)</li>\n<li>Fix: Link to cart page not working when WooCommerce Subscriptions is active</li>\n<li>Fix: MailChimp Selected list not showing on reloading in Form widget</li>\n<li>Fix: Sub-menu arrow position in Nav Menu widget</li>\n<li>Fix: Conflict with WP Security Audit Log plugin (<a href=\"https://github.com/elementor/elementor/issues/6648\">#6648</a>)</li>\n</ul>\n<h4>2.3.1 - 2018-12-19</h4>\n<ul>\n<li>Fix: Template widget search functionality (<a href=\"https://github.com/elementor/elementor/issues/6473\">#6473</a>)</li>\n<li>Fix: Apply <code>the_content</code> filter to post content in theme builder</li>\n</ul>\n<h4>2.3.0 - 2018-12-17</h4>\n<ul>\n<li>New: Introducing Discord Integration for Forms (<a href=\"https://github.com/elementor/elementor/issues/4218\">#4218</a>)</li>\n<li>New: Introducing Slack Integration for Forms</li>\n<li>New: Introducing MailerLite Integration for Forms (<a href=\"https://github.com/elementor/elementor/issues/4462\">#4462</a>)</li>\n<li>New: Activate Elementor Pro plugin by connecting to Elementor account</li>\n<li>Tweak: Added <code>elementor_pro/utils/get_public_post_types</code> filter hook (<a href=\"https://github.com/elementor/elementor/issues/5900\">#5900</a>)</li>\n<li>Tweak: Added <code>loop_start</code> &amp; <code>the_content</code> hooks for Post Content (<a href=\"https://github.com/elementor/elementor/issues/6173\">#6173</a>)</li>\n<li>Tweak: Removed Custom Attributes from Page Settings</li>\n<li>Tweak: Always add the Custom CSS control to the Advanced tab</li>\n<li>Fix: In sub Term condition false positive in edge cases</li>\n<li>Fix: ToolSet Dynamic Image fallback</li>\n<li>Fix: Style glitch with the dropdown color in Nav Menu widget</li>\n<li>Fix: Style glitch in the Conditions screen in Safari browser</li>\n<li>Fix: Ribbon in the CTA widget obscures drop down menu (<a href=\"https://github.com/elementor/elementor/issues/6080\">#6080</a>)</li>\n<li>Fix: The color of label won\'t change color in Widget login</li>\n</ul>\n<h4>2.2.5 - 2018-12-11</h4>\n<ul>\n<li>New: Add Style Tab &amp; Custom CSS for Header &amp; Footer Templates.</li>\n<li>Tweak: Added a better identifier for subpages (<a href=\"https://github.com/elementor/elementor/issues/6362\">#6362</a>)</li>\n<li>Tweak: Removed Custom Attributes from page settings</li>\n<li>Fix: Yahoo event URL date issue (<a href=\"https://github.com/elementor/elementor/issues/6354\">#6354</a>)</li>\n<li>Fix: Allow timezone settings in Google event URL (<a href=\"https://github.com/elementor/elementor/issues/6354\">#6354</a>)</li>\n<li>Fix: Avoid <code>z-index</code> changes by <code>nanocss</code> in build process</li>\n<li>Fix: Added missing WC upsells products CSS</li>\n<li>Fix: Nav Menu dropdown losing color on hover</li>\n<li>Fix: WC Product Add-ons CSS compatibility</li>\n</ul>\n<h4>2.2.4 - 2018-12-04</h4>\n<ul>\n<li>Fix: Global widget not saving changes (<a href=\"https://github.com/elementor/elementor/issues/6340\">#6340</a>)</li>\n<li>Fix: Dynamic tags support in Blockquote widget (<a href=\"https://github.com/elementor/elementor/issues/6334\">#6334</a>)</li>\n<li>Fix: Forms Redirect URL action when using form field values with spaces</li>\n</ul>\n<h4>2.2.3 - 2018-11-29</h4>\n<ul>\n<li>Fix: Missing &quot;Edit Template&quot; in Template widget (<a href=\"https://github.com/elementor/elementor/issues/6271\">#6271</a>)</li>\n<li>Fix: Follow menu anchors with UTF8 characters in Nav Menu</li>\n<li>Fix: Show only supported templates in Template widget</li>\n<li>Fix: Revert conflicting fix for a default order for WC archive</li>\n</ul>\n<h4>2.2.2 - 2018-11-28</h4>\n<ul>\n<li>Fix: Lightbox dynamic tag crashes the editor</li>\n</ul>\n<h4>2.2.1 - 2018-11-28</h4>\n<ul>\n<li>New: Added <code>ACF File</code> Dynamic tag to support text controls.</li>\n<li>Tweak: Added option to hide item count bubble when cart is empty in Menu Cart widget (<a href=\"https://github.com/elementor/elementor/issues/6223\">#6223</a>)</li>\n<li>Tweak: Added Actions group for Lightbox and Contact URL tags</li>\n<li>Tweak: Added filter <code>elementor_pro/dynamic_tags/shortcode/should_escape</code> to avoid escaping in Shortcode dynamic tag</li>\n<li>Tweak: MailPoet3 integration allow Subscriber to to subscribe to multiple lists</li>\n<li>Tweak: Added front-end max file size validation for upload fields</li>\n<li>Tweak: Added <code>by-author</code> per Post-Type condition for theme builder</li>\n<li>Fix: Template widget panel not showing the selected template (<a href=\"https://github.com/elementor/elementor/issues/6271\">#6271</a>)</li>\n<li>Fix: Conflict between ACF with Safari browser on Select option in Dynamic tag</li>\n<li>Fix: Add post classes only for the Single template</li>\n<li>Fix: Set document type as not editable for unsupported document like Global widget</li>\n<li>Fix: Avoid duplicate query for current WC product query</li>\n<li>Fix: Product Archive showing oldest products instead of latest</li>\n<li>Fix: CSS reset in Posts widget using cards skin</li>\n</ul>\n<h4>2.2.0 - 2018-11-19</h4>\n<ul>\n<li>New: Introducing Custom Attributes (<a href=\"https://github.com/elementor/elementor/issues/290\">#290</a>, <a href=\"https://github.com/elementor/elementor/issues/3990\">#3990</a>)</li>\n<li>New: Added evergreen option for Countdown widget (<a href=\"https://github.com/elementor/elementor/issues/4459\">#4459</a>)</li>\n<li>New: Added expire actions option for Countdown widget (<a href=\"https://github.com/elementor/elementor/issues/5242\">#5242</a>)</li>\n<li>New: Introducing Reviews widget (<a href=\"https://github.com/elementor/elementor/issues/3854\">#3854</a>)</li>\n<li>New: Introducing Sitemap widget (<a href=\"https://github.com/elementor/elementor/issues/5594\">#5594</a>)</li>\n<li>New: Added Request Parameter dynamic tag (<a href=\"https://github.com/elementor/elementor/issues/4934\">#4934</a>)</li>\n<li>New: Added Shortcode dynamic tag</li>\n<li>New: Added Image and Video Lightbox dynamic tag</li>\n<li>New: Added Contact URL dynamic tag</li>\n<li>New: Added Featured Image Data dynamic tag</li>\n<li>New: Added default value to each field in the Form widget (<a href=\"https://github.com/elementor/elementor/issues/4268\">#4268</a>)</li>\n<li>New: Added &quot;Any Child Of&quot; condition to template conditions (<a href=\"https://github.com/elementor/elementor/issues/5321\">#5321</a>)</li>\n<li>New: Added &quot;In Child&quot; condition to template conditions (<a href=\"https://github.com/elementor/elementor/issues/5587\">#5587</a>)</li>\n<li>Tweak: Added Form Redirect URL with form values (<a href=\"https://github.com/elementor/elementor/issues/2564\">#2564</a>)</li>\n<li>Tweak: Added default post classes to template wrapper (<a href=\"https://github.com/elementor/elementor/issues/5959\">#5959</a>)</li>\n<li>Tweak: Better labels for terms in Query control (<a href=\"https://github.com/elementor/elementor/issues/6092\">#6092</a>)</li>\n<li>Tweak: Renamed &quot;Child Of&quot; templates condition to &quot;Direct Child Of&quot;</li>\n<li>Tweak: Added <code>elementor/theme/get_location_templates/condition_sub_id</code> filter hook to allow template condition translations</li>\n<li>Tweak: Load the Template Library widget via Ajax for better performance</li>\n<li>Tweak: Added 404 page title for Page Title dynamic tag</li>\n<li>Fix: Menu Cart Toggle has # URL link (<a href=\"https://github.com/elementor/elementor/issues/6141\">#6141</a>)</li>\n<li>Fix: Alignment issue in Nav Menu widget (<a href=\"https://github.com/elementor/elementor/issues/5790\">#5790</a>)</li>\n<li>Fix: Avoid potential security risk in forms</li>\n<li>Fix: Template By Author condition conflicts with 404 page</li>\n<li>Fix: Restored WC Product Content widget in Single Product template</li>\n<li>Fix: Theme Builder Preview URLs for date archives and 404 pages</li>\n<li>Fix: Highlight active menu anchor items only when scrolled into view</li>\n<li>Fix: Carousel Pagination Progress style to support new Swiper version</li>\n</ul>\n<h4>2.1.13 - 2018-11-12</h4>\n<ul>\n<li>Tweak: Added compatibility for new brand Finder in v2.3.0</li>\n<li>Fix: Settings conflict when there are multiple carousels in the page</li>\n</ul>\n<h4>2.1.12 - 2018-11-05</h4>\n<ul>\n<li>Tweak: Added compatibility for the upcoming release of Elementor v2.3</li>\n<li>Tweak: Better performance for Template Library widget</li>\n<li>Fix: Fatal error if a taxonomy used in a dynamic field is removed (<a href=\"https://github.com/elementor/elementor/issues/6029\">#6029</a>)</li>\n<li>Fix: Date Time dynamic tag now respect site language (<a href=\"https://github.com/elementor/elementor/issues/6001\">#6001</a>)</li>\n<li>Fix: Custom CSS printed twice in the front-end</li>\n<li>Fix: ACF Image field PHP warning (<a href=\"https://github.com/elementor/elementor/issues/6051\">#6051</a>)</li>\n</ul>\n<h4>2.1.11 - 2018-10-22</h4>\n<ul>\n<li>New: Added ACF local fields compatibility</li>\n<li>Tweak: Re-brand TypeKit by Adobe Fonts integration</li>\n<li>Fix: Exclude <code>is_embed</code> from Singular condition (<a href=\"https://github.com/elementor/elementor/issues/5915\">#5915</a>)</li>\n<li>Fix: Avoid conflict with Ad Blockers and Share Buttons</li>\n<li>Fix: Current date time dynamic tag now shows local time</li>\n<li>Fix: Avoid conflict with 3rd party plugins that filter the permalink</li>\n<li>Fix: Avoid PHP warning when no groups are selected for MailChimp integration</li>\n<li>Fix: Avoid PHP warning if checkbox field is empty for ACF</li>\n<li>Fix: Respect password protected for a WC single product template</li>\n<li>Fix: Respect <code>order</code> settings for WC archive also without pagination</li>\n</ul>\n<h4>2.1.10 - 2018-10-09</h4>\n<ul>\n<li>Tweak: Added responsive alignment control for Share Buttons widget (<a href=\"https://github.com/elementor/elementor/issues/5821\">#5821</a>)</li>\n<li>Tweak: Added link control to Animated Headline widget</li>\n<li>Fix: Mobile nav menu jump on RTL (<a href=\"https://github.com/elementor/elementor/issues/5711\">#5711</a>)</li>\n<li>Fix: Responsive alignment control in Add to Cart widget (<a href=\"https://github.com/elementor/elementor/issues/5830\">#5830</a>)</li>\n<li>Fix: Added IE compatibility for Animated Headline widget</li>\n<li>Fix: Post Content widget is now shown only on <code>Single</code> templates</li>\n<li>Fix: Query Control Pagination with offset</li>\n</ul>\n<h4>2.1.9 - 2018-09-17</h4>\n<ul>\n<li>Tweak: Added Centered Slides option for Slideshow carousel</li>\n<li>Fix: Allow only public CPT for Manual Selection in Query Control (<a href=\"https://github.com/elementor/elementor/issues/5091\">#5091</a>)</li>\n<li>Fix: ACF Gallery option support (<a href=\"https://github.com/elementor/elementor/issues/5344\">#5344</a>)</li>\n<li>Fix: Page scrolling on resize when sticky is active (<a href=\"https://github.com/elementor/elementor/issues/5740\">#5740</a>)</li>\n<li>Fix: Edit custom name for Global Widget in the Navigator (<a href=\"https://github.com/elementor/elementor/issues/5689\">#5689</a>)</li>\n<li>Fix: Coverflow transition effect in Carousel</li>\n<li>Fix: Weird mobile behavior with Cube effect in Carousel</li>\n<li>Fix: Show the first thumbnail in the Slideshow carousel correctly</li>\n</ul>\n<h4>2.1.8 - 2018-09-12</h4>\n<ul>\n<li>Tweak: Added styling options for WC Additional Information widget</li>\n<li>Tweak: Added styling options for \'View Cart\' link in Products widget</li>\n<li>Fix: 3rd party plugin support for WC single product template (<a href=\"https://github.com/elementor/elementor/issues/5338\">#5338</a>)</li>\n<li>Fix: Layout of Related Product widget with WC native style</li>\n</ul>\n<h4>2.1.7 - 2018-09-03</h4>\n<ul>\n<li>New: WC Archive Description widget</li>\n<li>Tweak: Added blend mode to Slides widget background overlay (<a href=\"https://github.com/elementor/elementor/issues/5555\">#5555</a>)</li>\n<li>Tweak: Added \'Current Subcategories\' option to Product Categories widget</li>\n<li>Fix: Added default vertical alignment in Author Box widget (<a href=\"https://github.com/elementor/elementor/issues/5589\">#5589</a>)</li>\n<li>Tweak: Added more blend mode options for CTA widget</li>\n<li>Tweak: Improved plugin updater method based on WordPress version</li>\n<li>Fix: Improved IE compatibility for Posts and Portfolio widgets</li>\n<li>Fix: Added default gap for products pagination</li>\n<li>Fix: Post thumbnail flickering in Safari browser</li>\n<li>Fix: Close mobile nav menu on click only in full-width mode</li>\n<li>Fix: Added trailing slash to pagination links in Posts widget</li>\n</ul>\n<h4>2.1.6 - 2018-08-28</h4>\n<ul>\n<li>New: WC Product Category Image widget and Dynamic tag (<a href=\"https://github.com/elementor/elementor/issues/5117\">#5117</a>)</li>\n<li>Tweak: Allow HTML in Excerpt widget (<a href=\"https://github.com/elementor/elementor/issues/5491\">#5491</a>)</li>\n<li>Tweak: Added compatibility for the upcoming release of Elementor v2.2</li>\n<li>Tweak: Deprecated Follow option in the Facebook Button widget</li>\n<li>Fix: Posts widget grid in Safari &amp; IE11 (Depended on Elementor v2.2)</li>\n<li>Fix: Posts widget CSS when using cards skin in masonry mode</li>\n<li>Fix: ACF Image &amp; ACF URL option support (<a href=\"https://github.com/elementor/elementor/issues/5344\">#5344</a>)</li>\n<li>Fix: WC product gallery links in RTL</li>\n<li>Fix: Dynamic tags in Call To Action widget</li>\n</ul>\n<h4>2.1.5 - 2018-08-21</h4>\n<ul>\n<li>Tweak: Added compatibility for the upcoming release of Elementor v2.2</li>\n<li>Fix: Posts Widget layout theme compatibility</li>\n<li>Fix: Added compatibility for WooCommerce native style</li>\n</ul>\n<h4>2.1.4 - 2018-08-19</h4>\n<ul>\n<li>Fix: Layout issue compatibility with themes caused by v2.1 (<a href=\"https://github.com/elementor/elementor/issues/5442\">#5442</a>)</li>\n<li>Fix: Dynamic setting in Pricing Table widget (<a href=\"https://github.com/elementor/elementor/issues/5460\">#5460</a>)</li>\n<li>Fix: Hide Target URL control if is not necessary in Blockquote widget</li>\n<li>Fix: Selector specificity for WooCommerce Products widget</li>\n<li>Fix: WooCommerce conflicts in the editor in edge cases</li>\n</ul>\n<h4>2.1.3 - 2018-08-15</h4>\n<ul>\n<li>Fix: Thumbnails in the Posts widget jumping (<a href=\"https://github.com/elementor/elementor/issues/5350\">#5350</a>)</li>\n<li>Fix: Responsive grid in the Share Buttons widget (<a href=\"https://github.com/elementor/elementor/issues/5375\">#5375</a>)</li>\n<li>Fix: Added missing <code>setup_postdata</code> for Product Data Tabs widget</li>\n<li>Fix: Rollback to older version of Flip Box widget to resolve 3D depth issue (<a href=\"https://github.com/elementor/elementor/issues/5399\">#5399</a>)</li>\n<li>Fix: Allowed types in the Upload File field are now case-insensitive (<a href=\"https://github.com/elementor/elementor/issues/5254\">#5254</a>)</li>\n<li>Fix: Carousel behavior when using a single slide</li>\n</ul>\n<h4>2.1.2 - 2018-08-12</h4>\n<ul>\n<li>Fix: Error when ACF Pro is not installed (<a href=\"https://github.com/elementor/elementor/issues/5367\">#5367</a>)</li>\n<li>Fix: Edge cases in Inspector where document is a boolean</li>\n<li>Fix: Edge cases for incorrect file fields in PODS</li>\n</ul>\n<h4>2.1.1 - 2018-08-09</h4>\n<ul>\n<li>Fix: Highlighted text in Animated Headline widget (<a href=\"https://github.com/elementor/elementor/issues/5345\">#5345</a>)</li>\n<li>Fix: Flip Box effect issues</li>\n<li>Fix: ACF Options page fields support (<a href=\"https://github.com/elementor/elementor/issues/5329\">#5329</a>)</li>\n<li>Fix: Import Pro templates in edge cases</li>\n</ul>\n<h4>2.1.0 - 2018-08-07</h4>\n<ul>\n<li>New: Introducing WooCommerce Builder (<a href=\"https://github.com/elementor/elementor/issues/1690\">#1690</a>)</li>\n<li>New: Introducing 12 new dynamic tags &amp; widgets for WooCommerce: Gallery, Image, Price, Rating, Description, Breadcrumbs, Data Tabs, Stock, Related, Upsell, Title &amp; Archive</li>\n<li>New: Introducing Cart Menu widget (<a href=\"https://github.com/elementor/elementor/issues/4220\">#4220</a>, <a href=\"https://github.com/elementor/elementor/issues/4600\">#4600</a>)</li>\n<li>New: Added integration with Toolset (<a href=\"https://github.com/elementor/elementor/issues/2949\">#2949</a>)</li>\n<li>New: Added integration with Pods (<a href=\"https://github.com/elementor/elementor/issues/4129\">#4129</a>)</li>\n<li>New: Added stick to bottom in scrolling effects (<a href=\"https://github.com/elementor/elementor/issues/4799\">#4799</a>)</li>\n<li>New: Added Scrolling Effect to Widgets under advanced tab</li>\n<li>New: Introducing Internal URL Dynamic Tag</li>\n<li>Tweak: Added a Last Updated Date in the Post Info widget (<a href=\"https://github.com/elementor/elementor/issues/4597\">#4597</a>)</li>\n<li>Tweak: Added Redirect after Logout option for Login widget (<a href=\"https://github.com/elementor/elementor/issues/4447\">#4447</a>)</li>\n<li>Tweak: Avoid repeating posts when using more than one in the Posts widget (<a href=\"https://github.com/elementor/elementor/issues/1878\">#1878</a>)</li>\n<li>Tweak: Add Custom Query hook for Query control (<a href=\"https://developers.elementor.com/custom-query-filter/\">More Info</a>) (<a href=\"https://github.com/elementor/elementor/issues/1748\">#1748</a>)</li>\n<li>Tweak: Added form-message style (<a href=\"https://github.com/elementor/elementor/issues/1180\">#1180</a>)</li>\n<li>Tweak: Added dynamic tag for button on the Price Table widget (<a href=\"https://github.com/elementor/elementor/issues/4242\">#4242</a>)</li>\n<li>Tweak: Added dynamic tag for Call to action widget (<a href=\"https://github.com/elementor/elementor/issues/4767\">#4767</a>)</li>\n<li>Tweak: Added Dynamic Tags support for Google Map field (<a href=\"https://github.com/elementor/elementor/issues/4602\">#4602</a>)</li>\n<li>Tweak: Added an support for <code>label|value</code> in options field (<a href=\"https://github.com/elementor/elementor/issues/4594\">#4594</a>)</li>\n<li>Tweak: Added <code>by-author</code> condition for theme builder (<a href=\"https://github.com/elementor/elementor/issues/4681\">#4681</a>)</li>\n<li>Tweak: Added Activate/Deactivate license key via WP-CLI command (<a href=\"https://github.com/elementor/elementor/issues/4149\">#4149</a>)</li>\n<li>Tweak: Added <code>is_scroll</code> trigger to scrolling effect (<a href=\"https://github.com/elementor/elementor/issues/4340\">#4340</a>)</li>\n<li>Tweak: Added In Same Term support for Post Navigation widget (<a href=\"https://github.com/elementor/elementor/issues/4177\">#4177</a>)</li>\n<li>Tweak: Added responsive control for Slides To Scroll control in all carousel widgets (<a href=\"https://github.com/elementor/elementor/issues/3697\">#3697</a>)</li>\n<li>Tweak: Added style options for Posts widget (<a href=\"https://github.com/elementor/elementor/issues/1335\">#1335</a>)</li>\n<li>Tweak: Added button CSS ID for Forms widget</li>\n<li>Tweak: Added pixel units to Post-Info divider height control</li>\n<li>Tweak: Rewrite sticky library to handle with stretch section, auto scroller &amp; more bugs</li>\n<li>Tweak: Re-organize the panel categories per document type</li>\n<li>Tweak: Added ACF support for <code>options-page</code> fields</li>\n<li>Tweak: Added dynamic tag for Animated headlines</li>\n<li>Tweak: Added dynamic tag for BlockQuote widget</li>\n<li>Fix: Elementor Full Width template in GeneratePress theme (<a href=\"https://github.com/elementor/elementor/issues/4817\">#4817</a>)</li>\n<li>Fix: Checkbox fields can accidentally be set to required (<a href=\"https://github.com/elementor/elementor/issues/4324\">#4324</a>)</li>\n<li>Fix: Initial slide in Carousel widget</li>\n<li>Fix: Stay on current slide while editing in Carousel widget</li>\n<li>Fix: Default slides per device in Carousel widget</li>\n<li>Deprecated: Woo Products, Woo Elements &amp; Single elements widgets</li>\n</ul>\n<h4>2.0.18 - 2018-07-27</h4>\n<ul>\n<li>Fix: Global widget error on saving page</li>\n</ul>\n<h4>2.0.17 - 2018-07-26</h4>\n<ul>\n<li>Fix: Sub menu indicator direction in Nav Menu widget</li>\n<li>Fix: Change the title and icon for Global Widget when is moving</li>\n<li>Fix: CSS wrapper selector for Page Document</li>\n</ul>\n<h4>2.0.16 - 2018-07-16</h4>\n<ul>\n<li>Tweak: CSS Filter Control module is now included in Elementor</li>\n<li>Fix: Border gap in Portfolio widget when item gap set as <code>0</code> (<a href=\"https://github.com/elementor/elementor/issues/5077\">#5077</a>)</li>\n<li>Fix: Restore current query after get Global Widget data</li>\n<li>Fix: Add action item in History on unlink Global widget</li>\n</ul>\n<h4>2.0.15 - 2018-07-10</h4>\n<ul>\n<li>Fix: Dropdown menu items collapsing when activated (<a href=\"https://github.com/elementor/elementor/issues/4996\">#4996</a>)</li>\n<li>Fix: GMT offset in Countdown widget (<a href=\"https://github.com/elementor/elementor/issues/4997\">#4997</a>)</li>\n</ul>\n<h4>2.0.14 - 2018-07-08</h4>\n<ul>\n<li>Tweak: Added set method to form record for developers (<a href=\"https://github.com/elementor/elementor/issues/4983\">#4983</a>)</li>\n<li>Fix: Autoplay option for Carousels</li>\n<li>Fix: Close mobile menu on item click in the Nav Menu widget</li>\n</ul>\n<h4>2.0.13 - 2018-07-03</h4>\n<ul>\n<li>Tweak: Added compatibility for Elementor v2.1</li>\n</ul>\n<h4>2.0.12 - 2018-07-02</h4>\n<ul>\n<li>Fix: Global widget PHP notices</li>\n<li>Fix: Slides widget active slide lost focus when clicking Editor tabs</li>\n<li>Fix: Form select field send all selected values on multiple selection</li>\n<li>Fix: Validate time field only if it\'s not empty</li>\n<li>Fix: ConvertKit API not saving name field</li>\n</ul>\n<h4>2.0.11 - 2018-06-12</h4>\n<ul>\n<li>Fix: Theme Builder <code>author</code> archive condition (<a href=\"https://github.com/elementor/elementor/issues/4593\">#4593</a>)</li>\n<li>Fix: Respect password protected posts in Post Content widget</li>\n<li>Fix: Custom Fonts redirect to post edit screen in edge cases.</li>\n</ul>\n<h4>2.0.10 - 2018-06-05</h4>\n<ul>\n<li>Tweak: Added <code>elementor/theme/get_location_templates/template_id</code> filter hook for multi-language plugins</li>\n<li>Fix: Dynamic Post Terms missing taxonomies if the taxonomy is registered to more then one post types (#4386)</li>\n<li>Fix: Fields shortcode missing after removing a field in Form widget</li>\n<li>Deprecated: <code>get_theme_templates_by_location</code> is replaced by <code>get_location_templates</code></li>\n</ul>\n<h4>2.0.9 - 2018-05-28</h4>\n<ul>\n<li>Fix: Compatibility for PHP version 5.4</li>\n</ul>\n<h4>2.0.8 - 2018-05-28</h4>\n<ul>\n<li>Tweak: Added Active state for Nav Menu dropdown</li>\n<li>Tweak: Added style for &quot;Nothing Found&quot; Message for Archive Posts widget</li>\n<li>Tweak: Removed caption control in Site Logo widget</li>\n<li>Tweak: Added option to position currency symbol before/after In Price Table widget</li>\n<li>Fix: Query control manual selection does not show more than 10 items (<a href=\"https://github.com/elementor/elementor/issues/4479\">#4479</a>)</li>\n<li>Fix: Styling glitch with terms list in Post Info widget (<a href=\"https://github.com/elementor/elementor/issues/4342\">#4342</a>)</li>\n<li>Fix: Sub terms missing in Query control in edge cases (<a href=\"https://github.com/elementor/elementor/issues/4527\">#4527</a>)</li>\n<li>Fix: Avoid rendering a template if it\'s not published</li>\n<li>Fix: 404 Page style not working</li>\n<li>Fix: Price Table button with hover animation not working in editor</li>\n<li>Fix: Styling conflict in Call to Action widget</li>\n<li>Fix: Global Widget tab translation</li>\n<li>Fix: Adding parent wrapper class to Site Title widget</li>\n</ul>\n<h4>2.0.7 - 2018-05-16</h4>\n<ul>\n<li>Fix: Content not found on section when single is set to &quot;All Singular&quot;</li>\n<li>Fix: Open 404 template library for 404 page</li>\n<li>Tweak: Added CSS prefix for dev files</li>\n<li>Tweak: Removed product post type from display conditions</li>\n</ul>\n<h4>2.0.6 - 2018-05-15</h4>\n<ul>\n<li>Tweak: Set type on create new single template</li>\n<li>Tweak: Always show the conditions dialog in the Draft status</li>\n<li>Tweak: Added document type <code>widget</code></li>\n<li>Tweak: Added Post Custom Field tag to URL category</li>\n<li>Fix: When ACF Field Groups are Empty (<a href=\"https://github.com/elementor/elementor/issues/4428\">#4428</a>)</li>\n<li>Fix: Links inside carousel in edge cases</li>\n<li>Fix: Responsive issue in My Templates area</li>\n<li>Fix: Image alignment for post content with text alignment</li>\n<li>Fix: Post Content widget when preview post is missing</li>\n<li>Fix: Global Widget tab translation</li>\n<li>Fix: Style settings for Post / Archive Title widgets</li>\n</ul>\n<h4>2.0.5 - 2018-05-08</h4>\n<ul>\n<li>Fix: Creating a CPT with name like document-type breaks the editor (<a href=\"https://github.com/elementor/elementor/issues/4203\">#4203</a>)</li>\n<li>Fix: Added support for new version of reCAPTCHA</li>\n<li>Fix: Added fallback for controls after <code>post_status</code></li>\n<li>Fix: Required field in forms widget</li>\n<li>Fix: Media Carousel in the Coverflow skin</li>\n<li>Fix: 404 Page show wrong template in edge cases</li>\n<li>Fix: Save the default menu in the Nav Menu widget</li>\n</ul>\n<h4>2.0.4 - 2018-05-02</h4>\n<ul>\n<li>Tweak: Added parent\'s class for extended widgets</li>\n<li>Tweak: Set entire-site as default to avoid conflict with save without conditions</li>\n<li>Tweak: Initialize global model when it\'s needed</li>\n<li>Tweak: Removed some duplicate strings</li>\n<li>Tweak: Query control now includes empty terms</li>\n<li>Tweak: Design polish for conditions dialog</li>\n<li>Tweak: Decreasing <code>minimumInputLength</code> to 1 of select2</li>\n<li>Fix: Editor not loading for single templates in edge cases</li>\n<li>Fix: Select2 in Safari takes it\'s time to get the original select width (<a href=\"https://github.com/elementor/elementor/issues/4310\">#4310</a>)</li>\n<li>Fix: Slides per view not working for some effects</li>\n<li>Fix: New slides not showing in the editor</li>\n<li>Fix: Editor for section without a defined location, defaults to content area</li>\n</ul>\n<h4>2.0.3 - 2018-04-24</h4>\n<ul>\n<li>Tweak: Optimize CSS for Post Info widget (<a href=\"https://github.com/elementor/elementor/issues/4214\">#4214</a>, <a href=\"https://github.com/elementor/elementor/issues/4216\">#4216</a>, <a href=\"https://github.com/elementor/elementor/issues/4225\">#4225</a>)</li>\n<li>Fix: Double render on frontend view in core locations</li>\n<li>Fix: Masonry not working in edge cases</li>\n<li>Fix: Added default setting for Author Info tag</li>\n</ul>\n<h4>2.0.2 - 2018-04-18</h4>\n<ul>\n<li>Fix: Regenerate conditions to include all templates</li>\n</ul>\n<h4>2.0.1 - 2018-04-17</h4>\n<ul>\n<li>Tweak: Added div wrapper for Nothing Found massage (<a href=\"https://github.com/elementor/elementor/issues/4136\">#4136</a>)</li>\n<li>Tweak: Show empty categories in Query Control &amp; Display Conditions (<a href=\"https://github.com/elementor/elementor/issues/4127\">#4127</a>)</li>\n<li>Tweak: Added Divider control for Post Info widget</li>\n<li>Fix: Update admin links in Yoast Breadcrumbs widget</li>\n<li>Fix: Sticky element conflict with clearfix CSS</li>\n<li>Fix: Compatibility for PHP version 5.4.32 &amp; 5.5.16 and below</li>\n<li>Fix: Avoid running <code>wp_head</code> hooks twice</li>\n</ul>\n<h4>2.0.0 - 2018-04-16</h4>\n<ul>\n<li>New: Introducing Theme Builder - <a href=\"https://elementor.com/introducing-theme-builder/\">Release Post</a> (<a href=\"https://github.com/elementor/elementor/issues/417\">#417</a>)</li>\n<li>New: Introducing Locations API to inject custom location templates</li>\n<li>New: Introducing Display Conditions for all dynamic templates</li>\n<li>New: Introducing Dynamic Tag feature - a new way to add dynamic content to your design</li>\n<li>New: Introducing Role manager to allow &quot;Content Only mode&quot; (<a href=\"https://github.com/elementor/elementor/issues/483\">#483</a>, <a href=\"https://github.com/elementor/elementor/issues/653\">#653</a>, <a href=\"https://github.com/elementor/elementor/issues/885\">#885</a>)</li>\n<li>New: Introducing 9 new dynamic widgets: Archive Posts, Archive Title, Post Content, Post Info, Post Title, Post Excerpt, Featured Image, Site Logo &amp; Site Name (<a href=\"https://github.com/elementor/elementor/issues/543\">#543</a>)</li>\n<li>New: Introducing Developers area with guides and API documentation - <a href=\"https://elementor.com/introducing-elementor-developer-api/\">Release Post</a> (<a href=\"https://github.com/elementor/elementor/issues/451\">#451</a>)</li>\n<li>New: Introducing <a href=\"https://github.com/elementor/elementor-hello-theme\">Elementor Hello Theme</a> - A demonstration theme for developers</li>\n<li>New: Added new type of templates: Header, Footer, Single and Archive (<a href=\"https://github.com/elementor/elementor/issues/2761\">#2761</a>, <a href=\"https://github.com/elementor/elementor/issues/2623\">#2623</a>, <a href=\"https://github.com/elementor/elementor/issues/2109\">#2109</a>, <a href=\"https://github.com/elementor/elementor/issues/2061\">#2061</a>, <a href=\"https://github.com/elementor/elementor/issues/2439\">#2439</a>)</li>\n<li>New: Design 404 page with Single template (<a href=\"https://github.com/elementor/elementor/issues/1558\">#1558</a>)</li>\n<li>New: Design Search Results with Archive template (<a href=\"https://github.com/elementor/elementor/issues/3196\">#3196</a>, <a href=\"https://github.com/elementor/elementor/issues/2590\">#2590</a>)</li>\n<li>New: Added Scrolling Effect for sections including <em>Sticky Element</em> per device (<a href=\"https://github.com/elementor/elementor/issues/2412\">#2412</a>)</li>\n<li>New: Integration with Custom Fields (<a href=\"https://github.com/elementor/elementor/issues/2054\">#2054</a>)</li>\n<li>New: Partial support for Toolset integration (<a href=\"https://github.com/elementor/elementor/issues/2949\">#2949</a>)</li>\n<li>New: Partial support for Pods integration (<a href=\"https://github.com/elementor/elementor/issues/2169\">#2169</a>)</li>\n<li>New: Partial support for ACF integration (<a href=\"https://github.com/elementor/elementor/issues/2041\">#2041</a>, <a href=\"https://github.com/elementor/elementor/issues/2059\">#2059</a>)</li>\n<li>Tweak: Add custom fields support for ActiveCampaign (<a href=\"https://github.com/elementor/elementor/issues/3531\">#3531</a>)</li>\n<li>Tweak: Allow brackets in Forms Tel field</li>\n<li>Tweak: Added currency format control for Price Table widget</li>\n<li>Tweak: Reduced API request for some servers</li>\n<li>Fix: Dropdown <code>border-radius</code> in Nav Menu widget</li>\n<li>Fix: Price List widget layout breaks in edge cases</li>\n<li>Note: This version requires Elementor v2.0.6</li>\n</ul>\n<h4>1.15.6 - 2018-03-28</h4>\n<ul>\n<li>Fix: Removed duplicate Custom CSS section (<a href=\"https://github.com/elementor/elementor/issues/3938\">#3938</a>)</li>\n<li>Fix: <code>box-shadow</code> issue with cards skin (<a href=\"https://github.com/elementor/elementor/issues/3940\">#3940</a>)</li>\n</ul>\n<h4>1.15.5 - 2018-03-27</h4>\n<ul>\n<li>Fix: Added global widget compatibility for Elementor v2.0</li>\n<li>Fix: Reduced API request for some servers</li>\n</ul>\n<h4>1.15.4 - 2018-03-26</h4>\n<ul>\n<li>Tweak: Allow brackets in phone field</li>\n<li>Tweak: Added compatibility with Yoast 7.0.+</li>\n<li>Tweak: Added compatibility for the future release of Elementor v2.0</li>\n<li>Fix: Support for multiple carousel setting in editor</li>\n<li>Fix: <code>on_export</code> issue in forms widget (<a href=\"https://github.com/elementor/elementor/issues/3890\">#3890</a>)</li>\n</ul>\n<h4>1.15.3 - 2018-03-07</h4>\n<ul>\n<li>Tweak: Added unique class to field group div (<a href=\"https://github.com/elementor/elementor/issues/3595\">#3595</a>)</li>\n<li>Fix: Screen Options missing when Pro is active (<a href=\"https://github.com/elementor/elementor/issues/3622\">#3622</a>)</li>\n<li>Fix: Allow label styling even when <code>show labels</code> is set hide (<a href=\"https://github.com/elementor/elementor/issues/3544\">#3544</a>)</li>\n<li>Fix: Typography control not working in edge cases</li>\n<li>Fix: Safari compatibility for Search widget</li>\n</ul>\n<h4>1.15.2 - 2018-02-27</h4>\n<ul>\n<li>Fix: Only add support mine-type if needed (<a href=\"https://github.com/elementor/elementor/issues/3543\">#3543</a>)</li>\n<li>Fix: Better support for Old Typekit kits</li>\n</ul>\n<h4>1.15.1 - 2018-02-21</h4>\n<ul>\n<li>Tweak: Custom font title placeholder is not <code>enter font family</code></li>\n<li>Tweak: Custom font title set as required</li>\n<li>Fix: Custom font, <code>font-face</code> enqueued only once if used in global (<a href=\"https://github.com/elementor/elementor/issues/3513\">#3513</a>)</li>\n<li>Fix: Added workaround for upload validation which relies on a PHP extension (fileinfo) with inconsistent reporting behavior.</li>\n</ul>\n<h4>1.15.0 - 2018-02-19</h4>\n<ul>\n<li>New: Added custom fonts manager for self hosted fonts (<a href=\"https://github.com/elementor/elementor/issues/852\">#852</a>)</li>\n<li>New: Integration with Adobe TypeKit fonts (<a href=\"https://github.com/elementor/elementor/issues/631\">#631</a>)</li>\n<li>Tweak: Clear menu from Nav Menu widget on template export</li>\n<li>Tweak: Allow zero for GetResponse integration as <code>day of cycle</code></li>\n</ul>\n<h4>1.14.2 - 2018-02-13</h4>\n<ul>\n<li>Fix: Global widget content that got affected by previous update</li>\n</ul>\n<h4>1.14.1 - 2018-02-13</h4>\n<ul>\n<li>Tweak: Added <code>none</code> option to content animation in CTA widget</li>\n<li>Tweak: Added <code>form_id</code> to ActiveCampaign integration (<a href=\"https://github.com/elementor/elementor/issues/3422\">#3422</a>)</li>\n<li>Fix: Page crashed when Global widget not found.</li>\n</ul>\n<h4>1.14.0 - 2018-02-12</h4>\n<ul>\n<li>New: Added Call to Action widget</li>\n<li>Tweak: MailPoet pull field mapping from MailPoet instead of hardcoded</li>\n<li>Tweak: Added compatibility for the future release of Elementor v2.0</li>\n<li>Fix: Allow zero (0) to be accepted as a field value</li>\n<li>Fix: Login form when custom login URL is set</li>\n<li>Fix: Added Day of cycle control to GetResponse integration</li>\n</ul>\n<h4>1.13.2 - 2018-01-23</h4>\n<ul>\n<li>Tweak: Added placeholder to Password field</li>\n<li>Tweak: Removed <code>subscriber_already_exists_message</code> control to prevent potential data leakage</li>\n<li>Fix: MailPoet Subscriber Already Exists error validation against translated string directly from MailPoet</li>\n<li>Fix: Changed <code>imagesLoaded()</code> to Vanilla JS to avoid compatibility issues with some themes</li>\n<li>Fix: Only validate Tel field if not empty</li>\n<li>Fix: Stop slider while editing</li>\n</ul>\n<h4>1.13.1 - 2018-01-16</h4>\n<ul>\n<li>Fix: Added compatibility with old PHP versions</li>\n</ul>\n<h4>1.13.0 - 2018-01-16</h4>\n<ul>\n<li>New: Added File Upload field for Forms widget (<a href=\"https://github.com/elementor/elementor/issues/1482\">#1482</a>, <a href=\"https://github.com/elementor/elementor/issues/2974\">#2974</a>)</li>\n<li>New: Added Acceptance field for Forms widget (<a href=\"https://github.com/elementor/elementor/issues/1693\">#1693</a>, <a href=\"https://github.com/elementor/elementor/issues/2974\">#2974</a>)</li>\n<li>New: Added Date field for Forms widget (<a href=\"https://github.com/elementor/elementor/issues/1868\">#1868</a>)</li>\n<li>New: Added Time field for Forms widget</li>\n<li>New: Added Password field for Forms widget (<a href=\"https://github.com/elementor/elementor/issues/2164\">#2164</a>)</li>\n<li>New: Added HTML field for Forms widget (<a href=\"https://github.com/elementor/elementor/issues/1500\">#1500</a>)</li>\n<li>Tweak: Added characters validation for Tel field</li>\n<li>Tweak: Added min &amp; max validation for Number field</li>\n<li>Tweak: Added multiple selection for Select field</li>\n<li>Tweak: Added donReach integration for Share Buttons widget</li>\n</ul>\n<h4>1.12.3 - 2018-01-09</h4>\n<ul>\n<li>Fix: Render element plain content instead of parsed content when not needed in global widget</li>\n<li>Fix: Apply <code>url-encoding</code> to &quot;Tweet&quot; button text in Blockquote widget to prevent unexpected corruption of the tweet text</li>\n<li>Fix: Removed My Account link from dashboard widget</li>\n</ul>\n<h4>1.12.2 - 2018-01-03</h4>\n<ul>\n<li>Tweak: Added animation none for Nav Menu widget (<a href=\"https://github.com/elementor/elementor/issues/2964\">#2964</a>)</li>\n<li>Fix: Active license button style</li>\n</ul>\n<h4>1.12.1 - 2018-01-02</h4>\n<ul>\n<li>Tweak: Removed theme-element widgets from plain content</li>\n<li>Tweak: Set all theme-element widgets to extend same widget Base</li>\n<li>Tweak: Removed credit URL in forms meta data</li>\n<li>Tweak: Added compatibility for the future release of Elementor v1.9</li>\n<li>Fix: Validate Get response Error as real error</li>\n<li>Fix: Removed responsive height control from Facebook Page widget</li>\n</ul>\n<h4>1.12.0 - 2017-12-20</h4>\n<ul>\n<li>New: Added Drip integration to Forms</li>\n<li>New: Added ActiveCampaign integration to Forms</li>\n<li>New: Added ConverKit integration to Forms</li>\n<li>New: Added GetResponse integration to Forms</li>\n<li>New: Added form <code>id</code>, <code>name</code> attributes to handle integration with auto collectors like HubSpot</li>\n<li>New: Added Global API key for MailChimp to improve the workflow</li>\n<li>Tweak: Better error handling and message display for Forms</li>\n<li>Fix: PHP notice Undefined variable <code>$cc_header</code> (<a href=\"https://github.com/elementor/elementor/issues/2934\">#2934</a>)</li>\n</ul>\n<h4>1.11.0 - 2017-12-11</h4>\n<ul>\n<li>New: Added a native Comments widget (<a href=\"https://github.com/elementor/elementor/issues/543\">#543</a>)</li>\n<li>New: Added an Author Box widget</li>\n<li>New: Added a Post Navigation widget</li>\n<li>New: Added a Yoast Breadcrumbs widget (<a href=\"https://github.com/elementor/elementor/issues/2749\">#2749</a>)</li>\n<li>Tweak: Added a close button to search widget under Full Screen skin (<a href=\"https://github.com/elementor/elementor/issues/2762\">#2762</a>)</li>\n<li>Fix: Allow currency symbol to appear even if price isn\'t numeric</li>\n<li>Fix: Edge cases when the nav menu is empty in a stretched section</li>\n<li>Fix: Added fallback when you remove the <code>space-between</code> on Swiper carousel</li>\n</ul>\n<h4>1.10.2 - 2017-12-03</h4>\n<ul>\n<li>Fix: Missing save widget icon (<a href=\"https://github.com/elementor/elementor/issues/2878\">#2878</a>)</li>\n<li>Fix: Global widgets not saving edits (<a href=\"https://github.com/elementor/elementor/issues/2874\">#2874</a>)</li>\n<li>Fix: Removed <code>white-space: nowrap;</code> property from vertical menu in Nav Menu widget (<a href=\"https://github.com/elementor/elementor/issues/2815\">#2815</a>)</li>\n</ul>\n<h4>1.10.1 - 2017-11-30</h4>\n<ul>\n<li>Tweak: Added default value for search form</li>\n<li>Tweak: Order template list A-Z in the library widget</li>\n<li>Tweak: get_users/authors query is now done using AJAX only, for better performance in Query Control (<a href=\"https://github.com/elementor/elementor/issues/2865\">#2865</a>)</li>\n<li>Fix: When adding <code>.00</code> it is not displayed on the front</li>\n<li>Fix: Make sure space between is numeric for carousel control</li>\n<li>Fix: Added space for radio &amp; checkbox fields in form widget</li>\n</ul>\n<h4>1.10.0 - 2017-11-15</h4>\n<ul>\n<li>New: Added native Search form widget (<a href=\"https://github.com/elementor/elementor/issues/2576\">#2576</a>)</li>\n<li>Tweak: Added Slides To Scroll &amp; Loop controls to Media Carousel and Testimonials widgets</li>\n<li>Tweak: Added Inline editing to Blockquote widget</li>\n<li>Fix: Animated Headline color bug (<a href=\"https://github.com/elementor/elementor/issues/2516\">#2516</a>)</li>\n<li>Fix: Animated Headline with Rotating skin</li>\n<li>Fix: RTL fix for Animated Headline widget in \'typing\' and \'clip\' animations</li>\n<li>Fix: Empty menu cause jQuery to crash in Menu widget (<a href=\"https://github.com/elementor/elementor/issues/2662\">#2662</a>)</li>\n<li>Fix: Custom CSS gone after reloading the editor</li>\n</ul>\n<h4>1.9.5 - 2017-10-27</h4>\n<ul>\n<li>Fix: Broken Global widget with JS (<a href=\"https://github.com/elementor/elementor/issues/2639\">#2639</a>)</li>\n</ul>\n<h4>1.9.4 - 2017-10-24</h4>\n<ul>\n<li>Tweak: Improved UI for notices and license page</li>\n<li>Fix: Update system conflict with other EDD plugins</li>\n<li>Fix: WooCommerce frontend hooks on Elementor editor (<a href=\"https://github.com/elementor/elementor/issues/2577\">#2577</a>)</li>\n<li>Fix: Removed default border left in Nav Menu dropdown CSS (<a href=\"https://github.com/elementor/elementor/issues/2496\">#2496</a>)</li>\n<li>Fix: Increased submenu max-width (<a href=\"https://github.com/elementor/elementor/issues/2558\">#2558</a>)</li>\n<li>Fix: Save global templates without their defaults</li>\n<li>Fix: Horizontal scrolling issue with posts grid</li>\n</ul>\n<h4>1.9.3 - 2017-10-03</h4>\n<ul>\n<li>Fix: Condition slide style that got affected by previous update</li>\n</ul>\n<h4>1.9.2 - 2017-10-02</h4>\n<ul>\n<li>New: Added integration with MailPoet 3 for Forms actions</li>\n<li>Fix: Removed height control from Testimonial carousel in mobile editing mode</li>\n<li>Fix: Removed bottom padding when there\'s no pagination in Testimonial carousel</li>\n<li>Fix: Added condition for slides style section in skin bubble mode</li>\n<li>Fix: Slides per view control for mobile editing in Testimonial carousel</li>\n<li>Fix: Navigation Arrows icons matched with common Elementor Navigation Arrows</li>\n</ul>\n<h4>1.9.1 - 2017-09-28</h4>\n<ul>\n<li>Fix: Slides per view for slideshow carousel</li>\n<li>Fix: Final polish for the new Testimonial Carousel widget</li>\n<li>Fix: Don\'t play video if slide type is not video</li>\n<li>Fix: Removed slides style section condition (<a href=\"https://github.com/elementor/elementor/issues/2497\">#2497</a>)</li>\n<li>Fix: Set cursor as pointer for slideshow thumbnails</li>\n</ul>\n<h4>1.9.0 - 2017-09-26</h4>\n<ul>\n<li>New: Added Media Carousel widget (<a href=\"https://github.com/elementor/elementor/issues/216\">#216</a>, <a href=\"https://github.com/elementor/elementor/issues/347\">#347</a>, <a href=\"https://github.com/elementor/elementor/issues/2209\">#2209</a>)</li>\n<li>New: Added Testimonial Carousel widget (<a href=\"https://github.com/elementor/elementor/issues/715\">#715</a>)</li>\n</ul>\n<h4>1.8.3 - 2017-09-24</h4>\n<ul>\n<li>Fix: Added compatibility for WordPress 4.8.2 &amp; 4.7.6</li>\n<li>Fix: Remove slashes from Form sent data</li>\n</ul>\n<h4>1.8.2 - 2017-09-19</h4>\n<ul>\n<li>Tweak: Added target URL for the tweet message in Blockquote widget</li>\n<li>Tweak: Render the slide height before the slider is finished loading</li>\n<li>Fix: Space between words for Animated Headline widget</li>\n<li>Fix: RTL compatibility for Animated Headline widget</li>\n<li>Fix: Italic font style for Animated Headline widget</li>\n<li>Fix: Excluded Menu widget from the WP Editor text rendering</li>\n</ul>\n<h4>1.8.1 - 2017-09-18</h4>\n<ul>\n<li>Fix: WCAG Compatible &quot;required&quot; field attribute for W3C validation (<a href=\"https://github.com/elementor/elementor/issues/2391\">#2391</a>)</li>\n<li>Fix: Print the main menu only when is necessary in Menu widget</li>\n<li>Fix: Use CSS media query instead of JS to hide items in Menu widget to avoid flickering on page load (<a href=\"https://github.com/elementor/elementor/issues/2381\">#2381</a>)</li>\n</ul>\n<h4>1.8.0 - 2017-09-12</h4>\n<ul>\n<li>New: Added Nav Menu widget (<a href=\"https://github.com/elementor/elementor/issues/1406\">#1406</a>)</li>\n<li>Fix: Field ID for checkbox control in Form widget (<a href=\"https://github.com/elementor/elementor/issues/2279\">#2279</a>)</li>\n<li>Fix: Style for Blockquote widget included</li>\n</ul>\n<h4>1.7.2 - 2017-09-07</h4>\n<ul>\n<li>Tweak: Loading Facebook SDK via JS for better compatibility with caching plugins</li>\n<li>Fix: Responsive Embed Facebook post widget for Safari iOS (<a href=\"https://github.com/elementor/elementor/issues/2340\">#2340</a>)</li>\n</ul>\n<h4>1.7.1 - 2017-09-05</h4>\n<ul>\n<li>Fix: Facebook SDK version</li>\n</ul>\n<h4>1.7.0 - 2017-09-05</h4>\n<ul>\n<li>New: Added Facebook Button widget for Like, Recommend, Share and Follow</li>\n<li>New: Added Facebook Embed widget for Post, Video and Comment</li>\n<li>New: Added Facebook Comments widget</li>\n<li>New: Added Facebook Page widget (Previously known as Like Box)</li>\n<li>New: Added Blockquote widget with Tweet button</li>\n<li>Tweak: Added Facebook SDK integration for all Facebook widgets</li>\n<li>Fix: Animated headline rotating with long words</li>\n</ul>\n<h4>1.6.1 - 2017-08-28</h4>\n<ul>\n<li>Fix: Animated Headline marker gets in front of neighboring spans even when &quot;Bring to Front&quot; is not set</li>\n<li>Fix: Stroke animation in Animated Headline for MS Edge browser</li>\n<li>Fix: Animated headline with more than 1-word per rotation</li>\n<li>Fix: Animated Headline in two lines</li>\n<li>Fix: Some errors in Global widget</li>\n</ul>\n<h4>1.6.0 - 2017-08-22</h4>\n<ul>\n<li>New: Added Animated Headline widget</li>\n<li>New: Added Hidden field for Forms widget (<a href=\"https://github.com/elementor/elementor/issues/2038\">#2038</a>)</li>\n<li>Tweak: Added notice to update Elementor to v1.6.5 or higher</li>\n<li>Fix: CSS Animations names no longer minified, in order to prevent unexpected conflicts</li>\n</ul>\n<h4>1.5.9 - 2017-08-16</h4>\n<ul>\n<li>Tweak: Added compatibility for the future release of Elementor v1.7</li>\n<li>Fix: Portfolio compatibility for GeneratePress theme</li>\n<li>Fix: Portfolio filter compatibility for RTL</li>\n<li>Fix: Pagination apply for all posts widget in the page</li>\n<li>Fix: Global form widget with MailChimp integration not saving</li>\n</ul>\n<h4>1.5.8 - 2017-07-25</h4>\n<ul>\n<li>Tweak: Added compatibility for the future release of Elementor v1.6</li>\n<li>Fix: Improved backward compatibility for query control rename</li>\n</ul>\n<h4>1.5.7 - 2017-07-24</h4>\n<ul>\n<li>Tweak: Moved JS render of reCAPTCHA to a separate file</li>\n<li>Tweak: Display the label in the reCAPTCHA field for better experience</li>\n<li>Tweak: Rename <code>panel-posts-control</code> to <code>query-control</code> and added fallback support</li>\n<li>Tweak: Added compatibility for the future release of Elementor with history feature</li>\n<li>Fix: reCAPTCHA preview on the editor</li>\n<li>Fix: Manual selection (query control) has stopped working after saving (<a href=\"https://github.com/elementor/elementor/issues/2000\">#2000</a>)</li>\n<li>Fix: Added condition for icon size control in Share Buttons widget</li>\n</ul>\n<h4>1.5.6 - 2017-07-12</h4>\n<ul>\n<li>Fix: Query Control correction for taxonomies (<a href=\"https://github.com/elementor/elementor/issues/1963\">#1963</a>)</li>\n<li>Fix: Custom CSS override scheme color in the editor</li>\n<li>Fix: Added order by Menu Order for Query Control in WC widget</li>\n<li>Fix: Glitch with Flip Box background overlay</li>\n</ul>\n<h4>1.5.5 - 2017-07-03</h4>\n<ul>\n<li>Tweak: Moved reCAPTCHA render to handler &amp; load only if a form is exist</li>\n<li>Fix: MailChimp integration: Default number of items returned by API increased to 999</li>\n<li>Fix: MailChimp integration: Refresh the groups list if API is changed</li>\n<li>Fix: Sorted items in filter bar by A-Z</li>\n<li>Fix: Editor glitch with Elementor v1.5 (<a href=\"https://github.com/elementor/elementor/issues/1927\">#1927</a>)</li>\n</ul>\n<h4>1.5.4 - 2017-06-22</h4>\n<ul>\n<li>Tweak: Improved compatibility for Elementor v1.5</li>\n<li>Fix: URL default for Add To Cart widget</li>\n<li>Fix: Allowed <code>date</code> and <code>birthday</code> fields as text for MailChimp integration</li>\n</ul>\n<h4>1.5.3 - 2017-06-19</h4>\n<ul>\n<li>Tweak: Make flip-box height responsive control</li>\n<li>Fix: Facebook share count now gets retrieved by Elementor (<a href=\"https://github.com/elementor/elementor/issues/1829\">#1829</a>)</li>\n<li>Fix: Global form widget with MailChimp integration not saving</li>\n</ul>\n<h4>1.5.2 - 2017-06-13</h4>\n<ul>\n<li>Fix: Custom CSS panel location compatibility for the old versions</li>\n</ul>\n<h4>1.5.1 - 2017-06-12</h4>\n<ul>\n<li>Fix: MailChimp update existing user registration</li>\n<li>Fix: Global widget with JS in the editor mode</li>\n<li>Fix: Label section condition in Login widget</li>\n<li>Fix: Changes to unlinked global widget do not appear in the editor</li>\n</ul>\n<h4>1.5.0 - 2017-05-23</h4>\n<ul>\n<li>New: Added Cards, a new skin for Posts widget</li>\n<li>New: Added Exclude option to post query control group</li>\n<li>Tweak: Added <code>post_class()</code> for each post in the loop</li>\n<li>Tweak: Added <code>.elementor-posts-masonry</code> class when Masonry layout is enabled</li>\n<li>Tweak: Added compatibility for the next release of Elementor v1.5.0</li>\n<li>Tweak: CSS <code>autoprefixer</code> now supports last 5 versions of browsers</li>\n<li>Tweak: Added <code>imageLoaded</code> library for Posts &amp; Portfolio widgets</li>\n</ul>\n<h4>1.4.4 - 2017-05-18</h4>\n<ul>\n<li>Fix: Force Mailchimp API to return all lists and not just 10 (<a href=\"https://github.com/elementor/elementor/issues/1683\">#1683</a>)</li>\n<li>Fix: Added <code>.elementor-form</code> class to Login form to fix style glitch</li>\n</ul>\n<h4>1.4.3 - 2017-05-14</h4>\n<ul>\n<li>Tweak: Added Redirect After Login option to Login widget</li>\n<li>Tweak: Stay in the current page after logout in Login widget</li>\n<li>Tweak: Preparation for Elementor settings tabs in future version</li>\n<li>Fix: Pinterest in Share Buttons widget now sharing the URL alone</li>\n<li>Fix: Bug with <code>active</code> class in portfolio filter item</li>\n<li>Fix: Higher specific list-style-type <code>none</code> for filter items to override some theme style</li>\n</ul>\n<h4>1.4.2 - 2017-05-06</h4>\n<ul>\n<li>Fix: Temporary patch for form field shortcode in some servers</li>\n</ul>\n<h4>1.4.1 - 2017-05-03</h4>\n<ul>\n<li>Fix: Bug with custom success message in form widget</li>\n<li>Fix: Bug with meta data in email action</li>\n</ul>\n<h4>1.4.0 - 2017-05-03</h4>\n<ul>\n<li>New: Forms: integration with MailChimp</li>\n<li>New: Forms: integration with MailPoet</li>\n<li>New: Forms: Added Email 2 action for email confirmation</li>\n<li>New: Forms: Added shortcodes for fields</li>\n<li>New: Forms: Added custom ID for fields</li>\n<li>New: Forms: Added option to edit email HTML template (<a href=\"https://github.com/elementor/elementor/issues/1180\">#1180</a>)</li>\n<li>New: Added Login widget</li>\n<li>Tweak: Move <code>send_html</code> control to <code>email_content_type</code></li>\n<li>Fix: Email still sent even if validation failed in form widget</li>\n</ul>\n<h4>1.3.2 - 2017-05-01</h4>\n<ul>\n<li>New: Added action <code>elementor_pro/init</code> for better integration with Elementor Pro</li>\n<li>Fix: Posts without featured image in Posts widget (<a href=\"https://github.com/elementor/elementor/issues/1234\">#1234</a>, <a href=\"https://github.com/elementor/elementor/issues/1382\">#1382</a>)</li>\n<li>Fix: reCAPTCHA &amp; Honeypot fields with new method</li>\n<li>Fix: Added border width control in Share Buttons to avoid a glitch on Chrome browser</li>\n<li>Fix: Border radius glitch on hover in Share Buttons</li>\n</ul>\n<h4>1.3.1 - 2017-04-25</h4>\n<ul>\n<li>Fix: Conflict update with revision history module</li>\n</ul>\n<h4>1.3.0 - 2017-04-25</h4>\n<ul>\n<li>New: Added Share Buttons widget (<a href=\"https://wordpress.org/support/topic/social-sharing-buttons-is-it-possible/\">Topic</a>)</li>\n<li>New: Added Custom CSS for Page Settings</li>\n<li>New: Added Masonry layout for Portfolio widget</li>\n<li>New: Added Cc &amp; Bcc options to email action (<a href=\"https://github.com/elementor/elementor/issues/1181\">#1181</a>)</li>\n<li>New: Introduced <code>ElementorPro\\Modules\\Forms\\Classes\\Action_Base</code> class for better 3rd party integration for forms</li>\n<li>Tweak: Debugger module now also shows errors from Pro</li>\n<li>Tweak: Added options for Elementor Library</li>\n<li>Tweak: New base posts module for optimized performance</li>\n<li>Tweak: Adjusting Posts / Portfolio to the new structure</li>\n<li>Fix: Export for posts / portfolio</li>\n<li>Fix: Duplicate repeater field with switcher control (<a href=\"https://github.com/elementor/elementor/issues/1442\">#1442</a>)</li>\n<li>Fix: Post per Page in the query control</li>\n<li>Fix: Metadata does not come through on form emails (<a href=\"https://github.com/elementor/elementor/issues/1566\">#1566</a>)</li>\n</ul>\n<h4>1.2.6 - 2017-04-19</h4>\n<ul>\n<li>Fix: Added compatibility with WooCommerce 3.0 - Products &amp; Add to Cart widgets</li>\n</ul>\n<h4>1.2.5 - 2017-04-18</h4>\n<ul>\n<li>Fix: Offset query for posts widgets (Posts, Portfolio and Products)</li>\n</ul>\n<h4>1.2.4 - 2017-03-21</h4>\n<ul>\n<li>Tweak: Added Indian Rupee sign to Price Table widget</li>\n<li>Fix: Portfolio grid for IE11</li>\n<li>Fix: Link target blank in Price List widget</li>\n<li>Fix: Active item for filter bar in Portfolio widget</li>\n</ul>\n<h4>1.2.3 - 2017-03-06</h4>\n<ul>\n<li>Tweak: Fully compatible with Elementor v1.3.0</li>\n<li>Tweak: Added trigger for after form submission in Forms widget</li>\n<li>Tweak: Changed handle name in reCAPTCHA field to avoid conflict with other contact forms</li>\n<li>Fix: Portfolio filter syntax in Non-Latin languages</li>\n<li>Fix: Added <code>no-repeat</code> property for slide with <code>background-size:contain</code></li>\n<li>Fix: Condition control &amp; Import value in Posts widgets</li>\n<li>Fix: Offset and Pagination in WordPress (<a href=\"https://codex.wordpress.org/Making_Custom_Queries_using_Offset_and_Pagination\">More Info</a>)</li>\n<li>Fix: Submit handler bubbling for custom events in Forms widget</li>\n</ul>\n<h4>1.2.2 - 2017-02-23</h4>\n<ul>\n<li>Tweak: Change name from Side A/B to Front and Back in Flip Box widget</li>\n<li>Fix: Error when saving third party widgets in the global widget</li>\n<li>Fix: Image position &quot;none&quot; remains visible in editor preview (Posts)</li>\n<li>Fix: Hide the pagination when there are no links</li>\n</ul>\n<h4>1.2.1 - 2017-02-21</h4>\n<ul>\n<li>Fix: Firefox Flip Box 3D compatibility</li>\n</ul>\n<h4>1.2.0 - 2017-02-21</h4>\n<ul>\n<li>New: Added Flip Box widget</li>\n<li>New: Added Ken Burns effect for slides</li>\n<li>New: Added Masonry layout for Posts widget</li>\n<li>New: Added Pagination option for Posts widget</li>\n<li>Tweak: Added background size contain to slides</li>\n<li>Tweak: Improve Query control by preload items</li>\n<li>Fix: Text color for Checkbox and Radio fields</li>\n</ul>\n<h4>1.1.2 - 2017-02-05</h4>\n<ul>\n<li>Tweak: Added <code>aria-required</code> for better accessibility in forms widget</li>\n<li>Fix: Conflict Call to <code>undefined</code> method in Posts &amp; Portfolio widgets (<a href=\"https://github.com/elementor/elementor/issues/1271\">#1271</a>, <a href=\"https://github.com/elementor/elementor/issues/1266\">#1266</a>)</li>\n<li>Fix: Submit button HTML after error sending</li>\n<li>Fix: Success message for <code>skip_email</code> function</li>\n<li>Notice: Elementor 1.2.0 or later now required</li>\n</ul>\n<h4>1.1.1 - 2017-01-24</h4>\n<ul>\n<li>Fix: Can\'t save global widgets when <code>WP_DEBUG</code> is <code>true</code></li>\n<li>Fix: Undefined variable in WC widgets</li>\n<li>Fix: Removed duplicate strings</li>\n</ul>\n<h4>1.1.0 - 2017-01-24</h4>\n<ul>\n<li>New: Price Table widget (<a href=\"https://github.com/elementor/elementor/issues/102\">#102</a>)</li>\n<li>New: WooCommerce Add to Cart widget</li>\n<li>New: WooCommerce Categories widget</li>\n<li>New: WooCommerce Elements widget</li>\n<li>New: Honeypot field for Forms widgets</li>\n<li>Tweak: Added inline options for taxonomies &amp; authors if is less than 15 items</li>\n<li>Tweak: Added Required Mark for fields in Forms widget</li>\n<li>Fix: CSS selectors priority in Slides widget</li>\n<li>Fix: CSS bug in Price List widget</li>\n<li>Fix: Update all Post CSS files that includes specific Global Widget</li>\n</ul>\n<h4>1.0.9 - 2017-01-18</h4>\n<ul>\n<li>Fix: Auto complete bug in query controls</li>\n<li>Fix: Render template with escaping slashes</li>\n<li>Fix: Reply-to field in Forms widget</li>\n</ul>\n<h4>1.0.8 - 2017-01-11</h4>\n<ul>\n<li>Tweak: Code adjustments for Elementor API</li>\n<li>Fix: Removed go pro link from plugins page in admin</li>\n</ul>\n<h4>1.0.7 - 2017-01-05</h4>\n<ul>\n<li>Tweak: Added filter by featured / sale for WC Products widget</li>\n<li>Tweak: Added author control in Portfolio widget</li>\n<li>Tweak: Code adjustments for Elementor API</li>\n<li>Fix: Added support for empty image ratio</li>\n<li>Fix: Avoid nesting a sidebar within a template that will appear in the sidebar itself</li>\n</ul>\n<h4>1.0.6 - 2017-01-01</h4>\n<ul>\n<li>Tweak: Added Auto-updates for local translation files</li>\n<li>Fix: Custom CSS for Global widgets</li>\n<li>Fix: Remove <code>nonce</code> field (Fix some cache plugins)</li>\n</ul>\n<h4>1.0.5 - 2016-12-27</h4>\n<ul>\n<li>Fix: Slide element bug fix - \'Link apply on\' logic</li>\n<li>Fix: Removed unique wrapper for Custom CSS in order to allow media queries (<a href=\"https://github.com/elementor/elementor/issues/1086\">#1086</a>)</li>\n</ul>\n<h4>1.0.4 - 2016-12-21</h4>\n<ul>\n<li>Tweak: Mobile Editing for fields in the form widget</li>\n<li>Tweak: Mobile Editing for posts</li>\n<li>Tweak: Allow send form as HTML</li>\n<li>Tweak: Improved auto upgrades for Multisite installation</li>\n<li>Tweak: Improve editor rendering experience for Portfolio widget</li>\n<li>Fix: Posts widget check if image exist</li>\n<li>Fix: Changed the clone method for global widget (<a href=\"https://github.com/elementor/elementor/issues/1042\">#1042</a>)</li>\n<li>Fix: Bug slides in RTL (removed direction control)</li>\n<li>Fix: Slides with no height jumps when changing slides</li>\n</ul>\n<h4>1.0.3 - 2016-12-13</h4>\n<ul>\n<li>Fix: Added escape placeholder for HTML Entities in form widget</li>\n<li>Fix: Countdown widget RTL bug</li>\n<li>Fix: Remove redundant #elementor selector for control style</li>\n<li>Fix: Added prefixing with \'0\' for one digit number in Countdown widget</li>\n</ul>\n<h4>1.0.2 - 2016-12-12</h4>\n<ul>\n<li>Fix: Page layout collapses when inserting reCAPTCHA field in Form</li>\n</ul>\n<h4>1.0.1 - 2016-12-12</h4>\n<ul>\n<li>Fix: WordPress widgets disappear from Editor when Elementor Pro active</li>\n</ul>\n<h4>1.0.0 - 2016-12-12</h4>\n<ul>\n<li>Initial release</li>\n</ul>\";}\";s:11:\"new_version\";s:5:\"3.0.6\";s:4:\"name\";s:13:\"Elementor Pro\";s:4:\"slug\";s:13:\"elementor-pro\";s:3:\"url\";s:36:\"https://elementor.com/pro/changelog/\";s:8:\"homepage\";s:26:\"https://elementor.com/pro/\";s:8:\"requires\";s:3:\"5.0\";s:18:\"elementor_requires\";s:5:\"3.0.1\";s:6:\"tested\";s:5:\"5.5.1\";s:7:\"package\";s:188:\"http://my.elementor.com/edd-sl/package_download/MTYwNTE0MDQyNDozMzFiZmU3Y2RiMjQ0N2FkM2QxMzI4NTY4NzJmZWFiZjoxOmFkNzlmZmEwZGQ1YWQ3MDEzNTJhMTEyYjYyYjRhNmM1Omh0dHBALy9zYWNrYWJhcmUuYWMua2U6MA==\";s:13:\"download_link\";s:188:\"http://my.elementor.com/edd-sl/package_download/MTYwNTE0MDQyNDozMzFiZmU3Y2RiMjQ0N2FkM2QxMzI4NTY4NzJmZWFiZjoxOmFkNzlmZmEwZGQ1YWQ3MDEzNTJhMTEyYjYyYjRhNmM1Omh0dHBALy9zYWNrYWJhcmUuYWMua2U6MA==\";s:7:\"banners\";a:2:{s:2:\"2x\";s:65:\"https://ps.w.org/elementor/assets/banner-1544x500.png?rev=1475479\";s:2:\"1x\";s:64:\"https://ps.w.org/elementor/assets/banner-772x250.png?rev=1475479\";}s:5:\"icons\";a:1:{s:3:\"svg\";s:42:\"https://ps.w.org/elementor/assets/icon.svg\";}s:17:\"canary_deployment\";a:2:{s:11:\"plugin_info\";a:12:{s:11:\"new_version\";s:5:\"3.0.2\";s:4:\"name\";s:13:\"Elementor Pro\";s:4:\"slug\";s:13:\"elementor-pro\";s:3:\"url\";s:36:\"https://elementor.com/pro/changelog/\";s:8:\"homepage\";s:26:\"https://elementor.com/pro/\";s:8:\"requires\";s:3:\"5.0\";s:18:\"elementor_requires\";s:5:\"3.0.1\";s:6:\"tested\";s:5:\"5.5.1\";s:7:\"package\";s:193:\"http://my.elementor.com/edd-sl/previous_download/MTYwNTE0MDQyNDozMzFiZmU3Y2RiMjQ0N2FkM2QxMzI4NTY4NzJmZWFiZjoxOjMuMC4yOmI4ZWI4M2EwZmM2ZWRjMWE4YTQzNTFiZTA1MWJkMjExOmh0dHBALy9zYWNrYWJhcmUuYWMua2U=\";s:13:\"download_link\";s:193:\"http://my.elementor.com/edd-sl/previous_download/MTYwNTE0MDQyNDozMzFiZmU3Y2RiMjQ0N2FkM2QxMzI4NTY4NzJmZWFiZjoxOjMuMC4yOmI4ZWI4M2EwZmM2ZWRjMWE4YTQzNTFiZTA1MWJkMjExOmh0dHBALy9zYWNrYWJhcmUuYWMua2U=\";s:7:\"banners\";a:2:{s:2:\"2x\";s:65:\"https://ps.w.org/elementor/assets/banner-1544x500.png?rev=1475479\";s:2:\"1x\";s:64:\"https://ps.w.org/elementor/assets/banner-772x250.png?rev=1475479\";}s:5:\"icons\";a:1:{s:3:\"svg\";s:42:\"https://ps.w.org/elementor/assets/icon.svg\";}}s:10:\"conditions\";a:1:{i:0;a:1:{i:0;a:4:{s:4:\"type\";s:6:\"plugin\";s:6:\"plugin\";s:23:\"elementor/elementor.php\";s:7:\"version\";s:5:\"3.0.2\";s:8:\"operator\";s:2:\">=\";}}}}}', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(1176, '_transient_timeout_elementor_remote_info_api_data_3.0.10', '1605097289', 'no'),
(1177, '_transient_elementor_remote_info_api_data_3.0.10', 'a:4:{s:9:\"timestamp\";s:10:\"1605052227\";s:14:\"upgrade_notice\";a:3:{s:7:\"version\";s:5:\"2.0.0\";s:7:\"message\";s:0:\"\";s:11:\"update_link\";s:0:\"\";}s:11:\"pro_widgets\";a:59:{i:0;a:4:{s:4:\"name\";s:5:\"posts\";s:5:\"title\";s:5:\"Posts\";s:4:\"icon\";s:15:\"eicon-post-list\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:1;a:4:{s:4:\"name\";s:9:\"portfolio\";s:5:\"title\";s:9:\"Portfolio\";s:4:\"icon\";s:18:\"eicon-gallery-grid\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:2;a:4:{s:4:\"name\";s:7:\"gallery\";s:5:\"title\";s:7:\"Gallery\";s:4:\"icon\";s:23:\"eicon-gallery-justified\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:3;a:4:{s:4:\"name\";s:4:\"form\";s:5:\"title\";s:4:\"Form\";s:4:\"icon\";s:21:\"eicon-form-horizontal\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:4;a:4:{s:4:\"name\";s:5:\"login\";s:5:\"title\";s:5:\"Login\";s:4:\"icon\";s:15:\"eicon-lock-user\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:5;a:4:{s:4:\"name\";s:6:\"slides\";s:5:\"title\";s:6:\"Slides\";s:4:\"icon\";s:12:\"eicon-slides\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:6;a:4:{s:4:\"name\";s:8:\"nav-menu\";s:5:\"title\";s:8:\"Nav Menu\";s:4:\"icon\";s:14:\"eicon-nav-menu\";s:10:\"categories\";s:33:\"[\"pro-elements\",\"theme-elements\"]\";}i:7;a:4:{s:4:\"name\";s:17:\"animated-headline\";s:5:\"title\";s:17:\"Animated Headline\";s:4:\"icon\";s:23:\"eicon-animated-headline\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:8;a:4:{s:4:\"name\";s:10:\"price-list\";s:5:\"title\";s:10:\"Price List\";s:4:\"icon\";s:16:\"eicon-price-list\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:9;a:4:{s:4:\"name\";s:11:\"price-table\";s:5:\"title\";s:11:\"Price Table\";s:4:\"icon\";s:17:\"eicon-price-table\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:10;a:4:{s:4:\"name\";s:8:\"flip-box\";s:5:\"title\";s:8:\"Flip Box\";s:4:\"icon\";s:14:\"eicon-flip-box\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:11;a:4:{s:4:\"name\";s:14:\"call-to-action\";s:5:\"title\";s:14:\"Call to Action\";s:4:\"icon\";s:20:\"eicon-image-rollover\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:12;a:4:{s:4:\"name\";s:14:\"media-carousel\";s:5:\"title\";s:14:\"Media Carousel\";s:4:\"icon\";s:20:\"eicon-media-carousel\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:13;a:4:{s:4:\"name\";s:20:\"testimonial-carousel\";s:5:\"title\";s:20:\"Testimonial Carousel\";s:4:\"icon\";s:26:\"eicon-testimonial-carousel\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:14;a:4:{s:4:\"name\";s:7:\"reviews\";s:5:\"title\";s:7:\"Reviews\";s:4:\"icon\";s:12:\"eicon-review\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:15;a:4:{s:4:\"name\";s:17:\"table-of-contents\";s:5:\"title\";s:17:\"Table of Contents\";s:4:\"icon\";s:23:\"eicon-table-of-contents\";s:10:\"categories\";s:33:\"[\"pro-elements\",\"theme-elements\"]\";}i:16;a:4:{s:4:\"name\";s:9:\"countdown\";s:5:\"title\";s:9:\"Countdown\";s:4:\"icon\";s:15:\"eicon-countdown\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:17;a:4:{s:4:\"name\";s:13:\"share-buttons\";s:5:\"title\";s:13:\"Share Buttons\";s:4:\"icon\";s:11:\"eicon-share\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:18;a:4:{s:4:\"name\";s:11:\"search-form\";s:5:\"title\";s:11:\"Search Form\";s:4:\"icon\";s:17:\"eicon-site-search\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:19;a:4:{s:4:\"name\";s:10:\"author-box\";s:5:\"title\";s:10:\"Author Box\";s:4:\"icon\";s:12:\"eicon-person\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:20;a:4:{s:4:\"name\";s:13:\"post-comments\";s:5:\"title\";s:13:\"Post Comments\";s:4:\"icon\";s:14:\"eicon-comments\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:21;a:4:{s:4:\"name\";s:15:\"post-navigation\";s:5:\"title\";s:15:\"Post Navigation\";s:4:\"icon\";s:21:\"eicon-post-navigation\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:22;a:4:{s:4:\"name\";s:9:\"post-info\";s:5:\"title\";s:9:\"Post Info\";s:4:\"icon\";s:15:\"eicon-post-info\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:23;a:4:{s:4:\"name\";s:7:\"sitemap\";s:5:\"title\";s:7:\"Sitemap\";s:4:\"icon\";s:13:\"eicon-sitemap\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:24;a:4:{s:4:\"name\";s:11:\"breadcrumbs\";s:5:\"title\";s:11:\"Breadcrumbs\";s:4:\"icon\";s:11:\"eicon-yoast\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:25;a:4:{s:4:\"name\";s:10:\"blockquote\";s:5:\"title\";s:10:\"Blockquote\";s:4:\"icon\";s:16:\"eicon-blockquote\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:26;a:4:{s:4:\"name\";s:19:\"wc-archive-products\";s:5:\"title\";s:16:\"Archive Products\";s:4:\"icon\";s:14:\"eicon-products\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:27;a:4:{s:4:\"name\";s:31:\"woocommerce-archive-description\";s:5:\"title\";s:19:\"Archive Description\";s:4:\"icon\";s:25:\"eicon-product-description\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:28;a:4:{s:4:\"name\";s:20:\"woocommerce-products\";s:5:\"title\";s:8:\"Products\";s:4:\"icon\";s:14:\"eicon-products\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:29;a:4:{s:4:\"name\";s:22:\"woocommerce-breadcrumb\";s:5:\"title\";s:23:\"WooCommerce Breadcrumbs\";s:4:\"icon\";s:25:\"eicon-product-breadcrumbs\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:30;a:4:{s:4:\"name\";s:14:\"wc-add-to-cart\";s:5:\"title\";s:18:\"Custom Add To Cart\";s:4:\"icon\";s:17:\"eicon-woocommerce\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:31;a:4:{s:4:\"name\";s:11:\"wc-elements\";s:5:\"title\";s:17:\"WooCommerce Pages\";s:4:\"icon\";s:19:\"eicon-product-pages\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:32;a:4:{s:4:\"name\";s:13:\"wc-categories\";s:5:\"title\";s:18:\"Product Categories\";s:4:\"icon\";s:24:\"eicon-product-categories\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:33;a:4:{s:4:\"name\";s:21:\"woocommerce-menu-cart\";s:5:\"title\";s:9:\"Menu Cart\";s:4:\"icon\";s:10:\"eicon-cart\";s:10:\"categories\";s:41:\"[\"theme-elements\",\"woocommerce-elements\"]\";}i:34;a:4:{s:4:\"name\";s:25:\"woocommerce-product-title\";s:5:\"title\";s:13:\"Product Title\";s:4:\"icon\";s:19:\"eicon-product-title\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:35;a:4:{s:4:\"name\";s:26:\"woocommerce-product-images\";s:5:\"title\";s:14:\"Product Images\";s:4:\"icon\";s:20:\"eicon-product-images\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:36;a:4:{s:4:\"name\";s:25:\"woocommerce-product-price\";s:5:\"title\";s:13:\"Product Price\";s:4:\"icon\";s:19:\"eicon-product-price\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:37;a:4:{s:4:\"name\";s:31:\"woocommerce-product-add-to-cart\";s:5:\"title\";s:11:\"Add To Cart\";s:4:\"icon\";s:25:\"eicon-product-add-to-cart\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:38;a:4:{s:4:\"name\";s:26:\"woocommerce-product-rating\";s:5:\"title\";s:14:\"Product Rating\";s:4:\"icon\";s:20:\"eicon-product-rating\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:39;a:4:{s:4:\"name\";s:25:\"woocommerce-product-stock\";s:5:\"title\";s:13:\"Product Stock\";s:4:\"icon\";s:19:\"eicon-product-stock\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:40;a:4:{s:4:\"name\";s:24:\"woocommerce-product-meta\";s:5:\"title\";s:12:\"Product Meta\";s:4:\"icon\";s:18:\"eicon-product-meta\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:41;a:4:{s:4:\"name\";s:37:\"woocommerce-product-short-description\";s:5:\"title\";s:17:\"Short Description\";s:4:\"icon\";s:25:\"eicon-product-description\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:42;a:4:{s:4:\"name\";s:29:\"woocommerce-product-data-tabs\";s:5:\"title\";s:17:\"Product Data Tabs\";s:4:\"icon\";s:18:\"eicon-product-tabs\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:43;a:4:{s:4:\"name\";s:42:\"woocommerce-product-additional-information\";s:5:\"title\";s:22:\"Additional Information\";s:4:\"icon\";s:19:\" eicon-product-info\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:44;a:4:{s:4:\"name\";s:27:\"woocommerce-product-related\";s:5:\"title\";s:15:\"Product Related\";s:4:\"icon\";s:21:\"eicon-product-related\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:45;a:4:{s:4:\"name\";s:26:\"woocommerce-product-upsell\";s:5:\"title\";s:7:\"Upsells\";s:4:\"icon\";s:20:\"eicon-product-upsell\";s:10:\"categories\";s:24:\"[\"woocommerce-elements\"]\";}i:46;a:4:{s:4:\"name\";s:15:\"facebook-button\";s:5:\"title\";s:15:\"Facebook Button\";s:4:\"icon\";s:23:\"eicon-facebook-like-box\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:47;a:4:{s:4:\"name\";s:17:\"facebook-comments\";s:5:\"title\";s:17:\"Facebook Comments\";s:4:\"icon\";s:23:\"eicon-facebook-comments\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:48;a:4:{s:4:\"name\";s:14:\"facebook-embed\";s:5:\"title\";s:14:\"Facebook Embed\";s:4:\"icon\";s:14:\"eicon-fb-embed\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:49;a:4:{s:4:\"name\";s:13:\"facebook-page\";s:5:\"title\";s:13:\"Facebook Page\";s:4:\"icon\";s:13:\"eicon-fb-feed\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:50;a:4:{s:4:\"name\";s:8:\"template\";s:5:\"title\";s:8:\"Template\";s:4:\"icon\";s:19:\"eicon-document-file\";s:10:\"categories\";s:16:\"[\"pro-elements\"]\";}i:51;a:4:{s:4:\"name\";s:15:\"theme-site-logo\";s:5:\"title\";s:9:\"Site Logo\";s:4:\"icon\";s:15:\"eicon-site-logo\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:52;a:4:{s:4:\"name\";s:16:\"theme-site-title\";s:5:\"title\";s:10:\"Site Title\";s:4:\"icon\";s:16:\"eicon-site-title\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:53;a:4:{s:4:\"name\";s:16:\"theme-page-title\";s:5:\"title\";s:10:\"Page Title\";s:4:\"icon\";s:19:\"eicon-archive-title\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:54;a:4:{s:4:\"name\";s:16:\"theme-post-title\";s:5:\"title\";s:10:\"Post Title\";s:4:\"icon\";s:16:\"eicon-post-title\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:55;a:4:{s:4:\"name\";s:18:\"theme-post-excerpt\";s:5:\"title\";s:12:\"Post Excerpt\";s:4:\"icon\";s:18:\"eicon-post-excerpt\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:56;a:4:{s:4:\"name\";s:25:\"theme-post-featured-image\";s:5:\"title\";s:14:\"Featured Image\";s:4:\"icon\";s:20:\"eicon-featured-image\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:57;a:4:{s:4:\"name\";s:19:\"theme-archive-title\";s:5:\"title\";s:13:\"Archive Title\";s:4:\"icon\";s:19:\"eicon-archive-title\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}i:58;a:4:{s:4:\"name\";s:13:\"archive-posts\";s:5:\"title\";s:13:\"Archive Posts\";s:4:\"icon\";s:19:\"eicon-archive-posts\";s:10:\"categories\";s:18:\"[\"theme-elements\"]\";}}s:17:\"canary_deployment\";a:2:{s:11:\"plugin_info\";a:11:{s:2:\"id\";s:23:\"w.org/plugins/elementor\";s:4:\"slug\";s:9:\"elementor\";s:6:\"plugin\";s:23:\"elementor/elementor.php\";s:11:\"new_version\";s:5:\"3.0.0\";s:7:\"package\";s:58:\"https://downloads.wordpress.org/plugin/elementor.3.0.0.zip\";s:3:\"url\";s:40:\"https://wordpress.org/plugins/elementor/\";s:5:\"icons\";a:3:{s:2:\"2x\";s:62:\"https://ps.w.org/elementor/assets/icon-256x256.png?rev=1427768\";s:2:\"1x\";s:54:\"https://ps.w.org/elementor/assets/icon.svg?rev=1426809\";s:3:\"svg\";s:54:\"https://ps.w.org/elementor/assets/icon.svg?rev=1426809\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:65:\"https://ps.w.org/elementor/assets/banner-1544x500.png?rev=1475479\";s:2:\"1x\";s:64:\"https://ps.w.org/elementor/assets/banner-772x250.png?rev=1475479\";}s:11:\"banners_rtl\";a:0:{}s:6:\"tested\";s:3:\"5.4\";s:12:\"requires_php\";s:3:\"5.6\";}s:10:\"conditions\";a:1:{i:0;a:1:{i:0;a:3:{s:4:\"type\";s:8:\"language\";s:9:\"languages\";a:26:{i:0;s:5:\"he_IL\";i:1;s:5:\"en_GB\";i:2;s:5:\"en_NZ\";i:3;s:5:\"en_ZA\";i:4;s:5:\"en_AU\";i:5;s:5:\"en_CA\";i:6;s:5:\"sv_SE\";i:7;s:5:\"da_DK\";i:8;s:5:\"fr_FR\";i:9;s:5:\"nl_NL\";i:10;s:5:\"nb_NO\";i:11;s:5:\"de_AT\";i:12;s:2:\"fi\";i:13;s:5:\"it_IT\";i:14;s:5:\"nn_NO\";i:15;s:5:\"de_CH\";i:16;s:5:\"en_GB\";i:17;s:5:\"is_IS\";i:18;s:2:\"ga\";i:19;s:5:\"fr_BE\";i:20;s:5:\"nl_BE\";i:21;s:3:\"ast\";i:22;s:5:\"lb_LU\";i:23;s:5:\"es_ES\";i:24;s:5:\"pt_PT\";i:25;s:3:\"mlt\";}s:8:\"operator\";s:2:\"in\";}}}}}', 'no'),
(1178, '_site_transient_timeout_theme_roots', '1605055893', 'no'),
(1179, '_site_transient_theme_roots', 'a:11:{s:5:\"astra\";s:7:\"/themes\";s:12:\"bfastmag_pro\";s:7:\"/themes\";s:13:\"education-hub\";s:7:\"/themes\";s:14:\"education-soul\";s:7:\"/themes\";s:8:\"edupress\";s:7:\"/themes\";s:15:\"hello-elementor\";s:7:\"/themes\";s:7:\"oceanwp\";s:7:\"/themes\";s:22:\"page-builder-framework\";s:7:\"/themes\";s:14:\"twentynineteen\";s:7:\"/themes\";s:15:\"twentyseventeen\";s:7:\"/themes\";s:12:\"twentytwenty\";s:7:\"/themes\";}', 'no');

-- --------------------------------------------------------

--
