By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.
Barrel's Director of Strategy and Design Director hosted a live optimization session deep diving a brand who submitted their site for review, including a roadmap of fixes to implement before BFCM.
On Sunday, October 22nd, 2017, Barrel’s Director of Technology Wes Turner gave a talk on “headless” WordPress at WordCamp NYC, an annual gathering of leading experts in New York’s WordPress community. The two-day event took place at Convene in Midtown Manhattan, and Barrel was proud to support it as a sponsor.
Wes leads Barrel’s development team, which builds custom web experiences for our clients. He brings more than ten years of experience with web applications, especially content management and ecommerce systems, along with a deep understanding of WordPress and what it can do.
What “Headless” Really Means
His talk, “Headless” WordPress and What It Really Means, set out to clarify a term that was generating a lot of buzz in the developer community. In a headless setup, WordPress is used solely as a CMS. Its theme and templating features are replaced by a separate frontend framework, such as React, that pulls content from WordPress and displays it.
Wes walked through several benefits of taking a headless approach before turning to the “gotchas” teams should understand before committing to one. Drawing on past experience across Barrel projects, he pointed to infrastructure complexity and higher costs as key drawbacks. Plugins can also behave differently once the frontend is separated from WordPress, and user accounts can introduce their own challenges. He added that ongoing maintenance costs for a headless website could be higher than for a standard WordPress site.
Choosing the Right Approach
Barrel architects and builds more than a dozen WordPress websites a year for clients, ranging from microsites to enterprise-level, multinational builds. Headless isn’t automatically the better choice. Based on each client’s goals and needs, we may take a headless or a standard approach to development, and we’re upfront about the trade-offs so clients can make the right call for their business.