Remote work is an increasingly popular choice for employers and employees: employers get to enjoy the pick of the best talent from across the globe, and employees get the flexibility of working from wherever they like. For most remote workers (including me), this means working from home. Working from home or working remotely in general is on the rise: between 2012 and 2016, the number of people working remotely in the US rose from 24 to 31%, and in 2016 43% of Americans spent some time working from home (this was up on previous years).
Stories about remote work from home often paint an incredibly bright picture: of flexible hours, being closer to family, and saving an hour a day on commuting times. These are some of the benefits of remote work, but this paints an inaccurate picture. Working from home can be really hard:
Bitcoin has taken the world by storm ever since its inception on January 5, 2009. However, 2017 has really been what some have called “the year of Bitcoin”. You would have to be living under a rock not to have heard of it by now. The value of Bitcoin has been growing insanely fast and doesn’t appear to be slowing down anytime soon. If you’re enthralled by the idea of a cryptocurrency, and would like to learn how to add a Bitcoin donate button into your WordPress site, then you’re in the right place. But first, in case you aren’t familiar with it, or need a refresher, a few words about Bitcoin and what it is.
What Is Bitcoin?
In short, Bitcoin is a completely virtual currency, which means that you can’t pay Bitcoin in bills, notes, or even a real coin. All payments occur in cyberspace. Secondly, there’s a huge amount of it, with the dollar equivalent of over $1.5 billion in Bitcoin circulating today — numerous transactions take place every minute.
You can pay for anything and everything with Bitcoin as long as the merchant in question accepts it. That includes marketing services, website memberships, condos, car rentals, or even a
Most WooCommerce store owners are trying to get their products in front of as many eyeballs as possible. More traffic is always good because it means a better chance to make a sale, right? This post isn’t for those WooCommerce store owners.
Instead, I’m going to talk about a more niche use – password protecting certain WooCommerce product categories to restrict access.
Why the heck would you want to password protect WooCommerce categories? There are actually plenty of situations where it makes sense. Here are a few that come to mind right away:
Wholesale stores – if you’re a wholesaler, you probably don’t want your prices and product lists publicly available, so password protection lets you restrict access to only authorized shoppers.
Private client areas – you can create separate categories for individual clients to sell a unique set of products to each client.
Members-only store – you can create an entire store that’s only available to members.
Mix-and-match – you can leave most of your store public like normal, but password protect certain restricted products that you don’t want everyone to be able to see.
Hey everyone! We’re getting settled back in after an amazing trip to WordCamp US in Nashville. Beaver Builder is a distributed team and it’s always an awesome opportunity seeing the team face-to-face. Matt Mullenweg, the co-founder of WordPress and CEO of Automattic, gave his annual State of the Word speech and Gutenberg, WordPress’ new editor project, was the hot topic of the weekend. The #1 question that we all got over the weekend was, “what do you think about Gutenberg?” We wanted to bring that conversation here to the blog and invite you all to participate.
Matt mentioned that they’re designing Gutenberg for new users. We believe there’s always going to be another level of customization and features that Page Builders can provide.
The Gutenberg Demo
Gutenberg has come a long way since it was announced last year. If you’re not familiar with Gutenberg yet, I’d encourage you to check out the demo portion of the SOTW. It’s impressive! Matias mentions that he combined several unfinished features and, in doing so, he paints a picture of a much more finalized product than the iterations we’ve seen previously. There was a growing murmur of excitement in the crowd.
Perhaps you have heard the phrase Time to First Byte but somehow the concept seems to escape some people. Be it because it seems incredibly tech oriented or because it seems like an abstract concept, not that important to everyday use. Nothing could be further from the truth. Time to First byte is not actually a concept or an idea that only the techie people should understand. Everyone should be able to grasp it’s meaning and apply it into practice.
In this article I’m going to explain to you, in few words: what is Time to First Byte, how does this affect your site and why you should pay considerable attention on this subject if you want to give your readers the best experience possible when browsing your site.
What is Time to First Byte?
Time to first byte (TTFB) is a measurement used as an indication of the responsiveness of a webserver or other network resource.
TTFB measures the duration from the user or client making an HTTP request to the first byte of the page being received by the client’s browser. This time is made up of the socket connection time, the time taken to send the HTTP request, and the time taken to get the first byte of the page. Although sometimes
A while back, Google purchased the .dev TLD (Top Level Domain). At that time, they announced that they had no plans for it and that they were only going to use it for internal purposes. For years, the .dev TLD was primarily used for developers and designers to use in their local development environments. It was considered general acceptable use and, as a result, developers everywhere are now running sites locally which may now be affected. Recently Google announced that in a soon to be released update to Chrome, they will be forcing .dev to HTTPS. In short, this means that if you are running local sites using .dev AND running Google Chrome, you will find your site unreachable. Fortunately, there are a couple of options which are fairly simple to implement to get around this issue. Keep in mind that since .dev has been a standard TLD for local development for some time, this new policy by Google will affect you whether you are using DesktopServer or any other local development tool which utilizes the .dev TLD. This issue is NOT specific to DesktopServer.
Solution #1 (Any Local Host Development Platform): Stop Using Google Chrome for Local Development
Let’s start with the easiest