The rebranding of Eleventy to Build Awesome represents a fundamental shift in the static site generator landscape, raising critical questions about sustainability, community, and the commercialization of open-source tools that have flourished in their free, flexible form.
The static site generator ecosystem finds itself at a crossroads with the recent announcement that Eleventy will be rebranded as Build Awesome under Font Awesome. This transition, marked by a highly successful Kickstarter campaign that quickly reached its $40,000 goal, signals a significant departure from the project's origins as a flexible, community-driven open-source tool.
The Static Site Generator Landscape
Static websites predate the dynamic content management systems that now dominate the web. In the early days of the Internet, all websites were mere collections of static HTML files. The pendulum began swinging back toward static approaches with modern static-site generators, offering more security, simpler hosting, and superior performance.
The evolution of static site generators follows a clear timeline:
- Jekyll (2008), created by GitHub co-founder Tom Preston-Werner, repopularized SSGs with its integration into GitHub Pages
- Hugo (2013), written in Go, gained traction for its significantly faster build speed
- Gatsby (2015), a React-based SSG, introduced the "content mesh" and leveraged GraphQL
- Eleventy (2017), positioned as an "anti-framework" SSG, offering flexibility without imposing rigid structures
Eleventy's Philosophy and Appeal
Eleventy, created by Zach Leatherman, was designed to leverage the Node.js ecosystem while avoiding the imposition of a client-side JavaScript framework. Its core strengths lie in flexibility, JavaScript integration, and framework-agnostic design.
What made Eleventy distinctive was its support for multiple templating engines—Liquid, Nunjucks, Markdown, Handlebars, and EJS—allowing developers to mix and match according to their needs. While Eleventy could utilize the vast npm ecosystem for the build process, it deliberately avoided dictating client-side JavaScript architecture.
The framework gained impressive adoption, with users including NASA, CERN, the TC39 committee, W3C, Google, Microsoft, Mozilla, Apache, and freeCodeCamp. The A11y Project launched with Eleventy 1.0 and, as noted by its lead developer Eric Bailey, nearly three years later could still install and run from a cold start with no complications.
The Commercialization Challenge
By 2015, the term "Jamstack" (JavaScript, APIs, and Markup) was being codified, arguing that decoupling frontend from backend and pre-rendering static HTML at build time represented the correct architecture for the modern web. This framing opened commercial opportunities, but has proven difficult to monetize successfully.
Several attempts have been made to commercialize static site generators:
- Gatsby raised over $46 million in venture capital, attempting to monetize through "Gatsby Cloud" before being acquired by Netlify and ultimately sunset
- Stackbit aimed to be a "site builder" for various SSGs before pivoting and being acquired by Netlify, then sunset
- Companies like Netlify and Vercel built businesses around hosting and deployment services, treating SSGs as "loss leaders" to attract users to their paid platforms
These attempts reveal a fundamental tension: the model monetizes infrastructure rather than the SSG itself, leaving open-source projects dependent on the goodwill and strategic alignment of larger platforms.
Leatherman's Open Source Dilemma
Zach Leatherman, as the creator and BDFL lead maintainer of Eleventy, has been a vocal advocate for sustainable open-source development. In his podcast episode "How Eleventy Survived: Funding, Growth, and Open Source Reality", he spoke of the inherent struggle of maintaining a project that becomes widely adopted critical infrastructure with limited resources.
Leatherman joined Font Awesome because he believed the company shared his commitment to "boring" (reliable and stable) technology and sustainable development. His move, and the subsequent creation of Build Awesome, represents an attempt to solve the sustainability challenge through direct commercialization.
Build Awesome: A Familiar Pattern
Build Awesome aims to position itself as an accessible alternative to clunky full-stack CMSes, with pro features including:
- Collaborative visual editing (essentially a headless CMS)
- Build-in-a-browser (eliminating local development setup)
- Premium built-in templates and hosted import tools
This approach echoes previous attempts like Stackbit and NetlifyCMS, which have struggled to find success. The fundamental problem remains: the only people who genuinely care about creating static sites typically prefer using a free, local IDE and terminal rather than browser-based visual editors.

As one developer noted, "folks gotta eat, but pro tiers make me queasy." This sentiment captures the tension between sustainability and accessibility that plagues commercialization attempts in this space.
The Audience Disconnect
Build Awesome appears to target users of traditional CMS platforms like WordPress or Squarespace, who may find static generators intimidating. However, this misses the actual user base of tools like Eleventy, which includes developers, hobbyists, and organizations seeking autonomy, flexibility, and control over their digital presence.
The author's own project, Berry House, represents an alternative approach: creating static websites for nonprofits and marginalized communities on a pay-what-you-can or pro bono basis. This model addresses the accessibility concern without introducing subscription fees that alienate the core community.
Community Reaction
Reactions from the Eleventy community to the Build Awesome Kickstarter have been mixed, with many expressing concern about the future direction of the project:
"I only care about and use 11ty. Don't know anything about the awesome stuff but doesn't feel like I'm their target audience. I worry 11ty will get sucked up and cease to exist in a form I want to use." — Michael Harley
"Mixed feelings. I don't like change. It's a lame name. I know folks gotta eat, but pro tiers make me queasy." — Cobb
"Part of the reason I liked 11ty was the broad community using it and the homegrown feel. The change feels like the community will become centralized and gatekeep-y?" — nannnsss🌱🏴
These reactions reflect a common concern: the commercialization of a beloved open-source tool may fundamentally alter its character and accessibility.
The Legacy of Eleventy
Beyond technical considerations, Eleventy carries cultural significance through its mascot, Elle the possum, created by the late web developer James Williamson. Williamson, who passed away from ALS in 2019, was an influential instructor who contributed significantly to web accessibility and design education.
Elle represents more than just branding; she symbolizes the community and human connection that has made open-source projects like Eleventy thrive. As the author notes, "The tools and lessons he left behind outlasted him in ways no Kickstarter can manufacture."
Looking Forward
The transition from Eleventy to Build Awesome raises fundamental questions about the future of open-source tools in a commercial ecosystem. Can a project maintain its community-driven ethos while pursuing commercialization? Will the flexibility that made Eleventy appealing be preserved in a more structured product?
The history of static site generators suggests that attempts to monetize these tools have struggled, often failing to serve either the core community or the intended commercial audience. The challenge lies in finding a sustainable model that respects the values and needs of existing users while potentially expanding accessibility for others.
As this transition unfolds, the web development community will watch closely to see whether Build Awesome can succeed where others have failed, or whether it will become another cautionary tale in the ongoing tension between open-source ideals and commercial reality.

Comments
Please log in or register to join the discussion