-
Notifications
You must be signed in to change notification settings - Fork 1
Teams
We have several development teams that all handle specific parts of the website. Each has a different schedule and release cadence.
That's us! Our team plays a couple of different roles inside the company in regards to development, and they're equally important. First, we enhance stories and sections directly in CUE using CSS and JavaScript stored in The Bucket. Our techniques are vast and spread over a decade of successes and failures, but all of that is for another wiki. The second thing we do is maintain the design system. We work with all departments and development teams to build a system that works for everyone and is easy to use. The design system was created several years ago as a replacement for Bootstrap, and was intended to feel like it as well. In addition to the NPM package that allows development teams to use it in their own codebases, we maintain a style guide that stakeholders can view for approval and developers can use to understand the recommended DOM.
The front end team maintains WPS and the templating logic. We work with them frequently when building new ideas to ensure the concepts are scalable and easy to make. This team, more than any other, relies on the semantic versioning of the design system in their workflow. Occasionally, we will get requests from them to make a change that helps one of their developers with a ticket. In this case, we will cut a new release with the change that developer can install locally. Naturally, this is the team updates versions of the design system for us by incorporating it a new release build. This team is mostly remote and the project manager is Joe Vitale.
The performance team maintains Yozons and handles almost all of the dynamic and client-side aspects of the websites at scale. They also maintain the analytics connections for our products. To put more plainly, if you want your code to know what market it's in, if a person is logged in, or track an interaction, you'll need to ping this team. This team is mostly in-house and the project manager is Nena Whittaker.
Next is a complimentary team in the News department focusing on experimental concepts. We work with them to scale their ideas into the core codebase. They are all in-house and the program manager is Kat Sheplavy.
There are a few more teams that we don't work with directly on a regular basis, but it's good to know what they do.
This team handles the server logic in CUE, maintains our APIs and works with partners to incorporate external content in our system. The project manager is Joe Vitale.
This team handles payments, the pay flow, paywalls, registrations and all things subscription-related. The project manager is Amanda Hamilton.
This team maintains the servers themselves and network routing. The project manager is Joe Vitale.