Torque, a news site dedicated to WordPress professionals, has launched 2016 Plugin Madness: 64 of the most popular WordPress plugins from the official directory will compete for the champion title.
10up’s Simple Page Ordering, built by none other than our Founder, has been recognized as one of the most in-demand plugins, and selected as a top contender. Simple Page Ordering simplifies ordering of pages (and other post types) by adding drag and drop positioning to the backend page list. Torque has randomly assigned its selected plugins to brackets across four regions: Pressers (which includes our plugin), Wordees, Extenders and Installers. In NCAA March Madness bracket style, plugins will be narrowed down through rounds of voting, beginning with 64 entrants. Voting happens every week over at pluginmadness.com.
WooCommerce is the world’s most popular e-commerce software, available as a free WordPress plugin. Its expansive extensions library houses a number of premium extensions addressing recurring payments, different payment gateways, shipment tracking tools, and more.
Scaling open source e-commerce solutions like WooCommerce, that can be installed on infrastructures of all shapes and sizes, is challenging. Online stores typically require intensive database transactions: complex queries on both the front and back-end that filter and sort products based on several categories, stock, and properties like pricing and reviews.
Further, most shoppers depend on site search to find products. Complex filters combined with keyword search across fields heavily tax relational databases like MySQL, the underlying database used by WordPress. And of course, increased store traffic increases the number of database queries to process, making every transaction even slower. Not surprisingly, many WooCommerce sites run quite slowly.
Our origin story is modest: just five years ago, 10up began with a single individual working in the smallest U.S. state and a portfolio containing fewer clients than there were Star Wars movies at the time.
Since then, 10up has matured at a much faster pace than your average agency. We’ve continued to grow our team by ~30%, welcoming dozens of new 10uppers across Project Management, Web Strategy, Engineering, Design, Revenue, and User Experience. Financials also continue to thrive; in the first month of 2016, we saw more revenue than our first two years combined (and more than half of what we did in our third year).
But here at 10up, we value more than revenue and growth statistics—it’s about nurturing the culture within, providing our team the resources to achieve peak performance—a sense of community, a pride of ownership, and material benefits for a team that is building a future together, not merely cashing in a paycheck.
In 2015, we hosted our biggest All Hands Summit, practically taking over a hotel in Boulder for a 10up-only conference with sessions exploring our business goals, emerging and important technologies, and the latest tactics for effective project management, with a healthy dose of team building. We even hosted an awards ceremony: The First Annual Uppies – a tradition is born.
As we continue to strive for the very best consulting experience in the publishing and content management space, here are just a few accomplishments since our last birthday:
We now spend more time on mobile gadgets than on desktop devices. The mobile web experience is more important than ever, and overwhelmingly defined by content relevancy, timeliness, and above all, speediness.
Mindful web developers—given adequate budget allowances—strive to build mobile-first sites that provide lean, engaging experiences across different screen sizes and devices. These sites better retain their audience because the experience is enjoyable and, in some cases, because impatient readers will leave (“bounce”) rather than wait for a clunky web page. Because Google recognizes its customers’ preference for performant sites, it factors pagespeed into its search algorithm, boosting speedy sites in search results.
In spite of these incentives to minimize page weight, most websites are heavier than ever. High resolution displays ushered in huge images, and universal support for custom typography has us downloading fonts everywhere. While the renaissance in front end toolkits like jQuery and React.js eases development and alleviates server-side scaling, it has done so at the expense of pushing more assets and processor strain to the browser. Most problematically, today’s website monetization and measurement tools often deliver heavy (and invasive) ads with little incentive to improve.
Much of this “bloat” has been obfuscated by our increasingly powerful devices, improving mobile broadband connections (especially among the “creative” class), and increasingly competitive browser technology. Even so, publishers are clearly testing (or even lazily trampling) acceptable boundaries, creating an opening for ethically gray solutions like iOS 9’s content blockers, and more closed platforms like Apple News.
Enter the Accelerated Mobile Pages (AMP) project: an open source initiative based on existing open web standards led by Google, touting noble intentions to improve the mobile web experience by providing standardized, lightweight guidelines and tools for developers. AMP HTML versions of web pages trade complex functionality and capabilities for lightness, simplicity, and a focus on content, resulting in near instant load times.
While there may be more transformative long-term potential for AMP as a framework, in the near-term, Google’s initiative is hyper-focused on improving news and media consumption. In essence, AMP competes with the self-contained, largely closed, and far more restrictive experiences offered by Apple News, Facebook Instant Articles, and the rumored “long-form format” coming to Twitter (among others). Publishers opting to offer AMP’s lean presentation will be rewarded with increased visibility in mobile search results for news, including Google’s News Carousel: the highly coveted positioning at the top of mobile search results.
Each year people around the world make New Year’s resolutions to lose weight, exercise, and to get organized. The same resolutions that can make you a better person can also be applied to your website. Here are some 2016 resolutions for your website.
It’s an exciting time in the WordPress community, with the release of Calypso, a successful inaugural WordCamp US, and WordPress now powering 25% of all websites. Maturation of the WordPress REST API is enabling the decoupling of the content management layer from the display layer, which has the potential to further drive adoption; larger teams can write independent code that communicates via the API, reducing blockers and accelerating feature releases. At the same time, the entire Web is poised to undergo a metamorphosis, as HTTP/2 begins to fundamentally change how content is delivered.
While these developments offer tremendous potential for those of us who work with WordPress for a living, I think there are some important considerations to keep in mind as WordPress and the Web move into a new era of maturity and possibility.
Using a CDN with DDoS protection is increasingly important
We recently started testing a CDN service that offers DDoS protection and mitigation for this site. While we hardly consider ourselves a high-profile target, the number of attacks reported by service is astonishing (more than a dozen every day, sometimes double or triple that). The majority are attempts to exploit known vulnerabilities in WordPress plugins (or other common web applications), such as those listed in the WP Vulnerability Database. Exploit mitigation (or at least, notification) at the CDN layer provider is compelling.
In addition to protection from known vulnerabilities, CDNs are vital to accommodating significant burst traffic, and eliminate the effort involved in hosting sites in multiple datacenter across the world. Instead of scaling your servers to manage exponential traffic as a story goes viral or an online catalog gets slammed on Cyber Monday, the work is offloaded to the CDN and its network of edge servers.
Of course, a CDN might not speed up your site–in fact, it can do just the opposite if you start serving up your site over HTTP/2 and you’re using “best practices” for optimizing your site for HTTP1.1.
The web publishing experience is at the heart of 10up’s mission. So needless to say, when Observer (a long-time client) offered the opportunity to reimagine their editorial process, merging content management across their digital property and hallmark print publication, New York Observer, they couldn’t hold us back.
The existing process was relatively simple, but introduced several pain points and some potential for inaccuracy. Content was first authored in a word processor; it then moved through several teams and systems: from fact checkers to InDesign and InCopy, then to print, and finally to WordPress for publication on Observer.com. All of this was tracked in a spreadsheet, which involved manually copying and pasting between the word processor, spreadsheet, and WordPress. For a publisher doggedly moving to a “digital first” business model, their process hadn’t exactly caught up with their vision.
The 10up/Observer team came up with a better approach: let’s flip that process on its head and drive the entire process from within WordPress, taking advantage of its content authorship and storage capabilities! In doing so, the burden of duplicating content is removed, and content can be published online much more quickly, without waiting for print publication.
The result? Eight Day Week–a web to print plugin that helps digital content creators use WordPress to streamline their print production workflow.
A few weeks ago, we pushed out our newest open source project: Flexibility, a polyfill that back ports Flexbox support to Internet Explorer versions 8 and 9.
Flexbox is one of the most significant advances in front end website layout since the advent of CSS, empowering us to build beautifully responsive and flexible layouts using pure, clean CSS. Here’s a short explanation from a great overview prepared by CSS-Tricks:
The main idea behind the flex layout is to give the container the ability to alter its items’ width/height (and order) to best fill the available space (mostly to accommodate to all kind of display devices and screen sizes). A flex container expands items to fill available free space, or shrinks them to prevent overflow.
Unfortunately, Flexbox support wasn’t added to Internet Explorer until version 10, leaving older versions – still popular in some corners – out of the Flexbox revolution. This idea didn’t sit well with 10up’er Jonathan Neal, tasked with engineering a beautiful layout for a Fortune 50 forced to contend with supporting older versions. We decided to subsidize his time to see if we could introduce Flexbox support under less-than-ideal browser requirements. The result was Flexibility: a smooth front end experience for older browsers, without compromising our ability to use pioneering layout technology.
With 2015 coming to a close, I’ve been reflecting on the ElasticPress project’s accomplishments since its inception one and a half years ago.
Today, we released ElasticPress 1.7, which completely restructures post meta storage. This enables performant post meta queries with complex comparisons against data types, such as integers, dates, and times. We also fixed some bugs.
Like many of our popular open source projects, ElasticPress was originally conceived as an internal tool designed to support some specific client needs. Since open sourcing the project, ElasticPress has garnered over 30 contributors (most of whom do not work at 10up), 16 major releases, and a thriving Github community where developers and site owners are collaborating. ElasticPress is used by major hosting companies and across hundreds of websites, some of which serve millions of pages each month. I have introduced developers to ElasticPress at speaking engagements around the world.
I find myself often telling designers and front-end engineers that “buttons should feel like buttons and links should look like links.” It occurs to me, that after a few years of the flat design trend, I should explain what that means.
Buttons should feel like buttons
When you press a physical button in the real world — any key on a physical keyboard, for example — you can tactically feel it depressing. You’ll also see its form shrink away from you and the way the light falls on it will cause it to look slightly different. Read More on Button and link usability
Jaimee Ratliff
Taylor Lovett
Jake Goldman
Taylor Dewey
Vasken Hauri
While these developments offer tremendous potential for those of us who work with WordPress for a living, I think there are some important considerations to keep in mind as WordPress and the Web move into a new era of maturity and possibility.
Josh Levinson
