Over the years, it’s been fascinating to see how teams can and do make use of CodePen. When I say teams, it’s really either or both of these things:

  1. A formal or informal group of front-end developer/designers that all use CodePen
  2. A group like that with an actual CodePen PRO Team account.

Here are some things we’ve seen.

Teams can prototype things together, then show them to clients

When any Pen or Project (or Post! Or Collection!) is team-owned, every member of the team has access to it while they are logged in and in the Team context. That means you can start a component and Ashana can finish it later. Ashana can tweak Paul’s Project and Jeremy can add Pens to a Collection that Rebekah started two weeks ago.

Speaking of Collections, one major use-case for them is to gather Pens to show a client, so they have one URL for viewing all the relevant work.

They do “CodePen Wednesdays”

Ever heard of a brown bag? Not like, literally a brown bag. But a “brown bag” is a term at companies when people stay in the office for lunch (as in they brought a brown bag of food for lunch, like a lot of us did in grade school) and use that time to learn about something.

For example, front-end developers at your company could get together and kick around ideas for a feature. They could play around with the possibilities of CSS custom properties. They could do the current challenge. They could all take a crack at building the same bit of UI and then compare notes on how everyone did it.

They make mini design systems

Though you can’t run fancy design system software like Fractal, Pattern Lab, or Storybook on CodePen (just yet), the initial prototyping of components is one of the major use cases for CodePen.

Having a team-accessible easily searchable and browseable place for all the component prototypes you’ve ever placed with is extremely useful for a lot of teams.

They demonstrate what an in-place design system is capable of

Another way we’ve seen CodePen be used in the context of a design system is as a place to quickly demonstrate what an in-place design system is capable of by adding the design system resources and building with them.

For example, a lot of design systems are, ultimately, a CSS file. And possible a JS file on top of that. It’s easy to link up external resources on CodePen, either by uploading them or linking to them elsewhere on the web.

Once that’s in place, you can write the relevant HTML in the HTML editor and watch the patterns come to life. Here I’ll link up Bulma and pretend like that’s my design system CSS, and then just drop some HTML into place and it’ll be styled:

They Bring Pens to their own Internal Documentation

If you’ve built a Pen that demonstrates something useful that your team should see, it’s great that it’s on CodePen ready for anyone else on the team to find and use, but your team might have it’s own documentation for things like this. Maybe you have an internal wiki. Maybe you have a private subdomain of your site where you keep your pattern library and examples. Maybe you use a tool like Notion to keep your coding guidelines straight!

They host little websites

With CodePen Projects, you can go so far as to point your DNS (A records) at CodePen and have your project be a real website at a domain you own. Little sites like CSSSans Pro and Vend, Oregon are powered that way, and require nothing more to update them than to log in, make changes, and click a few buttons.

They live their own lives

You know what some CodePen Teams do together? Nothing. Or, at least not specifically with their shared Team account on CodePen. One of the most important aspects of teams is that it’s essentially just shared billing for PRO accounts. Everybody on a Team is PRO, even when they are using CodePen in their personal context instead of Teams. So some Teams exist just to give all their people CodePen PRO, which has a whole slew of useful features on its own.

They use private items… a ton

If there is one thing we’ve found out through seeing and talking Teams work on CodePen, it is that they use privacy a lot. Their work is for them, not for the world, so they keep everything private. Good thing you can make an unlimited number of private things on CodePen, eh?