ProcessWire
Why ProcessWire?
ProcessWire exists to bridge the gap between the current content management landscape and the needs of many designers, developers and clients in a CMS. In addition to being a content management tool for the end-user/client, the CMS should be a tool for the designer/developer that actually makes it simpler to create their vision, rather than something that they have to adapt their vision to. It should enhance and empower the designer/developer's processes rather than dictating them.
After considerable exploration and experimentation, we chose ProcessWire as the underlying content management system for the Saving Birds Thru Habitat website.
ProcessWire is an open-source content management system built around a relatively simple and flexible philosophy. Unlike many modern website platforms, it does not attempt to force every organization into a rigid predefined structure. Instead, it allows the structure of the site itself to emerge from the actual needs of the content and the organization maintaining it.
That flexibility became increasingly important as the website evolved. The site contains many different forms of material: essays, field notes, guest posts, news items, educational resources, native plant information, photography, infrastructure documentation, newsletters, and discussion systems. These materials do not all behave in the same way, and they should not necessarily be forced into identical templates simply for the convenience of the software.
“The structure should emerge from the work itself rather than forcing the work into a predefined system.”
ProcessWire allows fields, templates, relationships, navigation systems, and page structures to be developed gradually around the actual publishing needs of the organization. Instead of beginning with a generic theme and adapting the organization to fit the software, the software can be adapted to support the organization.
This approach aligned closely with the broader philosophy developing throughout the project. We wanted the website to remain understandable, durable, maintainable, and closely connected to the actual work being done rather than becoming dependent on layers of unnecessary abstraction.
Another important aspect of ProcessWire is that it remains comparatively transparent. The system is built primarily around PHP, HTML, CSS, and straightforward template logic rather than heavily abstracted frameworks or proprietary visual builders. This does not eliminate technical complexity entirely, but it helps keep the infrastructure visible and understandable.
That transparency matters. Organizations should be able to understand and maintain the systems they depend upon whenever possible. Technical infrastructure should not become a black box accessible only to outside specialists.
“We wanted a system we could still understand ten years from now.”
At the same time, ProcessWire supports the hybrid publishing model used throughout this website. Editors work within a modern content management environment during the editorial process, but the public-facing site is exported as static HTML files. This allows the organization to retain the flexibility of a dynamic CMS while preserving many of the advantages of the earlier web: simplicity, speed, durability, portability, security, and reduced infrastructure requirements.
Our interest in this approach was informed partly by earlier experience maintaining large websites manually. In the early 2000s, a website of roughly 1,200 pages was created and maintained entirely by hand in HTML. That experience created an appreciation both for the strengths of the early web and for the practical limitations of maintaining large sites manually.
Manual HTML publishing produced websites that were often lightweight, durable, understandable, and relatively independent of complex infrastructure. At the same time, maintaining consistency across large numbers of pages could become increasingly difficult. Navigation changes, layout revisions, and structural updates often required editing many individual files manually. As websites grew larger and collaborative publishing became more important, content management systems emerged to solve real organizational problems.
The approach used here attempts to combine the strengths of both worlds. ProcessWire provides the organizational and editorial capabilities needed to manage a complex modern website, while static export preserves many of the strengths of the earlier web.
“The goal was not to reject modern tools, but to use them carefully and selectively.”
The decision to use ProcessWire was therefore not simply a technical preference. It reflected a broader philosophy about stewardship, independence, clarity, sustainability, and long-term maintainability. The goal was to build a system that serves the organization rather than requiring the organization to reshape itself around the assumptions of the software industry.
What does the term “ProcessWire” mean?
Conceptually: wiring your processes together
ProcessWire is the “wire” that delivers the electricity to your “process”. The term “ProcessWire” refers to bringing everything together simply, easily and securely. Specifically, bringing together all the processes involved in building a website or application and wiring them all together to create something whole and complete.
ProcessWire enables you to make all these connections intelligently, efficiently and easily. It is the timeless tool that works with your existing processes (whatever they may be) and seamlessly wires them together into something much greater than the sum of its parts.
What is especially important is that ProcessWire does not assume all websites should behave the same way. Many modern CMS systems begin with the assumption that the software already knows what a website is supposed to be. ProcessWire instead begins with fields, templates, and relationships that can be adapted to the actual content model of the organization.
That distinction sounds technical at first, but it has very practical consequences. It means the organization is not forced into predefined publishing patterns simply because the software was designed around mass-market assumptions.
The ProcessWire philosophy reinforces one of our strongest themes: visibility of infrastructure. ProcessWire remains comparatively understandable because it still works in relatively direct ways through PHP templates, HTML, CSS, fields, and page structures rather than burying everything beneath multiple abstraction layers or visual-builder ecosystems.
That matters philosophically as well as technically. Systems people depend upon should remain at least somewhat comprehensible to the people maintaining them.