Wordpress News

WPTavern: The New Woo Adopts Gutenberg Components, User Interface Driven by React

Wordpress Planet - Fri, 10/19/2018 - 02:49

WooSesh, the free virtual conference devoted to WooCommerce kicked off earlier today. Todd Wilkins, Head of eCommerce at Automattic, Kelly Hoffman, Head of Design for eCommerce at Automattic, and Aviva Pinchas, Product Lead of the WooCommerce Marketplace at Automattic got things started with the keynote presentation.

Wilkins highlighted what the team has accomplished since last year and outlined what users can expect in 2019. Pinchas shared a wealth of data from a survey that was sent to WooCommerce users and to end the presentation, Hoffman described how the team designed the new interfaces.

One of the major changes coming to WooCommerce is a redesigned backend. The project is being developed on GitHub as a feature plugin called WC-Admin.

New WooCommerce Dashboard

The dashboard is a landing page where store owners will be able to see at a glance how their store is doing. The new interface is powered by the React JavaScript framework, specifically the React components that are part of the Gutenberg project. It’s modular, allowing users to add, move, and remove blocks. Developers will be able to extend the dashboard and provide custom blocks.

In addition to the new interface, reports are being overhauled. Store owners will be able to filter data, compare date records, have easy access to important data points, and download reports in CSV format. The Activity Panel has been completely redesigned and will be accessible from any page in the WooCommerce backend.

WooCommerce Activity Panel

The activity panel will also house a Notifications area that acts as an email Inbox. Developers will be able to add notifications from their extensions using the WooCommerce REST API endpoints.

WooCommerce Notifications Panel

To see WC-Admin in action, you’ll need to download the feature plugin and run it in a test environment. The WooCommerce team does not recommend using it in a production environment.

Once it reaches beta, the plugin will be made available on WordPress.org to allow a larger audience to test it before being merged into WooCommerce core. The plugin is scheduled to hit beta in early 2019 with new features being merged in the first quarter of 2019.

Similar to Gutenberg development where progress updates were published to the Make Core Developer blog every week or every other week, the WooCommerce team plans to publish progress updates every two weeks on its developer blog. With these improvements, WooCommerce is another reason for developers to learn JavaScript deeply.

WPTavern: Learn How to Build an Interactive Prototype with Dave Martin’s Free JavaScript for Designers Course

Wordpress Planet - Thu, 10/18/2018 - 19:13

Product designer Dave Martin has published a free video course called JavaScript for Designers. The course is made up of 46 bite-sized videos that walk students through the basics via a hands-on tutorial for building an interactive HTML prototype.

Martin said he created the course specifically for designers who have been putting off learning how to code with JavaScript. He focused on concepts that are applicable to designers in their jobs, teaching skills that help them communicate to developers exactly how they want an app to behave.

Coming from a designer’s perspective, Martin said most JavaScript tutorials are “dry and boring,” because they are written by developers. Ordinarily, these types of courses begin with JavaScript’s historical roots and progress from variables to arrays to objects, losing many learners along the way. Martin’s course is built more like a tutorial. Students will replicate some of the functionality found in a site like Dribbble. At the end, students should have a sufficient foundation of JavaScript that enables them to build an interactive HTML prototype.

One of the other important ways this course is different is that the giant “Get Started” button on the page doesn’t take you to a registration form or make you sign up for dripped emails. It simply scrolls down the page so you can dive into the videos. Participants can download the code and follow along with the tutorial.

Today’s announcement from WooSesh that WooCommerce is testing its new Javascript-driven interface is just another reminder that JavaScript is overtaking modern UI design and architecture. JavaScript knowledge is going to become increasingly in demand, and designers who have a decent grasp of it will land themselves higher paying positions. Even if you’re not a designer, Martin’s course may hold your interest better than traditional JavaScript beginners’ courses. Check out the videos at jsfordesigners.davemart.in.

YG Iconic

Drupal Themes - Thu, 10/18/2018 - 15:46

YG Iconic is modern Drupal 8 theme developed to help you to create a stunning websites.

Features

  • Drupal 8 core
  • Bootstrap v3
  • Services
  • Pricing
  • Testimonials

Live Demo Download Demo Site

It is highly recommended to install the demo site and customize it to get the exact look. Here is the link for the documentation to install demo site

Demo login credentials : admin / admin@123

Thanks for checking out our theme. We can install the theme in your server for free!

Contact us for free installation


Other YG Business themes


Credits

Drupal theme by Young Globes

WPTavern: WPWeekly Episode 334 – Accessibility, Gutenberg, and Twenty Nineteen

Wordpress Planet - Thu, 10/18/2018 - 14:40

In this episode, John James Jacoby and I have a lengthy discussion about the numerous Accessibility concerns being raised by members of the community. We also talk about the WordPress 5.0 release date, tempers flaring in the WordPress core Slack channel, dealing with political situations within the WordPress project, and more. We share our thoughts on the Twenty Nineteen default theme and provide a quick update on the status of WooCommerce 3.5.

Stories Discussed:

WordPress Accessibility Team Lead Resigns, Cites Political Complications Related to Gutenberg
First Look at The Twenty Nineteen Default Theme
Important update: WooCommerce 3.5 will now be released October 23rd.
WordPress Now at 32%

WPWeekly Meta:

Next Episode: Wednesday, October 24th 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #334:

YG Intechnic

Drupal Themes - Thu, 10/18/2018 - 10:06

YG Intechnic is modern Drupal 8 theme developed to help you to create a stunning websites.

Features

  • Drupal 8 core
  • Bootstrap v3
  • Services
  • Pricing
  • Testimonials

Live Demo Download Demo Site

It is highly recommended to install the demo site and customize it to get the exact look. Here is the link for the documentation to install demo site

Demo login credentials : admin / admin@123

Thanks for checking out our theme. We can install the theme in your server for free!

Contact us for free installation


Other YG Business themes


Credits

Drupal theme by Young Globes

Rizah

Drupal Themes - Thu, 10/18/2018 - 09:19

A Free Bootstrap Child theme

WPTavern: Gutenberg Accessibility Audit Postponed Indefinitely

Wordpress Planet - Wed, 10/17/2018 - 22:16
photo credit: pollascc

Discussion surrounding Gutenberg’s independent accessibility audit is heating up. Two weeks ago, Matthew MacPherson, who was named WordPress 5.0’s new accessibility lead, proposed the audit and agreed to it being performed by an independent third party. The audit had gained strong support among accessibility contributors and others following the ticket.

After soliciting detailed proposals from four companies, MacPherson has since rescinded the offer to coordinate the audit at this time and it seems he was unaware that he didn’t have the authority to authorize it in the first place.

“For at least the time being, Automattic has decided to forgo conducting an Accessibility audit on Gutenberg,” MacPherson said. He cited the following reasons:

  1. “an audit will not be actionable given our release timeline, because…
  2. the audit will not affect release timing, so…
  3. it would be more prudent to explore an audit on a less rushed timeline in the future”

MacPherson apologized for “getting hopes up and then failing the community” on this particular issue. He is supportive of getting an audit but it is not a priority to complete before Gutenberg’s merge proposal.

“I’m hopeful we’ll explore an audit going forward, but unfortunately it will not happen before the merge proposal and thus I’m closing this issue as a won’t fix,” MacPherson said. “I would still like to blog about the state of Gutenberg accessibility, both the good and the bad. We’re making some improvements to keyboard navigation, color contrast, focus behavior, and date/color-pickers just this week.”

Those following the ticket were disappointed in the decision and several heated replies have been hidden and/or moderated. The issue has since been locked and unlocked several times since the announcement that Automattic has decided to forgo the audit.

“Literally every person with disabilities who has tested Gutenberg, both recently and at the outset, has flagged blocking issues as to why it’s not accessible,” Accessibility team member Amanda Rush said. “And user testing is just as important to accessibility as is WCAG 2.0 level AA compliance.”

Because MacPherson said the decision came from Automattic, dissidents on the other side of the issue are saying that the company is acting in its own interests, as the decision was delivered without much explanation beyond an audit not fitting into Gutenberg’s timeline.

Gutenberg appears to be a commercially-driven add-on primarily intended for a8c’s benefit and should probably be treated as such by the community wherever that isn’t already true. pic.twitter.com/c3yFImB5XL

— Another Day, Another Doug (@zamoose) October 16, 2018

So disappointed in @automattic’s decision to forego an independent accessibility audit for Gutenberg. Shipping with known issues is the wrong way to go. Users with disabilities are more important than that! https://t.co/Z4diHmv4GX

— Marcy Sutton (@marcysutton) October 16, 2018

“The idea of accessibility being punted to meet a release deadline is what people have been worried about for over a year, and those concerns have not been alleviated,” Morten Rand-Hendriksen said during a recent Accessibility team meeting on Slack before the audit was post-poned. “A clear message about what would happen should the audit come back with substantial issues and recommendations would greatly improve communication and take some of the tension out of the conversation in my opinion.”

In response to one contributor asking how the audit might affect Gutenberg’s timeline, MacPherson said he doesn’t have veto power over the release, nor does he have the data to make that assessment.

“I’m still not convinced there are sufficient Accessibility issues that prevent a release,” MacPherson said. “If the second point changes, I’ll relay that info. I plan to be an advocate, but I don’t set the timelines and I also don’t have solid data around accessibility. That’s the point of the audit: so we can speak from a place of hard data.”

An independent accessibility audit would have revealed whether the team’s current perceptions of Gutenberg’s lack of accessibility are accurate or inflated. It would also give the team’s new leadership the data he needs in order to make the most accurate recommendations regarding its readiness for the world. Kevin Hoffman advocated for pushing on with the audit regardless, in case WordPress 5.0 comes on a later timeline.

“The January 22, 2019 date would allow more than three months between today and the release of 5.0 to complete an audit and take action,” Hoffman said. “The reasons above suggest that we cannot get an audit completed and significantly improve accessibility in three months time. If true, that is all the more reason to start the process now and respond to the audit by fixing as many issues as we can before 5.0 releases.

“The idea that the timeline will become less rushed after 5.0 (when it’s in the hands of real-world users who need it most) makes no sense at all.”

As a blind #WordPress user & sometime dev I really appreciate your work & it is a real tragedy that the leaders of WordPress & this project didn't build in #a11y from the very beginning – Any good team knows it is much harder to fix in hindsight

— Dale Reardon (@DaleReardon) October 9, 2018

Absolutely this. Like most prior #WordPress admin functionality, #Gutenberg has been designed and built with hardly any thought for #a11y. And the WP A11y Team have been left the job of trying to help retrofit it. This always ends badly – in burn out, and half-baked solutions. https://t.co/UKMR442gM5

— CoolfieldsConsulting (@coolfields) October 10, 2018

While Twitter’s court of public opinion cannot answer the question of whether or not Gutenberg is accessible, an independent audit would give contributors a good shot at resolving the most critical issues.

“I really like the idea of a professional audit, though I don’t recall us ever doing one of these in WordPress, certainly not a condition for a release,” Gutenberg merge lead Gary Pendergast said. “I’d love to see something like it happen at some point. WordPress has always tried to get most of the way there on accessibility by sticking to common patterns and semantics, with the difference covered by key efforts of volunteers everyone on the Accessibility team doing testing and filing actionable bug reports. Gutenberg’s move to being an entirely JavaScript-based application has made it harder to apply those patterns, but we can work together to establish new patterns, a new baseline.”

Although there is no precedent for it, in this instance where Automattic’s perception of the editor’s accessibility differs wildly from that of the community, an outside audit might mitigate some of the conflict surrounding the issue.

Pendergast said that despite best intentions and prioritizing accessibility, there is a possibility the Gutenberg team may not be able to deliver an “acceptable UX for assistive technology users by the time 5.0 is released.”

“I’m sorry,” Pendergast said. “Despite the best intentions of everyone on the Gutenberg team, we haven’t done enough. I can honestly say that accessibility has always been a priority, but it hasn’t been a high enough priority, and we’ve done a poor job of communicating where accessibility has been improved. I mentioned some of those improvements in my earlier comment, but those improvements are of no benefit if we haven’t hit the baseline accessible experience.”

The challenge of building in accessibility at the design stage, instead of retrofitting it after the fact, is one that WordPress is still struggling to get right in the Gutenberg era. Accessibility experts with React skills are few and far between, so it’s not easy to get fixes for all the issues testers are finding.

“In some meetings we’ve discussed how to make accessibility integrated in the design process (design in its broader sense) since the beginning,” Accessibility specialist Andrea Fercia said during the team’s most recent meeting on Slack. “This is certainly an area were our communication and knowledge sharing should improve.”

zTheme SCSS

Drupal Themes - Wed, 10/17/2018 - 11:13

SAAS Bootstrap Based Starter Theme for developers

WPTavern: First Look at The Twenty Nineteen Default Theme

Wordpress Planet - Wed, 10/17/2018 - 02:45

Allan Cole, a WordPress Theme Imagineer at Automattic has published the first glimpses of the Twenty Nineteen default theme slated to ship with WordPress 5.0. Cole is leading the theme while Kjell Regstad who does Product and Editorial Design at Automattic will be a design coach.

Twenty Nineteen Blog Post Layout

The theme takes a minimalist approach that’s a good fit for writers and can be adapted for simple business sites as well. Twenty Nineteen doesn’t have a sidebar but will have an area in the footer to display widgets.

The theme will have full compatibility with Gutenberg when it’s released. It will also contain Front-end and Back-end editor styles. This will allow the presentation of content in the back-end to closely resemble how the finished product will look like. 

Twenty Nineteen is based on the Underscores and Gutenberg starter themes. SASS is used to keep styles in-sync between Gutenberg and the front-end experience which Cole notes is, “not usual for a default theme and open to debate.”

With WordPress 5.0 scheduled for a November release, Twenty Nineteen is on a fast track development cycle. A release candidate is expected to be available at the end of this month.

To keep tabs on development, you can monitor the project’s GitHub page. GitHub will be used to develop Twenty Nineteen until it’s ready to be merged into core. At that time, the GitHub page will be deprecated as development moves to WordPress Core Trac.

Dev meetings that last a half-hour will take place every Tuesday at 12PM EDT in the #core-themes Slack channel. It’s worth noting that if Twenty Nineteen is not ready in time for the planned November 19th, release of WordPress 5.0, it will be removed and released at a later date.

WPTavern: ACF 5.8 Beta 1 Introduces Blocks Feature, Release Slated for November

Wordpress Planet - Tue, 10/16/2018 - 18:05
photo credit: Adabo! 3d printed tetris blocks(license)

Advanced Custom Fields is now actively testing its new block creation feature in ACF 5.8 beta 1, released this week. ACF Blocks is a feature aimed at PHP developers who have not taken the deep dive into JavaScript yet. It essentially offers a shortcut to creating custom blocks using PHP and HTML instead of JavaScript.

“We believe that ACF Blocks is one of the more important features ever added to our plugin,” ACF representative Eric Karkovack said. “It levels the playing field and allows more developers to take advantage of Gutenberg’s key feature.” The feature was designed to allow WordPress developers who use ACF to maintain their current workflow for extending the editor.

ACF Blocks allows developers to register a custom block type from a functions.php file. From there they can create a field group and use any ACF fields in the block. Rendering the block is the same process that’s used for displaying custom fields, with the notable addition of wrapping the HTML + PHP in a function.

The ACF team plans to include the new blocks feature in version 5.8, which is anticipated to arrive in November.

Creating custom blocks in this way seems like a stopgap measure for developers who haven’t had the time to learn how to extend Gutenberg before WordPress 5.0 arrives. This feature may be a useful abstraction for those who need to maintain their current workflow with ACF but it postpones the inevitable for developers who want to be truly proficient at extending the new editor. JavaScript skills will be required to properly understand what is going on under the hood.

Matt: The Importance of Meeting In-Person

Wordpress Planet - Tue, 10/16/2018 - 16:40

I recently returned from Orlando where Automattic hosted its annual Grand Meetup where nearly all of our 800 employees from around the world, spend a week together in the same place. (And yes, we’re hiring.)

Despite being a fully distributed company, I believe it’s still important to meet face-to-face — just not every day, in the same office. The Grand Meetup is our chance to get to know the people behind the Slack avatars and build relationships that can carry us through other 51 weeks of the year, when we’re working from more than 65 countries. It’s so much easier to hear the nuance in someone’s chat messages or p2 posts if you’ve hung out with them at Harry Potter World, or learned about their family, pets, and hobbies during a flash talk.

Photo by Paul Jacobson

The week can be mentally exhausting, given that you’re often meeting many people for the first time. But we urge people to take it at their own pace, and the results are well worth the effort. Our data team actually studied the impact of the Grand Meetup on our work relationships — the connections established between coworkers using our “Meetamattician” tool were demonstrably closer after the meetup:

Before the Grand Meetup. After the Grand Meetup.

This year we were proud to welcome some incredible keynote speakers: Wild author Cheryl Strayed talking about creativity and writing; Automattic board member Gen. Ann Dunwoody, the first woman in U.S. Army history to achieve the four-star officer rank; Ari Meisel on delegating and automating your life; and Dan Harris, author of 10% Happier, on the panic attack that led him to embrace meditation and mindfulness.

Photo by Leif Singer Ann Dunwoody. Photo by Luca Sartoni Ari Meisel. Photo by Luca Sartoni Photo by jessicacg

YG Sprint

Drupal Themes - Tue, 10/16/2018 - 06:42

YG Sprint is a modern drupal 8 theme.

Features

  • Drupal 8 core
  • Bootstrap v3.3.7
  • Blog
  • Portfolio
  • Testimonial

Live Demo Download Demo Site

It is highly recommended to install the demo site and customize it to get the exact look. Here is the link for the documentation to install demo site

Demo login credentials : admin / admin@123

Thanks for checking out our theme. We can install the theme in your server for free!

Contact us for free installation


Other YG themes

  • YG Booster: A free bootstrap based Drupal 8 theme with modern design for products and business
  • YG Newage: an app landing page theme built using bootstrap
  • YG Agency: Theme perfect for portfolio and agency websites
  • YG Flew: Theme perfect for business websites


Credits

Drupal theme by Young Globes

WPTavern: WordPress Privacy Contributors Begin Work on V2 Roadmap, Form Cross-Platform Working Group

Wordpress Planet - Tue, 10/16/2018 - 00:30
photo credit: Infosec Images Privacy blue(license)

Contributors to WordPress’ core Privacy component are collaborating on a V2 roadmap to address broader privacy and data protection issues that fall outside of legal requirements. The group organized at the beginning of the year to work on GDPR-specific objectives but has since expanded its scope to tackle concerns that are not attached to any specific piece of legislation.

The Privacy team meets weekly and has approximately a dozen contributors who show up regularly to work on tickets and issues. The working V2 roadmap identifies a list of common international privacy concerns, such as data minimization, data integrity, transparency and notice, and contributors will explore their impact on a few core focus areas:

  • Core privacy features
    • Gravatar privacy controls
    • Embed privacy controls
  • Plugin privacy
    • For administrators
    • For developers
  • Consent and logging
  • WP-CLI support
  • Multisite support

The team has agreed to use a Privacy by Design (PbD) approach, which uses a proactive framework to anticipate privacy issues before they are a problem for the user.

Privacy team contributors are also monitoring two specific pieces of legislation that may impact WordPress site owners in 2019 – the US California Consumer Privacy Act (CCPA), and the EU ePrivacy Directive overhaul. They plan to examine specific requirements once that information is available and will assist site owners in reaching compliance.

New Privacy Working Group to Facilitate Collaboration across Open Source Communities

At Drupal Europe 2018 a group of WordPress and Drupal contributors met to discuss the possibility of welcoming teams from major open source projects to work together on shared concerns. WordPress Privacy team contributor Heather Burns attended the first test run of the working group in the Open Source Lounge at the conference.

“For the working group we have the big three – Drupal, WordPress, and Joomla – and we also spoke with representatives from the smaller projects like Neos and Typo3,” Burns said. “We’re all dealing with similar issues but from different approaches.”

Burns said one of the goals of the working group is to push the idea forward that privacy is a common, positive, proactive value which can be taught and shared across projects. Members will discussion questions like whether privacy fixes belong in core or modules, how privacy notices pull information from different plugins and modules, and what laws are coming up that would require open source CMSs to build in some functionality in advance.

“It’s a way of pooling resources, code libraries, and briefings, as well as giving us a forum to share experiences,” Burns said. “For example, we’re going to arrange for Drupal’s privacy lead to give a live video demo of their GDPR tools to our core group, and we’re going to do the same for them.”

The privacy working group is being set up through the Drupal community structure and members are in the process of coordinating some funding. More information on funding will be available in the next few weeks.

Privacy Contributors Seek to Change the Perception of Privacy to a Positive, Proactive Value

In addition to collaborating across the broader open source community, the privacy working group endeavors to educate their communities on the inherent value of privacy instead of simply focusing on the consequences of companies being forced to pay a fee if they don’t meet legal obligations.

“We’re very keen to also shift the perception of what privacy is, and that it’s not just seen as being about negative legal obligations for GDPR, CCPA, etc.,” Burns said. “We want people to think of privacy like accessibility: just the right thing to do for user protection.”

Burns speaks about privacy at WordPress and Drupal conferences and how projects can have differing cultural, historical, and legal approaches to privacy. Cultural barriers to the recognition of privacy as a core value is one of the privacy team’s biggest challenges in advocating contributions that respect and protect users’ rights.

“What I’m proudest of this year is helping people to understand each other better,” Burns said. “We all come to the table assuming we share the same cultural, historical, and legal views of what privacy means and what role it should play, when the truth is there are wildly different views held even within project teams.

“To paraphrase that awful quote, we don’t know what we don’t know. What I do is help people to understand where we’re all coming from and what we don’t actually know. From there, I define what a healthy approach to privacy should involve outside reactive legal obligations, using a methodology derived from a number of international frameworks and treaties on privacy. It’s a matter of inspiring people to realize that as open source project contributors, we are people of enormous power and influence over privacy on the web. The actions we take within our projects, however small, can help to protect people from those who would use their data to hurt them. That’s the most important thing any developer can ever do.”

YG Architect

Drupal Themes - Mon, 10/15/2018 - 11:34

YG Architect is modern Drupal theme developed to help you to create a stunning website for Portfolio.

Features

  • Drupal 8 core
  • Bootstrap v3.0.0
  • Portfolios

Live Demo Download Demo Site

It is highly recommended to install the demo site and customize it to get the exact look. Here is the link for the documentation to install demo site

Demo login credentials : admin / admin@123

Thanks for checking out our theme. We can install the theme in your server for free!

Contact us for free installation


Other YG Business themes


Credits

Drupal theme by Young Globes

Beauty Blog Theme

Drupal Themes - Sat, 10/13/2018 - 15:05

WPTavern: Contributing to Gutenberg: A New Contributor’s Experience

Wordpress Planet - Sat, 10/13/2018 - 02:32

The following is a guest post by Chris Van Patten who shares his experience learning and contributing to Gutenberg. There’s been a lot of talk of Gutenberg’s higher barrier to entry for new contributors. Van Patten is the founder of Tomodomo, a digital agency for magazine publishers.

Over the past few months, but especially over the last few weeks, there has been extensive conversation about the barriers to entry present in contributing to the upcoming Gutenberg editor for WordPress.

Of course, everyone’s experiences are subjective and unique. I can’t pretend to understand what everyone has felt. But my experience has been different than what some folks have been articulating, and I wanted to share my own take.

The Early Days

I’ve used WordPress for close to half my life; almost 15 years now. I remember some of the earliest versions of WordPress: the classic theme, the advent of Kubrick, MP6, up through today.

Early Days of the WordPress Backend

Like many in the community, I’m entirely self-taught. I have no background in computer science, and have no formal instruction under my belt. I picked up code through trial-and-error, tweaking files and breaking my site as I wanted to make changes.

Since those early days, WordPress was always my CMS of choice both for personal projects and for clients with my agency Tomodomo. But even though I had committed to the WordPress platform, my contributions back were limited.

The rules, rituals, and etiquette around posting on Trac seemed arcane and illegible. To this day, I could not make an SVN patch if my life depended on it. And much of the core code, imbued with years of history and backwards compatibility, was hard for me to pick apart.

So instead, I contributed in other ways: open sourcing simple custom plugins I was building, organizing WordCamps and meetups, and speaking at WordCamps around the globe. But it always bothered me that I couldn’t find a way to get those elusive ‘props’.

(Okay, so I did actually get props on one release, but I am convinced it was a mistake; I had neither opened the ticket or provided a patch.)

Going… Going… Gutenberg

When I first learned about Gutenberg and started exploring, I was apprehensive. At first it seemed scary. My JavaScript abilities didn’t extend beyond jQuery. React was inscrutable and it seemed like I’d need a doctorate to understand some of the ideas behind it. I still don’t understand how Webpack works its magic. Does anyone, really?

But the possibilities of the new block interface were too enticing to ignore, so I started diving in and figuring out how it worked. In those halcyon days (aka earlier this year), Gutenberg was still pretty rough around the edges, and there were a lot of opportunities for improvement. I started lurking on the GitHub repo, reading issues, examining the code, and generally trying to wrap my head around what the heck was going on.

As I was playing around with Gutenberg for a client project, I started reporting issues: simple things, like user interface bugs. I started commenting on tickets, usually offering suggestions for a particular feature, trying to advocate from the perspective of independent developers.

I even filed my first pull request! It was simple. I updated the README to include the day and time of the weekly #core-editor meeting (Wednesdays at 1pm UTC, if you’re wondering). It was an inauspicious beginning, but I was excited to get it merged.

Over time, my knowledge grew. It was like my early days in web development, learning a CSS property here, and an HTML element there. I learned what a component was and how you could reuse them in different situations. I learned about JSX, and ES6, and some of the other crazy acronyms you encounter in Gutenland.

As I was building more with Gutenberg, I was also finding new ways to build Gutenberg itself. I was able to understand more of the discussions, and offer my thoughts and suggestions. I started opening pull requests, largely dealing with design issues but also solving small bugs and quirks. I made a point of attending the weekly meeting I had previously added to the README, chiming in when I felt I had more perspective to share.

Today I have 25 new issues and 27 pull requests under my belt, in addition to dozens of comments on existing tickets. I’m a ‘member’ of the Gutenberg team on GitHub, and try to find time every day to triage new bugs or review pull requests. It took me most of the year to get to that point and it certainly wasn’t always easy. I still have so much to learn.

When I hear about how difficult it is to contribute to Gutenberg, I can’t reconcile that with my own experience. That’s not to say it’s a breeze: Gutenberg does things very differently than WordPress core, and there is undoubtedly a learning curve.

Advice for Contributing to Gutenberg

If you aren’t comfortable coding from day one, there are so many other ways to contribute. Read through issues and add your own ideas and suggestions. Try testing and replicating bug reports. Hunt through inline documentation for typos and grammar corrections. All of these are valuable, and always appreciated.

As you absorb the Guten-way through osmosis, you’ll find that the code isn’t as hard as you think — it’s just different. The intelligent people who build Gutenberg have done a great job at hiding away the ‘computer-science’ bits so the rest of us don’t have to worry about data binding and other complex ideas. I still cannot explain state management, data stores, or context APIs but I have managed to find small areas of the code to improve.

This isn’t to deny anyone’s frustration or confusion with Gutenberg and its development. Documentation is still lacking in many places. Some of the APIs are unintuitive. The tooling isn’t the simplest to set up. These are real problems, and I don’t want to pretend they don’t exist; we can undoubtedly do more to make Gutenberg development easier.

And of course I have privilege to check: I’m lucky to have the time to spend in the GitHub repo, experimenting with code, and participating in weekly meetings. I recognize that’s not a reality for many people.

If you can’t find the time, the Classic Editor will continue to be an option, and there’s no shame in prolonging the upgrade. It may take time for the Gutenberg experience to be as intuitive as we would all like it to be, and waiting for that is totally reasonable.

But if you open yourself to some new ideas about what WordPress can be, and can make the time, you may end up surprised at how easy it is to contribute. If you get stumped, pop into #core-editor or the forums. Don’t be afraid to post a bug report or suggestion; we might consolidate it with another issue if it was previously reported, but the additional information is still valuable. Every experience matters.

I’m incredibly excited about the future of WordPress with Gutenberg and to finally be a real WordPress contributor. We have a long way to go, but that means there are still many exciting ways to make a difference. The project will only get stronger with more independent community voices chiming in.

I hope you’ll join us!

WPTavern: WordCamp for Publishers Seeks Host City for 2019

Wordpress Planet - Fri, 10/12/2018 - 23:32

WordCamp For Publishers’ distributed organizing team is looking for a new host city in 2019. The industry-focused camp gathers together professionals who use WordPress to manage publications. This year’s successful event hosted speakers who highlighted important topics, such as ethics in journalism, the open web, AMP, Gutenberg, and communication between tech and editorial teams.

The inaugural edition of this camp was held in Denver (2017), followed by Chicago this year. A few people on social media have lobbied for cities like Los Angeles and Detroit, but the decision rests on the availability of local organizers to handle the logistics of the event. These duties include facilitating venue coordination, swag delivery, and other things that need to happen on the ground.

Based on the call for host city applications, it seems that applicants do not need a large team behind them, since there’s already an existing organizing team. Applicants need only the availability to coordinate local preparations.

Individuals or teams who are interested to host the event in 2019 can submit an application. Organizers said they have a preference for cities that are “underrepresented media markets” where attendees may not see as many of these types of events.

WPTavern: Learn How to Build JavaScript Plugins for WordPress with Riad Benguella’s Starter Kit/Tutorial

Wordpress Planet - Fri, 10/12/2018 - 20:21
photo credit: Krzysztof Puszczyński

Riad Benguella, the technical lead for phase 2 of the Gutenberg project, has published an educational resource to help WordPress developers get started building JavaScript plugins. The WordPress JavaScript Plugin Starter is unique in that it is built as a tutorial, not just a boilerplate. The GitHub repo contains eight commits that have been structured to explain each step along the way. Benguella designed the repository to answer the following questions:

  • How do I quickly setup a WordPress environment and how do I bake it into my plugin?
  • How do I define a WordPress Plugin?
  • How do I load a simple JavaScript script in WordPress?
  • How do I bundle my JavaScript files?
  • How do I use advanced JavaScript features like JSX?
  • How do I build a production-ready version of my plugin?
  • How does all this fit together?

Benguella predicts a shift in the WordPress development community, as JavaScript skills become essential for extending core’s rapidly evolving JS-based UI. Plugin architecture is changing to accommodate that.

“Plugin developers are required to use JavaScript more in order to extend the editor,” Benguella said. “Most blocks need to be developed using this technology. The modules Gutenberg provides (Components, data module, i18n, apiFetch…) will also encourage developers to extend other parts of WP-Admin in JavaScript. Instead of writing HTML/CSS screens from scratch and rendering them from the server, developers are able to bootstrap and prototype fully accessible new screens in WP-Admin by composing these components in a small number lines of code.”

Benguella’s WordPress JavaScript Plugin Starter resource demystifies the plugin creation process with detailed explanations of each step throughout the readme file. It’s a valuable resource for PHP developers who are just getting started transitioning into building JavaScript plugins.

Ebiz Grazitti Theme

Drupal Themes - Fri, 10/12/2018 - 10:14

Ebiz Grazitti is a flat responsive business theme designed by Grazitti Interactive. This theme could easily be used for any type of personal website, corporate, business, marketing etc. Theme elements are easy for users to understand and make navigating your website a pleasure. This theme is completely free and contributed by Grazitti team.

Features
  • Responsive, Mobile-Friendly Theme
  • Google Font and nice typography
  • Drupal standards compliant and Supported standard theme features
  • One, two and three columns layout
  • Flex Image Slider with customize facility
  • Post comment and reply styles
  • HTML5 & super clean markup
  • Detailed CSS rules for Typography, Forms Elements, Node Teaser, Comments, etc.
Contact Grazitti Interactive for :
  • Drupal custom development
  • Decoupled Drupal
  • Drupal website design & development
  • Drupal website migration
  • Drupal Performance Audit
Sponsored by Grazitti Interactive

Connect with Grazitti Interactive

                        

WPTavern: WordCamp Nordic 2019 to be Held in Helsinki, March 7-8

Wordpress Planet - Fri, 10/12/2018 - 04:43

After many years of planning, WordPress’ Nordic communities are finally getting a regional WordCamp. The first WordCamp Nordic 2019 is set to be held in Helsinki, Finland the weekend of March 7-8 at the Paasitorni Congress Center.

“Some folks from the Norwegian community came up with idea in 2016,” lead organizer Marco Martins said. “Then in a WordCamp Stockholm we got people together and we discussed the idea. But it was earlier this year in WordCamp Jyväskylä (Finland) that we decided to commit to it and organize it. After that I went to Oslo to discuss personally with people from the Nordic countries and we came to an agreement. We gathered a team from the different countries and here we are.”

The international organizing team is planning for approximately 600 attendees but the venue has the capacity for 800 people, if ticket demand is higher than expected. Paasitorni is an 111-year old complex brimming with historic significance. The Art Nouveau style building is also known as the Helsinki Workers’ House, previously serving as leisure premises for the working class. It also provided the headquarters for the Red army during the 1918 Finnish Civil War. In the 1990’s it was remodeled to be a conference center and now includes a hotel and restaurants on premises.

Finland has a stable and active WordPress community, which Martins said was one of the factors in the decision to host the first WordCamp Nordic in Helsinki. Regular meetups are held across the country in Turku, Tampere, Jyväskylä, Oulu, and Seinäjoki. The local WordPress Helsinki Meetup group has more than 900 members with average attendance of 20-60 attendees each month.

Helsinki has hosted two previous WordCamps, both averaging more than 220 attendees. Three other WordCamps were held in Turku, Tampere, and Jyväskylä, along with an unofficial WP Metsä (“WP Forest”) in 2017, featuring cabins, lakes, outdoor tubs, sauna, and lightning talks by the fire. According to local organizers, Finnish camps have always sold out sponsor packages and tickets relatively fast.

WordCamp Nordic will host a Contributor Day on March 7, followed by the main event on March 8. Organizers expect attendees from Sweden, Norway, Iceland, Denmark, and other countries, with likely the most attendees from Finland. All the sessions will be conducted in English.

“While Nordic countries have very close ties both culturally and historically, one of the challenges we often face when thinking of attending a local WordCamp in the region is language,” co-organizer Niko Pettersen said. “Even though most Finns learn Swedish in school, the language often stays at a basic level and doesn’t extend to technical things such as WordPress. By having all of our talks in English, we’re hoping to level the playing field and hopefully attract more people from all around the world to come and listen to what these communities have to share.”

Organizers are still in the process of discussing what topics they would like to see, but Pettersen said many Nordic countries tend to focus heavily on education, the environment, and healthcare. “Also with the EU Accessibility Directive coming to full effect in the coming years, I have a feeling a11y will be one of the major topics we will want to cover,” Pettersen said.

WordCamp Nordic will also be hosting an informal Activity Day on March 9th where attendees will be welcome to join various activities, such as karaoke, cycling tours, trips to islands, and other other events coordinated by the community and sponsors.

“It is something that Oslo has been doing informally the day after the camp and the feedback has been great so we thought it would be a good idea to have the activity day for people to do something together and experience something Finnish in more informal way,” Martins said. “We are planning the activities, but sauna for sure, because Finland.”

One unique aspect of Finnish culture is the national obsession with saunas, and WordCamp Nordic organizers are ready to introduce attendees to Finland’s favorite pastime.

“Traditionally saunas have been a place to cleanse the body and mind, but more recently travelers have discovered it is also a great place to meet locals, share experiences and get tips on where to go next,” Pettersen said. “If you’ve never been to one, I warmly suggest you extend your stay over the weekend as we’re planning on taking groups to some of the new public saunas in Helsinki during the Activity Day the day after the event.”

WordCamp Nordic Organizers Aim to Revitalize Local Communities by Fostering New Meetup Groups

Finland is the birth place of many open source projects, including SSH, MySQL, Linux, and IRC. WordCamp Nordic organizers hope to inspire that same spirit of collaboration among neighboring WordPress communities by hosting the regional camp.

“One of the goals we listed in our initial proposal was to focus on revitalizing the local communities in the region and help to form new meetup groups by getting the organizers and interested parties together during Contributor Day,” Pettersen said. “We saw our meetup scene grow in Finland from one to six in the space of a few years largely thanks events like these and good mentoring from the community at large.”

Organizers plan to keep the camp running in future years but have not yet settled on the selection process for future host cities.

“As long as WordCamp Europe is organized during the summer, I have a feeling future events will be leaning towards spring/autumn or winter,” Pettersen said. “The selection process is still up for debate, but I imagine whoever feels like this is their calling will have the full support of the Nordic community to carry on where we left off.”

WordCamp Nordic joins a small list of regional WordCamps that have become can’t-miss, enriching events for many in the WordPress community. Tickets will go on sale at the end of October. Follow @WordCampNordic on Twitter or subscribe to the newsletter to get notified.

Pages