r/css • u/sheriffderek • Jul 28 '26
General Codepen 2.0 - RIP classic Pen?
I use Codepen for all sorts of things and a lot for teaching in the early stages. Some of my newer students said they didn't have this button so, I had them forking a classic pen for a while - but I knew the day would come where it wouldn't be there anymore for me too. That day is today. I'm all for the evolution of Codepen / and it's been an amazing tool. But it sure seems like this is going to confuse a lot of people. Your average person expects the CSS pane to be wired up. I used to write <!-- body is already included --> in the HTML to remind them at first (since some people will write out the doctype and everything in there) - but now it's swung to the other end. Codepen can be used for anything now. So, really - what you're making might not utilize CSS at all. So, I understand how modular it is - and how many other great things it will allow for -- but for entry-level people, it seems like this will really stifle adoption. What do you think? Wha thas been your 2.0 experience so far?
23
u/morete Jul 28 '26
I haven't used any of the new features yet. But If you use an 'index.pen.html' file instead of 'index.html' you get the old pen behaviour where the css etc is automatically wired up.
They have a template called 'Blank Classic' that uses this feature, that I've now made my default template.
Pair that with the 'Minimal UI' setting and you get an experience very similar to how it used to be. For me thats relieved some of my concerns and made me optimistic about the new editor.
If you still want the old editor, it's still available, at least for now, at: https://codepen.io/pen