For just $50, attendees will have access to everything throughout the three-day event, including more than 40 speaker presentations, workshops, “birds of a feather” meetups, and Contributor Day. The price also includes lunches, morning and afternoon snacks, admission to the WordFest party on Friday night, and a commemorative tee shirt with a surprise gift.
This year, parents bringing children children under 9 years old have a separate ticket option where they can indicate whether or not they are interested in on-site child care during the conference. There is no additional cost for selecting the “Parent with Kids” ticket option. Organizers are currently considering various options for childcare.
WordCamp is about diversity, this is not a catch phrase, it is not just a moment. It is about real people, doing real things, in the real world across gender, generation and culture. WordCamp embraces the world. #WordCamp #WordPress @WordCamp #WCUS pic.twitter.com/GdcCDNJYed
— WordCamp US (@WordCampUS) May 2, 2019
WordCamp US organizers have secured a block of hotel rooms at The Marriott St. Louis Grand with a special rate for conference attendees ($149/night). It is located directly across from the official venue. They anticipate the hotel block will sell out quickly. Attendees can follow the link from the WCUS website to reserve a room.
Attendee Services is now open, and this includes assistance with visa applications. Any prospective attendee who requires a visa may request a letter from WCUS organizers for the application. Requests must be made before September 1, 2019, in order to be processed in a timely way.
Speakers will be notified of their acceptance in June and the full schedule will not be announced until July. Volunteer applications will also open in July. Check out the WordCamp US 2019 Timeline to get a quick overview of what’s next and follow @WordCampUS on Twitter for all the latest.
WPTavern: WPCampus’ Gutenberg Accessibility Audit Finds “Significant and Pervasive Accessibility Problems”
WPCampus has published the results of the Gutenberg accessibility audit the organization commissioned from Tenon, LLC. The audit was crowdfunded by the WordPress community and Matt Mullenweg and Automattic pledged to cover the balance to ensure it would be fully funded.
Tenon’s analysis includes a 329-page technical audit of the editor along with user-based testing that included people with various disabilities. WPCampus’ announcement presents Tenon’s findings in a measured and diplomatic way, encouraging the community to use the report for improving WordPress:
Please use this report as what it is intended to be: constructive feedback in support of the WordPress project. We hope this report generates discussion about accessibility, excitement about inclusive design, and action toward improving the editing experience.
Beyond its use for WordPress core, the audit is also a valuable resource for those extending Gutenberg and more broadly for developers who are building React-based projects.
Tenon’s report includes a 34-page Executive Summary, highlighting key findings from the usability testing and technical review. It’s important to note that the audit was conducted on WordPress version 5.0.3 in January 2019. Since that time the Gutenberg and Accessibility teams have resolved an additional 116 accessibility issues, which will be included in WordPress 5.2 next week.
As expected, Tenon’s results show that overall the markup generated by Gutenberg is “clean, semantically correct and accessible” but that “Gutenberg’s user experience is consistently poor.” The audit found that Gutenberg fails to comply with all 30 of the WCAG 2.1 Success Criteria.
Tenon’s findings confirm the statement WordPress’ Accessibility Team published in October 2018 regarding the editor’s overall level of accessibility:
“The accessibility team will continue to work to support Gutenberg to the best of our ability. However, based on its current status, we cannot recommend that anybody who has a need for assistive technology allow it to be in use on any sites they need to use at this time.”
At that time, many WordPress contributors urged leadership not to ship an editor with critical accessibility issues that prevented people using assistive technologies from moving forward with the latest version.
Tenon’s Executive Summary concludes that the new editor is a step backwards for people with disabilities:
Gutenberg has significant and pervasive accessibility problems, the likes of which amount to a step backwards for users with disabilities over the legacy editor. Our user-based testing – backed by data from our technical review – indicates that the accessibility problems are severe in nature. We feel concerned that Gutenberg’s current accessibility issues will prove problematic for website owners who deploy Gutenberg to content creators in protected populations or for website owners who are themselves part of a protected population. Therefore, organizations which have high risk profiles should consult legal counsel before using it and may want to choose to use the legacy editor instead.
Tenon recommended that Gutenberg’s developers aggressively tackle the issues uncovered in the technical report, given the size of WordPress’ user base. The full report essentially functions as a guide for anyone who wants to contribute to the new editors’ accessibility. It is an excellent resource that outlines each issue with solutions and recommended code, making it easy for developers to get started with meaningful contributions right away. Tenon has created a collection of 84 issues on GitHub based on the findings in the audit and six of them have already been resolved/closed.
The second release candidate for WordPress 5.2 is now available!
WordPress 5.2 will be released on Tuesday, May 7, but we need your help to get there—if you haven’t tried 5.2 yet, now is the time!
There are two ways to test the WordPress 5.2 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip).
For details about what to expect in WordPress 5.2, please see the first release candidate post.
This release includes the final About page design. It also contains fixes for:
- Proper translation of the recovery mode notification emails (#47093).
- Improvements to the way Site Health works with multisite installs (#47084).
Please test your plugins and themes against WordPress 5.2 and update the Tested up to version in the readme to 5.2. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release.
The WordPress 5.2 Field Guide has also been published, which details the major changes.How to Help
Do you speak a language other than English? Help us translate WordPress into more than 100 languages!
If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
It’s the start of May
and the release is coming.
We all give a cheer!
This past month has been filled with anticipation as the community builds up towards a big new release, plans some important events, and builds new tools to grow the future of the project.WordPress 5.2 Almost Due for Release
WordPress 5.2 is due for release on May 7 with many new features included for developers and end-users alike. The Field Guide for the release provides a lot of information about what is in it and what you can expect, including a few key elements:Site Health Check
One of the most highly anticipated features for v5.2 is the Site Health Check. This feature adds two new pages in the admin interface to help end users maintain a healthy site through common configuration issues and other elements that go along with having a robust online presence. It also provides a standardized location for developers to add debugging information.Fatal Error Recovery Mode
The Fatal Error Recovery Mode feature was originally planned for the 5.1 release but was delayed to patch up some last-minute issues that arose. This feature will help site-owners recover more quickly from fatal errors that break the display or functionality of their site that would ordinarily require code or database edits to fix.Privacy and Accessibility Updates
The Dashicons library was last updated was over 3 years ago. Now, in the upcoming release, a set of 13 new icons will be added to the library along with improvements to the build process and file format of the icons.Block Editor Upgrades
WordPress 5.2 is now in the Release Candidate phase and you can test it by installing the Beta Tester plugin on any WordPress site.
On 11 May 2019, the fourth WordPress Translation Day will take place. This is a 24-hour global event dedicated to the translation of all things WordPress, from Core to themes, plugins to marketing.
Over the course of 24 hours, WordPress communities will meet to translate WordPress into their local languages and watch talks and sessions broadcast on wptranslationday.org. During the previous WordPress Translation Day, 71 local events took place in 29 countries, and even more communities are expected to take part this time.
Want to get involved in WordPress Translation Day 4? Find out how to organize a local event, follow the updates on the Polyglots team blog, and join the #polyglots channel in the Making WordPress Slack group.Block Library Project Gets Started
Since the initial proposal for a Block Library that would be made available from inside the block editor, work has been done to put together some designs for how this would look. Since then the project has received a more direct focus with a planned out scope and timeline.
The project is being managed on GitHub and people interested in contributing are encouraged to get involved there. You can also keep up to date by following the Design team blog and joining the #design channel in the Making WordPress Slack group.Further Reading:
- The results from the 5.0 release retrospective survey have been published – this is the first time this kind of open retrospective has been done for a WordPress release and the results provide valuable insight into the project and its contributors.
- The team behind the WordPress Coding Standards has released version 2.1, including some very useful new sniffs.
- The community is looking for volunteers for the Get Involved table at WordCamp Europe on 20-22 June.
- Gutenberg has been ported for use within the Laravel framework in a project dubbed Laraberg.
- The 2019 WordCamp for Publishers event has opened its call for speakers.
- The Gutenberg team has published an RFC regarding blocks being used in widgets.
- WordCamp Europe, taking place on 20-22 June, has published the schedule for the event.
- The Community Team has published the results of the 2018 meetup group survey.
Have a story that we should include in the next “Month in WordPress” post? Please submit it here.
I was born and brought up in the under-developed city of Layyah, which is situated in Southern Punjab and surrounded by desert and the river Sindh.
I graduated from college in my hometown with pretty much regular grades. Went through some hard times when I was in university. It was also difficult for me to pay the university dues due to financial shortcomings.
I am a sportsman and still have a wish to play in International Cricket which seems impossible from where I am today. At one point, I wished to join Pakistan Air Force but life directed me towards Computer Sciences.
I started using a computer in 2010 when I joined Government College University Faisalabad. Came to know about WordPress while I was finishing the last semester of my degree and my FYP was based on WordPress.
My mother–who is no more in this world–was the real hero of my life and stayed by my side till her last breath. I remember my kindergarten days when she helped me with my homework. I remember the moments in which she used to stay standing in front of the house while I drove off to school.
I remember her last day at the hospital. I met her in the ICU before her heart surgery. She hugged me and said “Don’t worry, everything will be good”. She expired during the surgery. I pray for her soul to rest in peace every day.Start of Career:
Something had always felt missing in my life, but I felt like I was on the right track for the first time in my life when I joined the WordPress community. After graduation, I struggled a lot to get my first job. I joined PressTigers as a Software Engineer and continued struggling to make my position better.
Khawaja Fahad Shakeel was my first mentor. For me, it has always been an honour to work with him. He directed me towards the right path and provided me with endless support.Community – WordCamps and Meetups:
I am using WordPress since 2015. Once I started attending meetups and open source contribution, it turned out to be a game changer for me.
I learned a lot of things from the WordPress Community platform. There are a lot of personalities who have left a deep impression on met. One of them is Nidhi Jain from Udaipur India. At this point, she is like a sister to me. We have an amazing chemistry when it comes to working on WordPress dev. The second one is Jonathan Desrosiers who is like my big brother whom I have learned a lot from and continue to do more every day.
WordPress Community is where I feel the most comfortable, after my family. I am supporting local WordPress communities and was part of WordCamp Karachi as an organizer. It was the first time that I spoke in an international level event.
People around the globe know me because of WordPress. This is why WordPress is my identity. I owe a huge part of who I am to the WordPress Community.WordPress and Future:
I believe WordPress can never die as long as people don’t stop baking new things and curating it according to the demands of the new era.
The beauty of WordPress is that it is made for everyone.
As a co-organizer of WordPress Meetup Lahore it is an honor for me to provide a platform for people to gather under one roof, to learn and share something with the community. I believe in diversity and would love to involve more people in the community leadership team.
I am extremely hopeful regarding the WordPress Meetup Lahore group and welcome everyone to contribute into making it great.
I have been terribly impressed by Marcel as he walked for WC Europe and I would love to walk for WC Asia after the approval.
In the future, if I get a chance in politics, I wish to be a part of upper house as a SENATOR OF PAKISTAN. Hopefully, I will be contesting in the next senate election either from the platform of the ruling party or as an independent candidate.Community Mentor:
Usman Khalid, the lead organizer of WC Karachi, is the hero behind the scenes for establishing the communities in Pakistan. He has mentored me for community relevant stuff. I would love to credit him, the person who gathered the Pakistani WordPress folks under one roof for the first time.Message for WordPressers:
If you seriously want to do something for yourself, do something for others first.
Go for open source, you’ll surely learn how to code. You’ll learn how to work in a team. Join local meetups, meet with the folks: help them, learn from them and share ideas.Wrap Up:
One thing I have learned from life is that there is no shortcut to success. You have to work hard to achieve your goals. The person who lives in a fantasy world will never succeed in life.
I don’t think I have achieved something great. I still have the thirst to do something; lots and lots of missions to be accomplished. My only wish is to do something different for this world which will be remembered long after I am gone.
Together we grow. Peace
After more than two years in beta, Creative Commons has launched its new search engine, featuring a completely redesigned search page, improved navigation and search filters, better search loading times, and more accurate search phrase relevance. It has replaced the old search portal and is now linked from the homepage.
This update to CC Search also improves attribution options, making it easy for users to copy the text or HTML with the license icons included. Each image also has a unique link for users to provide optional feedback on how they using the works.
Creative Commons has indexed 30 million CC-licensed images from 19 collections, including Flickr, Geograph Britain and Ireland, Bēhance, Metropolitan Museum of Art, and a number of other smaller collections. The nonprofit organization’s long-term goal is to provide access to all 1.4 billion CC-licensed and public domain works on the web.
Creative Commons will soon be expanding its image catalog with works from Europeana and Wikimedia Commons and is also adding open textbooks and audio later in 2019. The next items on the CC Search roadmap for this quarter include advanced filters to the home page, the ability to browse collections without entering search terms, and improved accessibility and UX on mobile. Some of this work will be performed by Google Summer of Code students beginning next month.
CC-licensed images are popular with bloggers and designers but tracking down license and attribution information can be tedious when searching various collections across the web. CC Search aggregates some of the most popular sources and is steadily improving the performance of its search tool. If you experience any issues, all of the CC Search code (CC Search, CC Catalog API, CC Catalog) is open source on GitHub and the organization welcomes bug reports and contributions from the community.
The upcoming BuddyPress 5.0 release will add plugin-specific debug info to the new Site Health Info screen that is coming in WordPress 5.2.
Mathieu Viet, who contributed the patch, said the information could be very useful to help solve issues on the BuddyPress forums. The panel is displayed at the bottom of the screen. It includes the BuddyPress version, active components, active template pack, and a list of other component-specific settings information.
This is a good example of how plugins can hook into this screen to add specific debug information. Users who need support can copy the information from the screen and paste it into the support forums for faster assistance with their issues.
BuddyPress 5.0 is expected at the end of May and will ship with this new site health enhancement.
Results for other frameworks are not yet available to the public but npm Inc. plans to share more details in future articles.
Another trend is the rising popularity of GraphQL. While its adoption is still relatively low, with only 7% of respondents indicating that they use it frequently, 23% of developers use it for some of their projects. The results showed that 72% of npm users are using or considering using GraphQL in 2019.
npm Inc. will be sending out follow-up surveys to specific groups of respondents who volunteered to answer additional questions. The company plans to publish more data from the questions about tooling choices, technical preferences, and attitudes towards various professional practices.
WordPress 5.2 was originally scheduled to be released on April 30, but has now been pushed back to May 7, due to the number of open tickets last week (43). There is now only one ticket remaining on the 5.2 milestone for completion of the About page and WordPress 5.2 RC 1 is ready for testing.
The upcoming release will bring major improvements to the block editor (everything released in the Gutenberg plugin prior to version 5.4). This includes the new block management capabilities and several new blocks that were ported from core widgets.
WordPress 5.2 will introduce a new admin interface for Site Health under the Tools menu. It runs tests that deliver results categorized as critical, recommended, or good, along with action items for users to improve their settings. The Information tab was added for basic debugging and provides information about the website and server setup.
A new feature called “fatal error recovery mode” is also included in this release. It pauses themes or plugins that are causing a fatal error and puts the site into recovery mode so the user can still access the admin to troubleshoot the issue. Users should experience fewer “white screen of death” situations with this new feature in place.
Check out the 5.2 field guide for a detailed breakdown of everything that’s coming in the upcoming release. If you want to get a sneak peak and help test the release candidate, the easiest way is to install the Beta Tester plugin and select the “bleeding edge nightlies” option.
The Apache Software Foundation (ASF), a non-profit corporation of decentralized volunteers from the open source developer community, has officially approved the NetBeans IDE as a Top-Level project. NetBeans joins more than 350 other open source projects and initiatives managed by the foundation after spending two years in the Apache Incubator.
NetBeans started as a student project in 1996 in what was formerly known as Czechoslovakia. It was the first Java IDE written in Java but it soon became more than just an IDE platform, as the community began using it to create applications that weren’t development tools. In 2000, Sun Microsystems acquired NetBeans and open sourced it, making it Sun’s first sponsored open source project. It became part of Oracle when it acquired Sun Microsystems in 2010 and the company continues to sponsor the project. NetBeans is now used by more than 1.5 million users each month.
Now that Apache NetBeans is governed by the ASF, it will be more likely to receive contributions than when it belonged to a commercial entity. However, contributors from Oracle and other organizations will continue to be part of shaping its future. Coming under the ASF umbrella is also bringing some welcome developments for the project’s governance, according to Apache NetBeans Vice President Geertjan Wielenga:
Being part of the ASF means that NetBeans is now not only free and Open Source software: it is also, uniquely, and for the first time, part of a foundation specifically focused on enabling open governance. Every contributor to the project now has equal say over the roadmap and direction of NetBeans. That is a new and historic step and the community has been ready for this for a very long time. Thanks to the strong stewardship of NetBeans in Sun Microsystems and Oracle, Apache NetBeans is now ready for the next phase in its development and we welcome everyone to participate as equals as we move forward.
Oracle’s decision to submit NetBeans to the ASF Incubator came as a surprise to many in 2016. At that time, OSI President Simon Phipps shared his thoughts about the benefits he saw for the project moving to open governance under the ASF:
By moving to independent governance and losing the Oracle CLA, others can join in with confidence their contribution won’t be used against them. More importantly, contributors also no longer need fear the transient decisions of cost-cutting Oracle VPs impacting the long-term viability of the project. Oracle’s Java team still needs NetBeans in order to make tools releases supporting new capabilities in Java 9 and later, so are likely to engage. Rather than withdrawal, this looks more like leveraging the ecosystem around NetBeans to sustain development while keeping Oracle’s costs in line with the direct benefit NetBeans delivers to them.
According to the proposal submitted to the ASF for NetBeans’ acceptance into the Incubator, the majority of code contributions have come from Oracle since it acquired Sun Microsystems. In addressing some of the known risks Oracle faces in contributing NetBeans to the ASF, the proposal states that “the size and diversity of the community is a guarantee against the project being orphaned.”
NetBean’s proposal said the purpose of moving NetBeans to Apache is to “expand the diversity of contributors and to increase the level of meritocracy.” The project already has a good foundation to build on, as its application framework is used by large companies and organizations, including Boeing, Airbus Defense and Space, NASA, and NATO, that depend on NetBeans for building mission critical scientific software. This new era of open governance should give the community a stronger sense of ownership and stimulate greater levels of contribution across the project.
The first release candidate for WordPress 5.2 is now available!
This is an important milestone as we progress toward the WordPress 5.2 release date. “Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. WordPress 5.2 is scheduled to be released on Tuesday, May 7, but we need your help to get there—if you haven’t tried 5.2 yet, now is the time!
There are two ways to test the WordPress 5.2 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip).What’s in WordPress 5.2?
Continuing with the theme from the last release, WordPress 5.2 gives you even more robust tools for identifying and fixing configuration issues and fatal errors. Whether you are a developer helping clients or you manage your site solo, these tools can help get you the right information when you need it.
The Site Health Check and PHP Error Protection tools have brand new features, giving you peace of mind if you discover any issues with plugins or themes on your site. There are also updates to the icons available in your dashboard, fresh accessibility considerations for anyone using assistive technologies and more.Plugin and Theme Developers
Please test your plugins and themes against WordPress 5.2 and update the Tested up to version in the readme to 5.2. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release.
The WordPress 5.2 Field Guide has also been published, which goes into the details of the major changes.How to Help
Do you speak a language other than English? Help us translate WordPress into more than 100 languages! This release also marks the hard string freeze point of the 5.2 release schedule.
If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
Howdy, RC 1!
With tools this interesting,
I can hardly wait.
BuddyPress 4.3.0 is now available. This is a security and maintenance release. All BuddyPress installations are strongly encouraged to upgrade as soon as possible.
The 4.3.0 release addresses nine security issues:
- A privilege escalation vulnerability was fixed that could allow users to “favorite” activity items to which they do not have read access. Discovered by Yuvraj Dighe.
- A privilege escalation vulnerability was fixed that could allow users to join non-public groups while using the Nouveau template pack. Discovered and reported independently by Yuvraj Dighe and Nam.Dinh.
- A privilege escalation vulnerability was fixed that could allow users to reply to activity items to which they do not have read access. Discovered by Yuvraj Dighe.
- A privilege escalation vulnerability was fixed that could allow users to view private message threads to which they do not have access while using the Nouveau template pack. Discovered by Yuvraj Dighe.
- An XSS vulnerability was fixed in the save routine for group names. Discovered by wxy7174.
- An XSS vulnerability was fixed in the content of activity items. Discovered by Yonatan Offek.
- A privilege escalation vulnerability was fixed that could allow unauthorized users to update certain group settings. Discovered by wxy7174.
- A privilege escalation vulnerability was fixed that could allow unauthorized users to view pending group invites. Discovered by Yuvraj Dighe.
- A privilege escalation vulnerability was fixed that could allow unauthorized users to delete pending group invitations. Discovered by Yuvraj Dighe.
These vulnerabilities were reported privately to the BuddyPress team, in accordance with WordPress’s security policies. Our thanks to the reporters for practicing coordinated disclosure.
BuddyPress 4.3.0 also fixes 3 bugs. For complete details, visit the 4.3.0 changelog.
Clean Blocks is a new free theme from Catch Themes that was released last week on WordPress.org. The design is suitable for businesses, agencies, freelancers, and other service professionals who require featured content, a portfolio, testimonials, a blog, and a services section.
Clean Blocks includes basic Gutenberg compatibility in that it supports all core blocks and is has a few enhanced block styles.
It may seem unnecessary to specify that it is Gutenberg-compatible, since the editor has been part of WordPress core since early December 2018. However, more than half of all WordPress users (~55%) are not running version 5.0+. Nearly 30% are hanging back at 4.9 and 25% are on even older versions.
Theme authors who create products that have Gutenberg-only features are not yet building for the majority of WordPress users. These authors are carving a path for the future of theme development. The Clean Blocks theme doesn’t really fall into this category, as its essentially enables users on WordPress 5.0+ to continue using the new editor without any styling issues. It is also compatible with earlier versions of WordPress (4.8+).
Clean Blocks recommends a collection of Catch Themes’ functionality plugins upon theme activation. These plugins handle things like galleries, infinite scroll, Instagram feeds, widgets, and additional content types. The theme includes dozens of options in the Customizer for controlling nearly every aspect of how content is displayed – from excerpt length to categories displayed on the home page to header text color. This sort of overloaded Customizer options panel is common for multipurpose style themes, and many users have come to expect it.
Check out a demo of the free version to see all the features in action.
The name “Clean Blocks” implies that the theme goes beyond the basics to customize the Gutenberg experience, but that doesn’t seem to be the case. The vast majority of the features seen in the demo are controlled by the Customizer. For example, features like Testimonials and Services are not available as blocks. While some theme authors opt to integrate features like this by pairing their themes with block collection plugins, Catch Themes has put everything into the Customizer.
Even with Gutenberg compatibility, many themes still have a disconnect between the back and frontend where certain features can only be configured in the Customizer. This fractured customization experience is one of the necessary evils for this transition time before the block editor is fully capable of handling more complex aspects of site customization.
Clean Blocks is an example of a multipurpose theme that is essentially keeping it old school in terms of content customization, while providing basic Gutenberg compatibility for users who are running WordPress 5.0+. The theme is available on WordPress.org and has already been downloaded several hundred times during its first week in the directory.
The family of Gutenberg derivatives is expanding with the beta release of Laraberg, an implementation for Laravel. Maurice Wijnia, a developer at Van Ons, an agency based in Amsterdam, created Laraberg as an easy way for developers building applications with Laravel to integrate the Gutenberg editor. It includes a simple API and support for the Laravel File Manager for uploading files.
“The goal for Laraberg is to give developers the ability to add the Gutenberg editor to any page they like in a way that is as easy as possible, but at the same time it has to prove enough options to tailor the editor so it can fit into any Laravel project out there,” Wijnia said.
Van Ons has a preference for using Laravel in their projects, due to its increasing popularity and active community. Laraberg makes it possible for the agency to tap into the convenience of the Gutenberg editor without giving up the performance and features they enjoy in the Laravel framework. The beta release is now available on GitHub and Packagist. Van Ons plans to actively implement Laraberg in their own projects and will also be collecting feedback from beta testers.
Wijnia said he was inspired by the Drupal Gutenberg project, whose creators also authored Gutenberg.js, a package that makes it easier to bring Gutenberg into other applications. Providing a foundation for using Gutenberg on any CMS or framework is part of Frontkom’s long term vision for improving the open web and enabling communities to collaborate on mutually beneficial extensions.
As the editor continues to expand to more platforms and frameworks, a CMS-agnostic block library would offer a central place for Gutenberg’s increasingly diverse user base to discover new blocks. WordPress.org has the opportunity to provide that in its own block library, with the support of the Gutenberg Cloud team that pioneered the idea in 2018.
“If Gutenberg Cloud can serve as a proof of concept that WP.org can later adopt as their own, we are happy,” Frontkom CTO Per Andre Rønsen said. He also further commented on the WordPress.org Block Library proposal, advocating for the team to grow their vision beyond the WordPress community only. No official decision has been announced yet. If WordPress decides to forgo the opportunity of providing a block library inclusive of other frameworks and platforms, then the Gutenberg Cloud will continue to be the place for discovering blocks that can be used across multiple platforms.
As I make a checklist of all the things I’ll have to pack to travel from São Paulo to Berlin, to attend WordCamp Europe 2019, I can’t stop thinking how hard the path to this point has been.
For some of people, a travel like this may seem ordinary, but for me, this will be the farthest I’ve ever been until now, in many ways. Especially because the last time I was planning to attend an international WordCamp, things didn’t work out at all.
So let me tell you about the path.The first steps
I was born and raised in São Paulo. Allow me to give you some context about my city. São Paulo is the richest and biggest city of Brazil. With more than 14 million people, it’s also the biggest city of the south hemisphere. It’s even bigger than New York.
Like every big city, São Paulo is a place of opportunities, but also a place of contrasts.
Growing up, although we were poor, my family cared a lot about the education of me and my little brother. My father who always liked technology, managed to get a computer for us in 1996. At that time, I was 6 years old, and we were the only family in my neighborhood to have a computer for a long time, and that was sad. That early exposure to technology made a big difference in my life.
At age 13, I was very interested in graphic design and coding.
We had a very limited and expensive dial-up internet, that was only free after midnight and at weekends.
So to learn these skills, my best options were the CD-ROM magazines that my father would bring home. I also learned about HTML with a book about Microsoft Front Page. At age 14 I sold my first website, entirely created on Front Page, with lots of GIFs and <marquee> tags, for a neighbour who needed it for a college project. She loved it!
I decided I wanted to work with design. So I started a Graphic Design course during the high school. With my love for web design, all I wanted was to have a site that was actually online. I couldn’t afford a host, but fortunately at this time, blogs became very popular here in Brazil.
I looked for a platform to create a portfolio. I played a little with one called WordPress (you may have heard of it) and ended up using Blogger instead, because there was the possibility to customize the theme’s CSS online. I made a very dark grungy theme for my blog that’s still online.A bumpy road
I got a scholarship for Graphic Design at a good College in São Paulo, but I still would have to pay for half of the monthly tuition. The problem was that my family definitely had no means to afford it. My parents said they would cut some expenses and help me, but I knew that there wasn’t anything they could cut. So I told them to not worry, I would find a job.
At this point I had made a freelance gig creating a HTML website (in Dreamweaver this time). With exactly 1 month left for the College application, this client proposed that I started working there to maintain the website I just made. So I was able to (barely) pay for the college. After six months, I applied for a full scholarship and it was granted. Things got a little better financially, but the path was still rocky.
It took me 3 hours by bus from my house to the college every single day, just inside the city of São Paulo (remember when I said this city is huge?).
I had the cheapest hot dog for lunch every day, because I couldn’t afford a real meal.
Then I would go to work (another 1h30 of bus from the college), and at night I would head back home (another bus, another 1h30). That was my routine for one and a half year throughout the college. As you can imagine, I was exhausted, and eventually getting ill.A fork in the path
That’s when I decided that I would quit my job and start a business with my boyfriend Allyson Souza, that I met during my Graphic Design course in High School. We started the company officially in july, 2009. We named it Haste (the portuguese word for “stem”).
We were 19 years old, not much experience, zero network and money, a lot of energy, and some extra self-confidence (I could have summarized simply as “millennials”, right?). Allyson’s father gave us a computer and a part of his office, for which I am very grateful, and we created all the graphic materiais for his courses company in exchange.
We started working with graphic design only, and it took us some time to realize that web development was our future.
I remembered WordPress and tried it again. I liked how the platform had evolved. We made a second version of our website in WordPress, using a simple free theme, which I edited the CSS directly (oh god). We tried to create websites for clients modifying existing themes (at least we learned about child themes later), but we definitely didn’t feel in control of what we were doing.When you hit your lowest point
In January 2011, my mother had a stroke. She had a brain surgery, and after a month, she was back home with a 6 inches scar in the head. That was the lowest point on my path.
The next years I had to take care of her, because of some consequences of the stroke, both physical and psychological. As the only family member who hadn’t a “formal” job, with a boss and a defined schedule, I was the one who had to take her to appointments, or the ER, or stay home when she wasn’t ok. It was very hard to reconcile the final year of college, the work and my mom’s health care.The only way is up
At Haste, we felt that things were not evolving. In 2013, after some partnerships that took us to some confusing paths, we decided to have a complete makeover. We defined a new focus: web design and development with WordPress. We created a new website, with a theme fully developed by us. We wanted to overcome the fear of coding, and wanted to know exactly what we were doing. So we started studying a lot by ourselves.
We were proud WordPress developers now.
We started attending the meetups, and then the WordCamp. I was amazed how the open-source culture was all about sharing knowledge with strangers, with no fear of competition, just the spirit of collaboration. We felt no longer isolated. We made real friends (shout out to all my WordPress friends).
Soon we were both involved in the community, and became WordCamp São Paulo organizers in 2014.
The new website and our participation in the WordPress community were really what we needed to give us some perspective and stability. So we didn’t stop there.Bring others to walk with you
In the 2014 edition of WordCamp São Paulo, I was the only female speaker. That made me realize a few things.
First that the proportion of men in the community events was not only the majority but, we almost didn’t had any women at all, which was very weird.
Second, we know that lots of girls feel intimidated in an environment with too much men. I always had a majority of male friends since I was a kid, and even so, I probably wouldn’t get involved with the community if it wasn’t by the fact that my boyfriend / partner was with me.
A few sexists incidents had happened with me too. I reacted, and the men involved seemed to understand that I wasn’t ok, and changed their behavior as far as I know.
We don’t have as many meetups and WordCamps here in Brazil as in US. Although Brazil is becoming a technology hub, the WordPress community has still a lot of room to grow, compared to other communities. So, I think we have the opportunity to make things different while everything is not settled yet.
So I decided to act now.
I started a poll asking the women involved with WordPress the reasons why they wouldn’t attend the events. The results proved it wasn’t just me complaining about small things.
Some jokes kept women away. Some condescending actions made them feel diminished. And even the lack of information from our part, that the WordCamps are inclusive events, made the women not to come. The lack of time, was an important factor too.
Based on this data, the next year we managed to increase the proportion of female speakers from 5% to 32% at WordCamp São Paulo 2015. More women became organizers too. In 2019 we have 4 women out of 10 active organizers. The last WordCamp we had blind people attending, and their feedback was great. We still need to improve racial diversity though.Barriers and frontiers
In 2015, Allyson had told me about this new scholarship program from the WordPress Foundation for women who work for equality in the community around the world. So I applied for the very first Kim Parsell Memorial Scholarship. Kim Parsell left a beautiful legacy of inclusion and love, having worked to bring more women, older people, and other minorities to the WordPress community. She was known as the #WPMom.
The result came few months later. I received an email, and had no reaction for a few minutes. I had won the scholarship, and it granted me a travel to WordCamp US 2015, in Philadelphia Pennsylvania, with flights and hotel covered.
You see: I had never left my country. I had just took flight for the first time that same year. I was not even close to dream to go to US, because it was impossible for me at the moment. Sometimes your mindset in the only thing putting limitations in your dreams.
I was so happy, you have no idea. Alx Block and Cami Kaos reached to me to give me instructions and they were very kind.
But then… my visa application was denied. They considered my sudden passport and visa solicitation, with no money to travel (that’s exactly the point of a scholarship!), and lack “ties” in Brazil very suspicious. I told them that the WordPress Foundation would pay for everything. The flights and the hotel were already booked. The officer even told me that the WordPress Foundation letter could be easily forged. I tried again, with no success.
I couldn’t go to WordCamp US 2015.
I couldn’t go to WordCamp US 2016 too, when they asked if I wanted to try again, and my visa was denied… again. This time I think at least the officer searched online for me, saw it was true, but couldn’t do anything, since my situation hadn’t change.
I was so disappointed. This still hurts me, I must confess. Sometimes, there are real barriers and gates that a simple mindset change cannot open.Crossed paths
The next years, I focused on my company and the work at the community. My mom’s health improved, she’s in great shape now. My family supports my work.
We became specialists in WordPress at Haste. We developed themes, plugins and sites for companies in Brazil and America. I now have a stable income and I live exclusively from my work with WordPress. We are celebrating 10 years in 2019.
I traveled through Brazil because of WordPress, to speak at WordCamps and Meetups. I see more and more women working with WordPress, attending meetups and WordCamps, and talking to each other, finding something familiar in every other woman’s face.
Last year we decided we would go to WordCamp Europe 2019 in Berlin, since we don’t need a visa to most countries there, including Germany.
This time I can afford it (with a lot of planning and expenses cut, but I’ll be ok). I have to confess that I’m a little anxious about the immigration process.
My goal at WordCamp Europe is to know the most people I can. It’s not a matter of quantity, but if the WordPress community taught me something was that every person has something to teach and to learn. So If you are attending WordCamp Europe, let’s meet!Opening trails
So now I hope you can see what this travel really means to me, and why every small conquest means a lot. It’s not just because it was hard. But because I’m not the only one who deserve it, but unfortunately I’m a exception between other people who have the same background as I.
There are so many young girls and boys that don’t dare to dream about visiting other countries, or even getting in the college. Lots of kids that don’t have a computer, or even access to internet. The only difference is that I was given opportunities, people believed in me. Doors were opened. And just then I could prove my value.
Now my next dream is to be able to make the journey a little easier than it was for me, specially for women and young Brazilians. Because I think that’s our responsibility in the community. Teach others, share information, donate some of your time, create new tools, plugins and resources, mentor people. As my brother’s tattoo says, be the person you needed when you were younger.Como a comunidade WordPress me ajudou a encontrar o meu caminho
Enquanto faço uma lista de todas as coisas que preciso para viajar de São Paulo para Berlim, para participar do WordCamp Europe 2019, não posso deixar de pensar no quão difícil foi o caminho até esse ponto.
Para algumas pessoas, uma viagem como essa pode parecer comum, mas, para mim, esse será o mais longe que já fui até agora, de muitas maneiras. Especialmente porque, da última vez que eu planejava participar de um WordCamp internacional, as coisas não deram certo.
Então deixe-me contar sobre esse caminho.Os primeiros passos
Eu nasci e cresci em São Paulo. Permita-me dar um pouco de contexto sobre minha cidade. São Paulo é a mais rica e maior cidade do Brasil. Com mais de 14 milhões de pessoas, é também a maior cidade do hemisfério sul. É maior que Nova York.
Como toda grande cidade, São Paulo é um lugar de oportunidades, mas também de contrastes.
Crescendo, apesar de sermos pobres, minha família se importava muito com a minha educação e do meu irmão mais novo. Meu pai, que sempre gostou de tecnologia, conseguiu um computador para nós em 1996. Naquela época, eu tinha 6 anos, e éramos a única família das redondezas a ter um computador por um longo tempo, e isso era triste. Essa exposição precoce à tecnologia fez uma grande diferença na minha vida.
Aos 13 anos, eu já estava interessada em design gráfico e programação. Nós tínhamos aquela internet discada muito limitada e cara, que só era gratuita depois da meia-noite e nos fins de semana. Então, para aprender essas habilidades, minhas melhores opções eram as revistas em CD-ROM que meu pai trazia para casa. Eu também aprendi sobre HTML com um livro sobre o Microsoft Front Page. Aos 14 anos, vendi meu primeiro site, inteiramente criado no Front Page, com muitos GIFs e tags <marquee>, para uma vizinha que precisava para um projeto da faculdade. Ela adorou!
Eu decidi que queria trabalhar com design. Então fiz o curso técnico em design gráfico durante o ensino médio. Com o meu interesse pelo web design, tudo o que eu queria era ter um site que estivesse online. Eu não podia pagar um servidor, mas felizmente, neste momento, os blogs se tornaram muito populares aqui no Brasil.
Procurei uma plataforma para criar um portfólio. Eu brinquei um pouco com uma plataforma chamada WordPress (você pode ter ouvido falar dela) mas acabei usando o Blogger, porque havia a possibilidade de personalizar o CSS do tema online. Eu fiz um tema escuro e grunge para o meu blog que ainda está online.Uma estrada esburacada
Consegui uma bolsa de Design Gráfico em uma boa faculdade em São Paulo, mas ainda teria que pagar metade da mensalidade. O problema era que minha família definitivamente não tinha como arcar com isso. Meus pais disseram que cortariam algumas despesas e me ajudariam, mas eu sabia que não havia nada que pudessem cortar. Então eu disse a eles para não se preocuparem, eu encontraria um emprego.
Neste momento, eu havia feito um trabalho freelancer criando um site HTML (no Dreamweaver desta vez). Com exatamente 1 mês para o aplicativo da faculdade, esta cliente propôs que eu começasse a trabalhar lá para manter o site que tinha acabado de criar. Então eu pude pagar pela faculdade (bem mal). Depois de seis meses, solicitei uma bolsa de estudos integral e ela foi concedida. As coisas melhoraram um pouco financeiramente, mas o caminho ainda era rochoso.
Levava 3 horas de ônibus da minha casa para a faculdade todos os dias, apenas dentro da cidade de São Paulo (lembra quando eu disse que essa cidade é enorme?). Eu comia um cachorro-quente mais barato para o almoço todos os dias, porque eu não podia pagar uma refeição de verdade. Então eu ia trabalhar (outra 1h30 de ônibus da faculdade), e à noite eu voltava para casa (outro ônibus, outro 1h30). Essa foi a minha rotina por um ano e meio durante a faculdade. Como você pode imaginar, eu estava exausta e ficando doente.Uma bifurcação no caminho
Foi então que decidi largar meu trabalho e começar um negócio com meu namorado Allyson Souza, que conheci durante o curso de Design Gráfico no Ensino Médio. Nós começamos a empresa oficialmente em julho de 2009. Nós a nomeamos Haste.
Nós tínhamos 19 anos de idade, não muita experiência, zero networking e dinheiro, muita energia e alguma autoconfiança extra (eu poderia ter resumido simplesmente como “millennials”, certo?). O pai do Allyson nos deu um computador e uma parte de seu escritório, pelo que sou muito grata, e criamos todos os materiais gráficos para sua empresa de cursos em troca.
Começamos a trabalhar apenas com design gráfico e levamos algum tempo para perceber que o desenvolvimento web era o nosso futuro.
Lembrei-me do WordPress e tentei novamente. Eu gostei de como a plataforma evoluiu. Fizemos uma segunda versão do nosso site no WordPress, usando um simples tema gratuito, que eu editei diretamente o CSS (não façam isso!). Tentamos criar websites para clientes que modificando temas existentes (pelo menos aprendemos sobre temas filhos mais tarde), mas definitivamente não nos sentíamos no controle do que estávamos fazendo.Quando você atinge seu ponto mais baixo
Em janeiro de 2011, minha mãe teve um AVC. Ela fez uma cirurgia no cérebro, e depois de um mês, ela estava em casa com uma cicatriz na cabeça. Esse foi o ponto mais baixo do meu caminho.
Nos anos seguintes eu tive que cuidar dela, por causa de algumas consequências do AVC, tanto físicas quanto psicológicas. Como a única pessoa da família que não tinha um emprego “formal”, com um chefe e um horário de trabalho definido, fui eu quem teve que levá-la às consultas, ao pronto-socorro ou ficar em casa quando ela não estava bem. Foi bem difícil conciliar o último ano da faculdade, o trabalho e cuidar da saúde da minha mãe.O único caminho é para cima
Na Haste, sentimos que as coisas não estavam evoluindo. Em 2013, após algumas parcerias que nos levaram a caminhos confusos, decidimos fazer uma reformulação completa. Definimos um novo foco: web design e desenvolvimento com WordPress. Criamos um novo site, com um tema totalmente desenvolvido por nós. Queríamos superar o medo de programar e queríamos saber exatamente o que estávamos fazendo. Então começamos a estudar muito por conta própria.
Nós começamos a frequentar os meetups, e depois o WordCamp da comunidade WordPress. Fiquei espantada com a forma como a cultura de código aberto era toda sobre compartilhar conhecimento com estranhos, sem medo de competir, apenas o espírito de colaboração. Não nos sentíamos mais isolados. Nós fizemos amigos de verdade (alô amigos do WordPress).
Logo nos envolvemos na comunidade e nos tornamos organizadores do WordCamp São Paulo em 2014.
O novo site e nossa participação na comunidade WordPress foram realmente o que precisávamos para nos dar alguma perspectiva e estabilidade. Então nós não paramos por aí.Traga os outros para caminhar com você
Na edição de 2014 do WordCamp São Paulo, eu era a única palestrante mulher. Isso me fez perceber algumas coisas.
Primeiro, a proporção de homens nos eventos da comunidade não era apenas a maioria, mas quase não tínhamos nenhuma mulher. O que era muito estranho.
Em segundo lugar, sabemos que muitas mulheres se sentem intimidadas em um ambiente com muitos homens. Eu sempre tive a maioria de amigos homens desde criança, e mesmo assim, eu provavelmente não me envolveria com a comunidade se não fosse pelo fato de meu namorado / sócio estar comigo.
Alguns incidentes sexistas também aconteceram comigo. Eu reagi, e os homens envolvidos parecem ter entendido o problema, e mudaram seus comportamentos até onde eu sei.
Não temos tantos meetups e WordCamps aqui no Brasil como nos EUA. Embora o Brasil esteja lentamente se tornando um polo de tecnologia, a comunidade WordPress ainda tem muito espaço para crescer, em comparação com outras comunidades. Então, acho que temos a oportunidade de fazer as coisas diferentes enquanto tudo ainda não está definido.
Então eu decidi mudar isso.
Eu comecei uma pesquisa perguntando às mulheres envolvidas com WordPress quais eram as razões pelas quais elas não compareciam aos eventos. Os resultados provaram que não era só eu reclamando de pequenas coisas.
Algumas piadas mantinham as mulheres afastadas. Algumas ações condescendentes fizeram com que se sentissem diminuídas. E mesmo a falta de informação de nossa parte, de que os WordCamps são eventos inclusivos, fez com que as mulheres não viessem. A falta de tempo também foi um fator importante.
Com base nesses dados, no ano seguinte conseguimos aumentar a proporção de mulheres palestrantes de 5% para 32% no WordCamp São Paulo 2015. Mais mulheres se tornaram organizadoras também. Em 2019, temos 4 mulheres de 10 organizadores ativos. No último WordCamp, tivemos deficientes visuais comparecendo e o feedback deles foi ótimo. Ainda precisamos melhorar a diversidade racial.Barreiras e fronteiras
Em 2015, Allyson me contou sobre o novo programa de bolsas de estudos da Fundação WordPress para mulheres que trabalham pela igualdade na comunidade em todo o mundo. Então me inscrevi para a primeira bolsa Kim Parsell Memorial. Kim Parsell deixou um lindo legado de inclusão e amor, tendo trabalhado para trazer mais mulheres, pessoas mais velhas e outras minorias para a comunidade WordPress. Ela era conhecida como a #WPMom.
O resultado veio alguns meses depois. Recebi um email e não tive reação por alguns minutos. Eu tinha ganhado a bolsa que me garantia uma viagem para o WordCamp US 2015, na Filadélfia, na Pensilvânia, com voos e hotel cobertos.
Veja bem: eu nunca tinha saído do meu país. Eu tinha acabado de voar de avião pela primeira vez naquele mesmo ano. Eu não estava nem perto de sonhar em ir para os EUA, porque era impossível para mim no momento. Às vezes sua mentalidade na única coisa colocando limitações em seus sonhos.
Eu estava tão feliz, você não faz ideia. Alx Block e Cami Kaos entraram em contato para me dar instruções e foram muito gentis.
Mas então… meu pedido de visto foi negado. Eles consideraram minha solicitação repentina de passaporte e visto, sem dinheiro para viajar (esse é exatamente o ponto de uma bolsa de estudos!), e a falta de “laços” no Brasil muito suspeitos. Eu disse a eles que a Fundação WordPress pagaria por tudo. Os voos e o hotel já estavam reservados. O oficial até me disse que a carta da Fundação WordPress poderia ser facilmente falsificada. Eu tentei de novo, sem sucesso.
Eu não pude ir para o WordCamp US 2015.
Eu também não pude ir ao WordCamp US 2016, quando eles perguntaram se eu queria tentar novamente, e meu visto foi negado… de novo. Desta vez, acho que pelo menos o oficial pesquisou on-line por mim, viu que era verdade, mas não conseguiu fazer nada, pois minha situação não mudara.
Eu estava tão desapontada. Ainda fico triste de lembrar, devo confessar. Às vezes, existem barreiras e portões reais que uma simples mudança de mentalidade não pode abrir.Caminhos cruzados
Nos anos seguintes, concentrei-me em minha empresa e no trabalho na comunidade. A saúde da minha mãe melhorou, ela está em ótima agora. Minha família apóia meu trabalho.
Nós nos tornamos especialistas em WordPress na Haste. Desenvolvemos temas, plugins e sites para empresas no Brasil e na América. Agora tenho uma renda estável e vivo exclusivamente do meu trabalho com o WordPress. Estamos comemorando 10 anos em 2019.
Eu viajei pelo Brasil por causa do WordPress, para falar em WordCamps e Meetups. Fui para Fortaleza, Belo Horizonte, Curitiba, Porto Alegre. Eu vejo mais e mais mulheres trabalhando com o WordPress, participando de meetups e WordCamps, e conversando, encontrando algo familiar no rosto das outras mulheres.
No ano passado, decidimos que iríamos para o WordCamp Europa 2019 em Berlim, já que não precisamos de visto para a maioria dos países, incluindo a Alemanha.
Desta vez, posso pagar (com muito planejamento e redução de despesas). Tenho que confessar que estou um pouco ansiosa com o processo de imigração.
Meu objetivo no WordCamp Europa é conhecer o máximo de pessoas que posso. Não é uma questão de quantidade, mas se a comunidade do WordPress me ensinou algo foi que cada pessoa tem algo para ensinar e aprender. Então, se você estiver participando do WordCamp Europa, vamos nos conhecer!Abrindo trilhas
Então agora eu espero que você possa ver o que essa viagem realmente significa para mim, e porque cada pequena conquista significa muito. Não é só porque foi difícil. Mas porque eu não sou a única que merece isso, mas infelizmente sou uma exceção entre outras pessoas que têm o mesmo histórico que eu.
Há tantas meninas e meninos que não se atrevem a sonhar em visitar outros países ou até mesmo entrar na faculdade. E quando se atrevem, tem seus sonhos podados. Muitas crianças que não têm computador nem acesso à internet. A única diferença é que me foram dadas oportunidades, as pessoas acreditaram em mim. Portas foram abertas. E só então eu pude provar o meu valor.
Agora meu próximo sonho é poder tornar a jornada um pouco mais fácil do que foi para mim, especialmente para mulheres e jovens brasileiros. Porque acho que é nossa responsabilidade na comunidade. Ensine outras pessoas, compartilhe informações, doe um pouco do seu tempo, crie novas ferramentas, plugins e recursos, oriente as pessoas. Como diz a tatuagem do meu irmão, seja a pessoa de que você precisava quando era mais jovem.
Bank Zymphonies Theme is a financial multipurpose theme for banking, finance business companies, like loan providers, credit card companies and personal insurance. We have extended Bootstrap UI and Drupal basic layout to provide you with more user friendly theme to create a awesome responsive banking website.
- Drupal 8 core
- Bootstrap v4
- Mobile-first theme
- Top bar information
- Top menu
- Social media links
- Top highlight blocks
- Included Sass & Compass source file
- Well organized Sass code
- Custom slider - Unlimited image upload
- Home page layouts
- 4 column top layout
- 4 column middle layout
- 4 column bottom layout
- 4 column footer layout
In his new podcast, Zhu is talking with other maintainers to unearth their valuable perspectives and share similar struggles. By presenting them as regular people, rather than faceless code projects, Zhu is aiming to encourage empathy for maintainers.
Maintainers Anonymous is centered around the “how” of maintenance and Zhu is open to having guests from a variety of fields and disciplines, such as a librarian, gardener, or moderator. In an episode titled “Speedrunning with Omnigamer,” Zhu and his first guest, Eric Koziel, discuss the intricacies of “speedrunning,” playing a video game with the goal of beating it as fast as possible. Koziel describes it as a medium for doing an optimization challenge. Since the games are just software, he and Zhu explored how speedrunning intersects with coding and talked about some of the parallels with maintaining open source software.
The next two episodes are a series with guest Stephanie Hurlburt, a graphics engineer and owner of the company that makes Basis, an image/texture compression product. They delve deeper into how business development is relevant to open source, setting healthy boundaries, inherent vs. perceived value, marketing, and more.
If you’re looking for a new podcast to add to your subscriptions, Zhu’s Maintainers Anonymous offers a wide variety of topics and perspectives that touch on open source, maintainership, and other aspects of life and business in the world of technology. New episodes are available on the podcast’s website, and listeners can also subscribe via RSS, Apple Podcasts, Google Podcasts, or Spotify. Follow @MaintainersAnono on Twitter for all the latest.
WPTavern: Celebrate Earth Day by Learning about Environmentally Friendly Web Development on WordPress.tv
Today is Earth Day, a worldwide annual event first celebrated in 1970 that focuses on addressing environmental concerns. Earth Day Network coordinates 192 countries with more than a billion people participating in today’s event. The organization uses WordPress to build the world’s largest environmental movement through education, public policy, and consumer campaigns.
Over the past few years, environmentally-friendly web development has become an increasingly popular topic at WordCamps. Several presentations are available on WordPress.tv that highlight how web developers have the ability to make a positive impact on reducing the internet’s carbon footprint.
Jenn Schlick, a project manager at the MIT Energy Initiative, was one of the first WordCamp speakers to bring greater awareness to this topic with her presentation on Low-Carbon Web Design at WordCamp Finland in 2016. She explained a few ways that developers can minimize a website’s carbon footprint by choosing online services that are powered by renewable energy and optimizing for performance.
In 2017, Tom Greenwood gave a presentation titled Zero Carbon WordPress that challenged the community to help tackle climate change. With WordPress powering such a large percentage of the web, the community has the opportunity to lead the way in developing sites that use less energy, powered by hosts that run on renewable energy sources.
More recently, Jack Lenox spoke at WordCamp Bordeaux 2019 on “How better performing websites can help save the planet.” His presentation had a stronger emphasis on performance with practical steps for simplifying the interface, reducing code, using the right image file types, caching, accessibility, and more.
At WordCamp Nordic 2019, Jaakko Alajoki gave a presentation titled Environmentally friendly WordPress development, with experiments that used a Raspberry Pi web server and power meter to demonstrate power consumption. The session should be available on WordPress.tv soon.
WPTavern: AMP Plugin for WordPress 1.1 Adds Experimental PWA Plugin Integration, Pre-release of AMP Stories Editor Available in 1.2-alpha
Version 1.1 of the AMP Plugin for WordPress was released this week after four months in development and 125 merged pull requests from contributors. It includes CSS tree shaking improvements that restore AMP compatibility for WordPress’ default Twenty Nineteen theme, reducing the size of its stylesheet by 53%.
In an effort to get more users opting for the Native mode option, the plugin’s development team has rebranded the template modes:
In this release the Paired mode has been rebranded as Transitional mode. One reason for this is that the classic mode was also a paired mode (where there are separate parallel URLs for the AMP version). But more importantly, the goal for this mode is to help facilitate a transition a site to being AMP-first, where there is no separate AMP-specific URLs. So the goal of the Transitional mode is to be a path to Native mode.
The team has also decided to rebrand Classic mode to “Reader” mode, instead of deprecating it. It provides a basic AMP template for getting started that doesn’t necessarily match the site’s theme. Users can can add an “Exit Reader Mode” to the header of their sites with a setting in the Customizer.
Version 1.1 introduces compatibility with the PWA feature plugin, bringing support for the service worker to AMP pages. It extends the service worker to cache AMP CDN assets, images, and Google Fonts. Since the PWA feature plugin is still under active development, the service worker integration is still considered experimental.
Support for creating AMP Stories in WordPress is the next major feature coming to the plugin. A pre-release of the AMP Stories editor is available in 1.2 alpha 1, which also requires the latest version of the Gutenberg plugin. It uses the Gutenberg editor to allow users to build AMP stories with rich media capabilities.
A preview of the AMP Stories editor was unveiled at AMP Conf 2019 in Tokyo, Japan. Check out the video below to see Alberto Medina give a quick demonstration of how it will work in the upcoming version 1.2 of the AMP for WordPress plugin.