Archive for "Case study"
Words like innovation and digital transformation tend to be sprinkled liberally in discussions about digital publishing and online revenue models these days. But stories about publishers that have actually implemented new digital strategies resulting in positive revenue streams are not nearly as common. One of our clients, The Christian Science Monitor, however, has done just that, reinventing itself online to better resonate with its readers, and generating a critical new stream of subscriber revenue.
Giving association members the ability to submit insurance claims online saves time and money for the Alberta Gymnastics Federation. Here we'll take a look at the insurance claims submission web app we built in eZ Publish / eZ Platform.
In an effort to engage its audience, our client, FindaTopDoc, wanted to integrate a custom Q&A platform into its site. They chose Oracle + Bronto as the accompanying marketing automation tool. Here we outline how we integrated Bronto with eZ Platform to build a robust Q&A and newsletter system with the capacity to send customized e-mails to tens of thousands of users.
Infrastructure as Code: provisioning and configuration management with Vagrant, Terraform, and Ansible
Intended audience: technical managers, senior developers
Agile developers must constantly strike a balance between building solutions for a known existing case and building solutions that can scale to handle unknown future cases. On the one hand, Agile philosophy encourages us to build and iterate as necessary: Move Fast and Break Things. On the other, various programming best practices encourage us to build in an extensible and modular way from the start: Do One Thing and Do It Well. On smaller projects, these two goals can be achieved simultaneously; but on larger projects – especially given time and budget constraints – it is sometimes necessary to prioritize one over the other.
Project managers and full-stack developers face such choices almost immediately, during the initial development, staging, and deployment phases. For instance, a project may begin with a narrow scope and require only a single developer’s time. In this case, it often makes sense to forgo provisioning a dedicated development virtual machine (VM) or staging server, and instead, to use generic or shared environments. But as the scope of the project grows, for instance with caching or proxy layers, it often makes sense to implement better development, staging, and production parity.
Hi, we're Mugo Web - Nice to meet you!
We're a group of web experts who solve complex web problems.Learn more about us »
- Business solutions (58)
- Case study (24)
- eZ Publish add-ons (21)
- eZ Publish community (11)
- eZ Publish development tips (64)
- Productivity tools (10)
- Site performance (10)
- User experience (27)
- Web accessibility (14)
- Web solutions (56)
- Work at Mugo (10)
Yes - we can do that.
Many years of experience with complex websites allows us to offer total solutions.Learn more about what we can do »
We love our clients (and they love us too)
We've solved problems across North America and around the world.Learn more about what we've done »
We tweet too
Follow us on Twitter for the latest Mugo happenings