Presentation Framework

For all its success, the original version of the Presentation Framework had one major drawback: it had been written in a way that tightly coupled it to the javascript framework originally chosen by The Weather Company (an IBM business) for use on the site, Angular 1.

As mentioned in our first post, refactoring the Presentation Framework originally built for weather.com to be javascript framework agnostic and work with Angular 2 presented us with some interesting challenges. Today, I’ll talk about the second big problem we encountered when building out this system - how do we allow the exact same component to be placed on a page multiple times?

In choosing to adopt a framework without an official release, there were problems to be overcome as well. The biggest complication we encountered was that since the project is still in beta, much of the documentation is not fleshed out, and some of the specific architectural challenges we were trying to solve were not documented anywhere at all.

One of the requests of the Wunderground team in beginning this effort, was that instead of starting a new project using Angular 1, they wanted to push into new territory and use the not-yet-released Angular 2.

For this first entry, we will explore part of the custom built solution we call the “Presentation Framework”. TWC needs to allow a (non-technical) content team to rapidly modify content and layout of pages throughout the site. Given the numerous types and rapidly changing nature of the content widgets required, we wanted to involve TWC’s own talented team of developers as much as possible in the implementation of the logic driving them.

Subscribe to RSS - Presentation Framework