Some good thoughts but I mainly submitted this to highlight how snappy Aaron's site is.. What kind of magic is that?
While I've used WordPress in many ways over the last nearly ten years, I primarily spend my time working on two publications: Scary Mommy and Cafe. "Big Media" publications have challenges and use cases that are different than standard WordPress sites. As Gutenberg continues to evolve, there are a number of use cases that I see as needing to be accommodated. Most of these are things that don't need to be solved "out of the box", but that the extensibility of Gutenberg should accommodate. It's possible that some of these use cases are already accounted for, but that that the documentation on them is lacking.
Before "Publish" can be pressed, a number of steps need to happen. This could be selecting a featured image, making sure some taxonomies are properly filled out, or that there is 2nd sign off. This takes the form from the super basic such as what make.wordpress.org sites use ( an "Are You Sure" checkbox that must be checked before the publish button is enabled) to the complex custom plugins that are prevalent.
The important part is that there needs to be a documented and extensible way of only allowing posts to be published
Too much cash. Geez, tough problem to have, I guess :)
A start-up often tipped as being one of the country's next "unicorns", Envato, has more cash than it needs to keep growing, so it has decided to make the unusual move of sharing its profits with its staff. The bootstrapped online graphics marketplace was founded 11 years ago in the garage of Collis Ta'eed's Bondi home with his wife Cyan, their long-time friend Jun Rung and two years later his brother Vahid Ta'eed. Since then it has emerged as one of the most profitable tech start-ups in the country.
In the 2016 financial year the company recorded $US29.4 million ($37.1 million) in net profit. While it is yet to file its 2017 numbers, it is expected that profits will be similar.
Envato chief executive Collis Ta'eed said he wasn't aware of any other start-ups having profit shares with their staff, partly because many are not profitable.
"We've been profitable for pretty much as long as we've been around, and we're bootstrapped, so last year at our 10-year anniversary we stopped and reflected and thought about what we're doing and where it's going and with us being profitable enough, we'd always wanted to reward the staff and people who contribute each year," he said.
While WordPress is trying to be more like Wix (Gutenberg) it seems that Wix is trying to be more like WordPress (Wix Code). Whats your take on it?
In Brad's last article he described how to create a self-signed certificate that works locally without browser privacy errors. In this article, he discusses how to simplify that by creating your own Certificate Authority to sign certificates and simplify the whole process of getting HTTPS working locally.
In my last article I described how to generate your own self-signed SSL certificates and add them to macOS Keychain so that your browser doesn’t give you a privacy error. Soon after it was published, Ross McKay made a very interesting comment on that article:
If you have a few servers you need to do this with, you can just create yourself a CA (Certifying Authority) certificate and load that instead. Then your self-signed certs, signed by your CA cert, will all be accepted without you needing to load each one.
So basically he’s saying that I can be a certificate authority (CA) like Let’s Encrypt, Amazon, Verisign, Comodo, etc but just for my local network. How did I not know about that? So cool. But how does it work exactly?
How It Works
After some research I think I get it now. To request a certificate from a CA like Verisign, you send them a Certificate Signing Request (CSR), and they give you a certificate in return that they signed using their root certificate and private key. All browsers have a copy (or access a copy from the operating system) of Verisign’s root certificate, so the browser can verify that your certificate was signed by a trusted CA.
Glad to see this article come out. When speaking to many friends in WP community, these stories about GD's past frequently come out. Since joining the company 10 months ago I could not see any of that. If anything GD is one of the healthiest work environments I've ever seen and the new leadership that took over 4 years ago did fantastic work to turn the company around. PS. The screenshot shows some of the dear colleagues I work with every day
A few years after Blake Irving became chief executive of the internet company GoDaddy, he spoke at a conference where the jeers started almost immediately. Attendees were particularly offended by GoDaddy’s history of sexist television commercials, which featured women in wet bikinis and innuendos so graphic some stations had refused the ads. But when Mr. Irving tried to explain that those advertisements, created by his predecessor, had been discontinued, and that he had been hired, in part, to change the firm’s culture, he was mocked.
“Every time Blake quotes Sheryl Sandberg or calls himself a feminist, throw something at his head,” one person shouted.
Which is why it was surprising when Mr. Irving appeared as a keynote speaker a year later, in 2015, at the Grace Hopper Celebration of Women in Computing — and received a standing ovation after detailing GoDaddy’s efforts to become one of the most inclusive companies in tech.
By then, GoDaddy had been recognized as being among the nation’s top workplaces for women in tech. The company’s policies on equal pay, its methods for recruiting a diverse work force and its approach to promoting women
SiteLock Acquires Patchman’s Malware and Vulnerability Detection Technology, Expands WordPress Customer Base to 4 Million
Big new from Sitelock acquiring Patchman. These kinds of aquisitions we'll see more and more of in the WordPress space as the marketplace continues to mature.
SiteLock Acquires Patchman’s Malware and Vulnerability Detection Technology, Expands WordPress Customer Base to 4 Million
SiteLock, a website security company, has acquired Patchman, a Dutch security startup that offers automated vulnerability patching and malware removal for hosting providers. Prior to the acquisition SiteLock protected 6 million sites, with 2.2 million of them running on WordPress. The addition of Patchman extends SiteLock’s customer base to 12 million sites and more than 4 million of those are powered by WordPress. Patchman detects vulnerabilities in a wide range of popular applications and quarantines and patches threats automatically. The quarantine feature neutralizes malicious files by removing them from public access. Patchman supports detection and patching for WordPress 3.x and later.
Historically, the service has not included patches for plugins but it has applied them on a case-by-case basis for high impact vulnerabilities, including a few found in WP Super Cache, MailPoet, and the open source Genericons font project. The Patchman dashboard allows users to easily track files where vulnerabilities have been detected, view status, and revert patches if necessary.
Patchman’s single focus on hosting providers gives SiteLock the opportunity to offer more options to its
Check out this interview with Ryan Sullivan; founder of WP Site Care, a WordPress support and maintenance company. "As far as high level goes, WordPress will ultimately be what we make it..." -- Ryan
You can find Ryan on LinkedIn or Twitter. This is our recent interview with him, as part of our Kinsta Kingpin series. Q1: What is your background, & how did you first get involved with WordPress?
Before WordPress, I worked as a System Administrator for a health care network. It was a Microsoft world *shudder* in a big corporation and while I didn’t hate what I did for work, I didn’t particularly love it either and started playing with some open source software in my spare time.
A friend asked me to build him a website and I stumbled onto WordPress. I knew enough PHP to be dangerous and was really familiar with server stacks, so I put something together that he was really happy with.
That little project turned into many, and then I started to notice a pattern. The same people who I built websites for kept coming back and asking for help over and over again, and their requests were all pretty similar.
I figured there may be a business opportunity if I could establish a baseline set of services and charge a monthly fee, and sure enough, it worked! About a year after putting up a website for WordPress support services, I left my job and started working on WP Site Care full
Pretty big move by Pantheon. A global CDN and automated HTTPS is pretty awesome for any WordPress website worth its salt.
Pantheon sites are now faster and more secure than ever, thanks to our new, integrated Global CDN. The Content Delivery Network, along with automated HTTPS, is included for all sites, regardless of service level and at no extra cost. We did it by integrating Fastly’s edge cloud platform seamlessly into Pantheon and configured it for advanced caching, optimized for Drupal and WordPress. Next, we added Let’s Encrypt to the mix. The result frees you up from CDN configuration or hassling with manually obtaining or renewing certificates for HTTPS. As an added bonus, we’ve improved the go live experience, complete with a new Launch Essentials guide, so it’s easier than ever to take a site live on the platform. If you’ve got an existing Pantheon site and don’t see action required to update your DNS, just open a support chat and you’ll be on your way to a faster and more secure site.
Beat the Speed of Light
Gone down the rabbit hole to optimize your site’s page load time? Seeker of the holy grail of sub-second page loads? Then you know that no matter what you do at the site level, without a CDN, the speed of light is working against you.
Some tips on helping others learn and understand WordPress. It can be very rewarding to see someone learn how to help themselves.
As WordPress continues to power more and more websites, it stands to reason that many site owners will want to learn how to use it. One of the strengths of any CMS is the ability to login remotely and add/edit content or perform other maintenance tasks. WordPress especially excels in this area and includes some built-in functionality to simplify the process. Still, with so many available themes, plugins and customization possibilities, each website has its own quirks.
So while most basic tasks in a default WordPress install can be easily learned, every item we add something new creates that much more for clients to study up on. What starts out as a fairly simple process can become a bit overwhelming to the non-designer if you’re not careful.
But never fear – there are things you can do to make the training process go more smoothly. Check out our tips below for training clients to use WordPress:
Make it Personal
Just as you may create goodies such as custom fields or custom post types to make updating a website more straightforward, you should also customize training to suit your client. That means taking into account what types of tasks they’ll handle. You should also
Learn how to make the transition from employee to freelancer and then again from freelancer to digital nomad.
Alright guys, I’ll admit it, I got a little too excited there about my new life as a digital nomad. So excited, in fact, that I pretty much wrote that entire last article of mine as a giant humblebrag which focused primarily on my accomplishments instead of providing you with any real value… #Whoops, sorry about that. Anyways, if you haven’t read that one and you’re interested in hearing about my personal milestones then by all means check it out… But, if you’d be more interested in learning how I came to make my transition to island life, then you’re in luck. I’ve written this post to help answer all of your questions.
So, here it is… My guide to location independence: in this post you’ll learn how I made my transition from full-time employee to full-time freelancer… And then again from freelancer to digital nomad.
I’d say there’s only one thing better than living my dream as a beach bum while traveling the world with my best friend, and that’s living my dream while still growing my business… Okay, well, perhaps winning the lotto and never working again does sound even better, but for those
Ionut from CodeInWP (also known for ThemeIsle) is back again with their transparency report, and this time it's their 5-year anniversary special.
Welcome to the 29th edition of the monthly transparency report (for June 2017). This is a series where I share everything that’s been going on at CodeinWP and ThemeIsle, business-wise. I try to get to as much detail as possible while also making it interesting for you to read. Click here to see the previous reports. Let’s do something unusual in this edition of the report. As you can see in the headline, it’s our 5th anniversary here at CodeinWP, or rather the 5th anniversary of us getting involved in WordPress!
Fine if you use feedburner but if not, then what?
Reduce Your WordPress Resource Usage By Hiding Your RSS Feed Link In my previous post How to Change Your Default RSS Path in WordPress Without Touching Code, I explained how I was able to move my default RSS Feed on WordPress. But I didn’t explain my reasons for doing so.
Many web hosts will limit the number of executions that can be performed against your account. An execution is counted whenever the server needs to execute a script file. In the case of WordPress users, this means PHP. Every page delivered on WordPress counts as an execution. Regular HTML files and images do not.
If your WordPress web host limits by executions and you need to get your numbers down, read on.
Feedburner manages my RSS Feed and they have for years. So the only purpose of the /feed/ path on my site was to redirect requests to my FeedBurner feed. Because this redirect happens in WordPress, a PHP file handles the task and it counts as an execution.
Caching can help, but it doesn’t help you completely in cases where a single resource gets hammered with requests. My support rep at SiteGround explained it to me like this:
…this means that the feed is cached as much as possible right now,
Quadruple your user’s experience with your very own Quick Edit fields in the WordPress dashboard! In this tutorial I’m going to show you how to make your very own Quick Edit fields to improve your client’s content editing experience.
In this tutorial I’m going to show you how to make your very own Quick Edit fields to improve your client’s content editing experience. Quick Edit Fields
You probably heard this phrase many times: “Content is king”. By all means, that’s true. No matter how awesome your site is functionality-wise, if it isn’t easy for the content editors to manage, then your site will simply suck. And we don’t want our sites to suck, do we?
Note: Before you can create a Quick Edit field, you must register a custom admin column. Unfortunately, there is currently no way to add a Quick Edit
3 things that went well over the past month and 3 things I screwed up at WP Buffs. Let's do this.
This is another chapter in a series of posts that I’ll be writing to keep you updated on what’s going on with WP Buffs from the perspective of its founder. That’s me. I’ll keep it pretty simple. 3 things I screwed up and 3 things that went well over the past month. I want to tell you about all the solid stuff happening at WPB, but I can’t stand people who only post when they have good news. It’s like looking at someone’s Instagram account and being jealous of how awesome their life is when those pictures have been carefully curated from the best 1% of their lives.
As anybody who’s run a startup before knows, what it looks like from the outside may not reflect what’s happening on the inside. A company can easily look like it’s running smoothly when in reality, it’s going up in flames.
I’ll be writing something quick like this every month so please subscribe to stay tuned in.
1. Financial Squeeze
Now that I’m on Sterling’s healthcare (thanks Equal Justice Works), it adds ~$300 / month to our living costs.
Then, I’ve had a few extra costs this month:
2 new writers to produce content for the
The new mobile Editor from WordPress.com looks pretty slick. Try it out!
Now that so many of us carry around tiny pocket-size computers, more and more of our Internet time happens on phones and tablets — not just browsing, but creating. You’ve been asking for a better publishing experience in the WordPress app to make mobile publishing smoother. Today we’re introducing a new editor for iOS and Android, codenamed “Aztec.” It’s speedy and reliable, works with posts and pages, and is ready for beta testing! What’s New?
At first glance, the Aztec editor might look like the old editor — which means you already know how to use it, with no learning curve.
What’s different, exactly? A lot:
The overall user experience is smoother and snappier, with improved scrolling and faster image insertion.
Spellcheck now works reliably.
The addition of Undo and Redo tools means you can easily fix mistakes or move between different versions of your text when writing (and re-writing!).
Dictation! Now, you can draft your thoughts without typing.
Full support for accessibility technologies like iOS’ VoiceOver and Android’s TalkBack.
It’s not just better for people on phones: Tablet users will feel more at home,
4.8.1 is adding a "Custom HTML" widget to address the issues that sites were having with custom HTML markup in the updated "Text" widget when they updated to WordPress 4.8. There's also a few notices that will guide users on which widget to use.
Justin Sainton shares his thoughts on the shifting WP economy and what it means for businesses moving forward.
Not too long ago, Post Status’ newsletter covering Rainmaker’s move from a SaaS product model to a service-only model served as the catalyst for a lot of conversation on Twitter. We saw the esteemed Brad Williams tweet this thought about the WordPress economy: Definitely seeing a slow-down in the WordPress economy this year, but not many people want to publicly admit it. From @post_status… pic.twitter.com/DdmDTWhLc8
And it sparked a conversation in the Zao Slack about the WordPress economy and how this impacts us, too.
Zao has been around for over a decade, and we’ve seen the WordPress economy grow and expand during that time. We’ve watched many amazing businesses pop up, incredible developers thrive, and observed the expansion of open-source software’s role in business and tech overall. So far, it has been a wild ride.
In some ways, the WordPress economy has slowed down, especially in the product space, and likely in the service space as well. More than anything, though, I believe this to be a correction, rather than a real dip in the WP economy.
WordPress has been booming for the last eight to ten years, with the last five being especially lucrative
Nice to see a company take over for a developer who is unable to manage the load. Best of luck to them all.
Tailor Page Builder Under New Management Tailor was launched by Andrew Worsfold in April 2016. Since then a lot of work has gone into it, resulting in many updates and new features. Currently Tailor has three extensions (all free) which each add further functionality and features. It has been acknowledged by some key players in the WordPress community and have received a lot of positive feedback overall.
Tailor needs more time and efforts!
Until now Andrew has been doing all of the work on Tailor, but moving forward Tailor needs more time, money and a bigger team to manage it. As a result of other commitments, Andrew has not been able to maintain the rapid pace of development that he desires (and the plugin demands), which is why the team at Enclavely has taken over. They will be dedicated to delivering bug fixes and new features, ensuring that Tailor has a bright future.
Who is the new management?
Tailor has been acquired by Enclavely, inc. Enclavely is a startup founded by two experienced and skilled friends Munir Kamal and Essa Mamdani. Both were early adopters of Tailor and have been supporting Tailor since the beginning. They’ve got the necessary skills and experience needed
Brief overviews and reviews on the best wiki themes and plugins, free & paid. Includes over 15 options.
eCommerce integration has been growing in popularity steadily over the course of the past few years. More and more businesses are now selling online, whether or not their core business is eComm. Big enterprises, smaller businesses and even home-based entrepreneurs are making use of WooCommerce to create eCommerce stores and sell online within minutes. So here’s our ultimate WooCommerce Guide to keep in your back pocket. Considering the fact that WordPress is the world’s most popular Content Management System, it is a logical and often obvious choice to use WP for setting up eCommerce stores. As a result, eCommerce solutions that work within the WordPress environment are really helpful. WooCommerce is one such solution that offers both simplicity and great customization.
In this article, we will be discussing WooCommerce, what it is, how it can be of use to you, and things you should bear in mind to help you get the most out of WooCommerce.
Or, skip past The Overview to 7 Articles to Support Your WooCommerce Efforts in your one-stop-shop page to access all of the valuable information we’ve published on WooCommerce to the Pagely blog and website.
WooCommerce: The Overview
3 questions to make your Support inquiries crystal clear and easier to answer by Zach Skaggs, "Director of Happiness" at Ninja Forms
What's your impression of theme authors who force you to activate your theme before allowing you to fully install it or get the demo content for it? Please, share your experience with this trend that I discuss in my brief article here.
Recently I noticed that a lot of theme authors would force you to activate your theme before being able to properly install it or even install the demo content that comes with the theme, and here is an example of that I saw recently from the Impreza theme Would love to hear your feedback on this and where you think this is going to be a standard practice in the near future.
Please, comment below and share your opinion with this step.
ManageWP's Safe Updates feature just added the ability to automatically roll back an unsuccessful WordPress core/plugin/theme update.
Since we released the Safe Updates feature we have gotten a lot of positive feedback from you all. Making updates safer is something that we have been prioritizing recently, and right now we are back with an additional perk; the rollback option. In a nutshell, if we detect any type of issue during the update, you are now able to enjoy a fully automatic rollback to its original state. Safe Updates ensures your update of WordPress core, plugins and themes is safer than ever. Let’s quickly recap how Safe Updates are performed.
It’s a 7 step process:
Step one – creating a restore point for your website
Step two is sending HTTP requests to the website before the actual update to make sure everything is working smoothly on your website
Step three – creates a before screenshots of your website
Step four is running the updates
Step five we send a HTTP request again to check your website response after the update
Step six we take an after update screenshot of your website
Step seven is your option to go in and see the screenshot comparison
What’s the rollback option?
The rollback option is an automatic restore in case something goes wrong during the update. The
Dumitru Brînzan shares his experience with releasing free WordPress themes on WordPress.org while dealing with theme name collisions and other issues.
This post is about the Team Review Team (TRT) at WordPress.org, which I am (still) a small part of. I would like to address some weird things that have been going on lately in this team and what it looks like from a distance. I might be burning some bridges with this post, but if someone needs to take “one for the team”, so be it.
The Basics of WordPress.org Theme Repository
With 4,860 of free themes (at the time of writing this), the official WordPress.org Theme Repository (short: “repository”) is the first thing that any WordPress adopter sees and is probably one of the main reasons why WordPress grew to what it is today.
You can sort the themes in the repository by 3 main filters: Featured, Popular, Latest.
Latest is pretty straightforward: the newest themes are at the top, the oldest themes are at the bottom. I believe that this page is not very useful to end-users, as a theme’s usefulness doesn’t depend on how new it is, 1 week old or 3 months old.
Featured is the starting page for the Themes Repository, this is what users see first.
Contrary to popular belief the themes are not screened or moderated in any way.
DDoS attacks are getting more frequent, but what should you do when your WordPress site is under attack?
In our last case study, we showed you how we cleaned up a negative SEO attack on Kinsta. Today we are going to show you some steps and troubleshooting we took to stop a DDoS attack on a small WordPress e-commerce site. DDoS attacks can come out of nowhere and smaller sites are usually even more vulnerable, as they aren’t prepared to deal with it when it happens. Let us ask you this question. If your site was attacked tomorrow, what would you do? If you don’t have any ideas, then perhaps you should bookmark and read this article. What is a DDoS Attack?
DDoS is short for distributed denial of service. The primary purpose of a DDoS attack is to simply overwhelm your web server and either cripple it or take it down. One of the frustrating things with these types of attack is generally the attacker doesn’t gain anything and typically nothing is hacked. The big problem with DDoS attacks is with the overwhelming load associated with it. Most likely you will also see your bandwidth spike to an incredible amount, and this could cost you hundreds or even thousands of dollars. If you are on a cheaper or shared host, this can easily result in a suspension of your account.