When planning the Jetli.com site, the developers of the project came across the DustPress framework and even though DustPress was fairly new and not that documented, it was selected as the basis for the site development. In this blog post they describe how they used DustPress to get the site up and running.
We spoke with Vivek Mangiani from VipeLabs.
How did you come across DustPress?
– We had built something similar last year. However, this time we wanted to build something more maintainable and more “enterprise-y”. That’s how I stumbled on DustPress, it’s an interesting approach to theme development and we’re loving it so far.
What was it like to develop with DustPress?
– Due to the lack of documentation early on, we had to improvise along the way. We may not be doing certain things correctly as per the latest version, but are aware of how we’ve worked around problems and the implications. Along with DustPress we are also using ACF for easy metaboxes & postmeta setup and Visual Composer for content setup.
The people at VipeLabs were among the early adopters of DustPress. Even though they got on board early they were able to complete this large project with a completely new way of doing WordPress.
– Due to the lack of helpers (early on, I’ve noticed there are newer ones now), we had to create our own. When we first started working with DustPress, there was no image helper. This is what we wrote instead.
DustPress is designed to be extendable by utilizing the standards of object-oriented programming. The developers are able to define their own classes and extend the features of DustPress and this is exactly what VipeLabs has done with their own set of elpers, for example the image helper shown above and their Google Ads helper seen in the image below and several others.
DustPress can also be used without its autoloading features. You can either disable the autoloading and do the rendering yourself, or use DustPress renderer anywhere you like.
– One of the things I absolutely love about DustPress is the ability for me to use the renderer outside of page templates. We have our own Emailer class with some statics to help us shoot emails out in our logic (we may introduce a queueing feature later on).
– We also did make use of DustPress.js mainly for subscription logic and popups.
– It’s pure code examples, but we hope it shows how DustPress is be used to build a service and make developing WordPress themes more manageable.