Did a quick firefox compatibility pass on my codepens, adding some polyfills and workarounds non (yet) supported features.

https://codepen.io/villepreux

#codepen #firefox #webdev #baseline

RE: https://front-end.social/@hejchristian/116719922552187722

There was some interest in the sticky notes I had in my screenshot earlier, so I've put the code that makes it up on #CodePen 💜

https://codepen.io/editor/HejChristian/pen/019ead35-f1cf-7353-b299-f88e5e408247

Also tried the @codepen 2.0 editor for this, it's lush 🤩

#CSS #Frontend

RE: https://front-end.social/@hejchristian/116697513534647811

Here's a lil #CodePen for it 💜

https://codepen.io/HejChristian/full/NPbBeqO

#CSS #Frontend

A #CodePen-style #live #IDE for #building, #testing, and #debugging Model Context Protocol (#MCP) #servers — #LLM #agnostic — https://github.com/AnandPilania/mcp-live-playground

#modelcontextprotocol #sandbox #webide #llmagnostic #llmops #aitools #apiinterface #ai #BuildInPublic #nodejs #javascript

Built a beach sandwich shack menu UI for this week’s CodePen Challenge 🪶🥪

The seagulls were not part of the original business plan.
Now they run the place.

#CodePen #CSS #Frontend https://codepen.io/grauconejo13/pen/KwNzOVR

Trying to figure out the CodePen 2.0 editor

Recently, CodePen introduced CodePen 2.0, and since then, I have been trying to figure out how to modify my workflow for this blog to use it. I have been using CodePen to host my code demos for over six years now, and it feels weird to change, but it seems like a positive development. Lately, I have been writing a lot of posts about how to use Vue.js with Web Awesome. Let’s start with something that we can use to demonstrate basic functionality with Vue.js, Web Awesome, and Font Awesome.

So, what’s going on here? In previous demos (like the one for More Web Awesome Dropdowns), there were three files for each pen (the markup, CSS, and JavaScript). For 2.0 pens, you can have many more (and it uses Vite). In the demo above, App.vue handles the application layout, Header.vue handles the header, and CounterButton.vue handles the button’s behavior. I have done A LOT of experimentation since the 2.0 editor dropped, and I can’t get a few things (like Vue Router) to work, but I am hoping that will come with time. Since I can add more files, I added the social meta tags and a manifest.json. It means that the result should be more shareable on its own. I also added a light-mode/dark-mode toggle, a link to view the files, and a link to the blog post.

I think that, moving forward, I will keep using the same header. I hope that you appreciate the result.

Example: https://strange-scene-malamute.codepen.app

I'm adding a collectable card system to my site 👀 Already got the card setup from a previous CodePen demo

https://codepen.io/HejChristian/pen/RNwXexO

Just needs a page (binder) to keep track of any folks might find (LocalStorage or IndexedDB for some persistence 🤔)

No battle system yet, maybe one day though ☺️

#CSS #CodePen