CodePen Radio

Stephen and Chris jump on the podcast to talk about our (ahem, super cool) deployment feature.

Any Pen can be a website!

Well, they kinda are already, but you know what I mean.

If you're a PRO user all you do is click a button and the Pen is instantly deployed at a *.codepen.app website. From there, it's pretty trivial to update a domain you own's DNS records to point to it, if you want to. Subdomains are a good choice, partially because they are free.

Why is CodePen a good place to host? We take care of the asset decaching, everything is CDN-backed and super fast, deployment is instant, it's DDoS proof, and it's just included in your PRO plan without silly complicated limits.

Marie and Chris talk about CodePen Challenges. We've been at it for many years! We get into the technology behind it, how we build our own CMS for it that powers the website and the emails that get sent about it. We also cover why they can be so beneficial for everyone involved.

Rach and Chris jump on the podcast to talk about the brand-new in-app notification system we built and shipped. We're actively trying to balance a system that isn't annoying, but allows us to show targetting information to targetted users when we think that's valuable for both you and us. It started with "We launched 2.0!" and is useful for stuff like short downtime notifications, reminders about PRO features, and all sorts of other things.

The system is designed to be as flexible as it possibly can be, meaning no particular UI is enforced, and can be used on any page anywhere in the DOM, and can have any set of logic applied. The "system" part just comes in with the fact that we track when they are seen so we can not annoy you with too many.

Stephen just implemented a great UI feature for the 2.0 editor where all the Panels that were previously stuck to the left side of the page can now be dragged away to become an "Editor Tab" just like a file (or Block!). Now you've got a lot more freedom for what you're looking at, and of course, the editor will remember your layout should you refresh or even come back in another browser.

Chris has Jacob Miller on the show, who is building a tool called DiffUI. The big idea is that it uses a diffusion model to do prompt-to-website design rather than an LLM, because image-based models are more interesting and creative. So stay there for a while, producing really detailed visual mockups and plans, then head to the LLM.

Stephen and Chris hop on to talk about the couple of weeks post 2.0 launch. Things are certainly different in 2.0! Literally the location of certain buttons is in a new place, and that requires folks to poke around a bit and figure it out. Some people just do that and it's a non-issue. Some write in for help and even find delight in the new features. Some lash out.

The cheese metaphor is from an old book by Spencer Johnson about people experiencing change in the workplace and learning to deal with it. You might call it a bit heavy handed, and the metaphor was plucked away by UX folks to describe interface changes, so consider this the end of the line for this already-stretched metaphor. That didn't stop us from using the icon in our documentation about this though.

With the recent launch of Custom Agents, Notion became the collaborative AI workspace where teams and agents work side by side. And now, their new Developer Platform is turning that workspace into infrastructure developers can build on.

Just one week off our big 2.0 launch, Shaw and Chris hop on to talk about how email is actually a big part of the launch. Social media ain't what it used to be, and not everybody is on your app every single day waiting for a notification.

With the recent launch of Custom Agents, Notion became the collaborative AI workspace where teams and agents work side by side. And now, their new Developer Platform is turning that workspace into infrastructure developers can build on.

The whole team is here! That's a first for us. Today we're launching 2.0, so we're having a little fun in this episode picking out our favorite features.

Plus a bonus appearance here of Marie's victory graphic.

Marie and Chris hop on CodePen Radio for a little chat on how we're still happily using WordPress for a variety of things here on CodePen. We've got it hosted on a subdomain and on a different (WordPress-specific) hosting plan than our main monorepo, so it has its own deployment process and such. We use WordPress for our blog, where this very podcast is published, because WordPress handles RSS well, and a podcast is an RSS feed with an audio file. We also, quite importantly, use it for our docs. For 2.0, we re-wrote the docs and used a Custom Post Type in WordPress to organize them, which feels much more organized.

When we set out to build the 2.0 editor, another editor in the CodePen cannon, the goal was actually to reduce the number of editors we have and support. Ideally, reduce it to one. The trick is that anything an existing Pen or Project can do, this new editor needs to be able to do as well. All while making sure it's forever future extensible. That was the wild engineering task in front of us, and we're happy to report it's done.

To be clear, at the time of publishing: all Projects have been converted to 2.0 Pens, so Projects doesn't even exist anymore. Someday we'll convert Pens too, but not particularly soon. Instead, you can choose to convert Classic Pens (with a button click under the Save menu) if you want to.

With the recent launch of Custom Agents, Notion became the collaborative AI workspace where teams and agents work side by side. And now, their new Developer Platform is turning that workspace into infrastructure developers can build on.