Html codes
183 subscribers
111 photos
15 videos
226 files
197 links
👋 Welcome to Html Codee
🚀 Here you’ll find mini tools, code snippets, and web tricks to grow fast.
🧩 Built with HTML, PHP, and smart ideas.
💌 Support: support@bestpage.x10.mx
🏁 If you don't walk today, run tomorrow.
Download Telegram
CodePen Blog
Chris’ Corner: Little Bits of CSS

Adam Argyle is clear with some 2025 CSS advice:

I think every front-end developer should know how to enable page transitions, transition a <dialog, popover, and , animate light n’ dark gradient text, type safe their CSS system, and add springy easing to animation.

Nobody asked me, but if I had to pick a favorite of Adam’s six, it’s all the stuff about animating <dialog, popover, and . There is a lot of interesting new-ish CSS stuff in there that will help you all around, between allow-discrete, overlay, ::backdrop, :popover-open, @starting-style, and more. /* enable transitions, allow-discrete, define timing */
[popover], dialog, ::backdrop {
transition: display 1s allow-discrete, overlay 1s allow-discrete, opacity 1s;
opacity: 0;
}

/* ON STAGE */
:popover-open,
:popover-open::backdrop,
[open],
[open]::backdrop {
opacity: 1;
}

/* OFF STAGE */
/* starting-style for pre-positioning (enter stage from here) */
@starting-style {
:popover-open,
:popover-open::backdrop,
[open],
[open]::backdrop {
opacity: 0;
}
}

Jeremy Keith also did a little post with CSS snippets in it, including a bit he overlaps with Adam on, where you by default opt-in to View Transitions, even if that’s all you do. @media (prefers-reduced-motion: no-preference) {
@view-transition {
navigation: auto;
}
}

The idea is you get the cross-fade right way and then are set up to sprinkle in more cross-page animation when you’re ready. Una Kravets has a post about the very new @function stuff in CSS with a bunch of examples. I enjoyed this little snippet: /* Take up 1fr of space for the sidebar on screens smaller than 640px, and take up the --sidebar-width for larger screens. 20ch is the fallback. */
@function --layout-sidebar(--sidebar-width: 20ch) {
result: 1fr;

@media (width > 640px) {
result: var(--sidebar-width) auto;
}
}

.layout {
display: grid;
grid-template-columns: --layout-sidebar();
}

I’m intrigued by the idea of being able to abstract away the logic in CSS when we want to. Perhaps making it more reusable and making the more declarative parts of CSS easier to read.

Here’s another. I had absolutely no idea design control over the caret was coming to CSS (the thing in editable areas where you’re typing, that is usually a blinking vertical line). I guess I knew we had caret-color, which is prettttttty niche if you ask me. But now apparently we’re given control over the shape and literal animation of the caret. textarea {
color: white;
background: black;
caret-shape: block;
caret-animation: manual;
animation: caret-block 2s step-end infinite;
}

@keyframes caret-block {
0% { caret-color: #00d2ff; }
50% { caret-color: #ffa6b9; }
}

Jump over to the Igalia blog post to see the video on that one.

OK that’s all for this week. Er wait actually you gotta watch Julia Miocene’s Chicken video. Now I’m done.
1
CodePen Blog
410: Trying to help humans in an industry that is becoming increasingly non-human

Chris & Marie jump on the podcast to talk about just how drastically customer support has changed over the last few years. We still exclusively do customer support over email. Incoming email from real customers who need a hand with something where they type out that email in plain languages themselves are few and far between. Instead we get an onslaught of noise from users that don’t exist about Pens and situations that don’t exist. The influence of agentic AI is massive here, some of it with nefarious intent and some not. All of it needs work to mitigate.

Time Jumps
* 00:07 How much support has changed in the last 2 years
* 01:12 How do we do support at CodePen in 2025
* 07:41 How much noise AI has added to support
* 14:02 Verifying accounts before they’re allowed to use support or CodePen
* 23:05 Some of the changes we’ve made to help deal with AI
* 29:50 The benefits of learning to code with AI
Html codes
Photo
CodePen Blog
Chris’ Corner: Word Search

My daughter had a little phase of being into Word Searches. I found it to be a cool dad moment when I was like “I’ll make you a tool to make them!”. That’s what she was into. She liked doing them OK, but she really liked the idea of making them. So my tool starts with a blank grid where you can type in your words, then fill in the blanks with random letters, then print it.
https://blog.codepen.io/wp-content/uploads/2025/09/CleanShot-2025-09-23-at-11.06.40.gif
Perhaps unsurprisingly, this type of simple game with simple well-defined interactions is rife for front-end developer experimentation.

Interestingly, I’ve found most takes on HTML/CSS/JavaScript Word Searches to be more about the experience of solving them, which is just as interesting! Let’s look at some.

Christian Collosi’s Version on

Canvas is nice here as lines and arcs can be drawn at really specific coordinates to “circle” the words as you interact with it, and stay circled when you find a correct word.
https://blog.codepen.io/wp-content/uploads/2025/09/CleanShot-2025-09-24-at-08.30.40.gif
Mads Stoumann’s Pure CSS Version

You click on the letters individually, and if the ones you have clicked on match a word, it changes background to let you know you’ve got it. This all happens with s and simpler-than-you’d-think :has(:checked + :checked ...) selectors.
https://blog.codepen.io/wp-content/uploads/2025/09/Screenshot-2025-09-24-at-8.41.43-AM-1024x529.png
Kevin Newcombe’s Responsive word search

The responsive-ness of Kevin’s approach here is actually really cool. It doesn’t just scale, it literally changes the columns/rows of the puzzle itself. But I’m actually even more into the SVG-drawn lines where you make guesses and the SVG-drawn circles around the successful guesses. Some sort of similar work here.
https://blog.codepen.io/wp-content/uploads/2025/09/CleanShot-2025-09-24-at-11.48.33.gif
Kit Jenson’s Word Search in Color

Gotta love the aesthetics here! Just not a game you usually see a lot of color in, so nice to see some playing in that direction.
https://blog.codepen.io/wp-content/uploads/2025/09/CleanShot-2025-09-25-at-13.03.57.gif
Part of what makes me so damn proud of the CodePen community is that this is really the tip of the iceberg of experimentation in this very niche thing. Go around exploring for this sort of thing and you’ll find loads more.
This media is not supported in your browser
VIEW IN TELEGRAM
🎬 Sora 2: video AI gets a major upgrade

OpenAI has released Sora 2, its updated video generator.

What’s new:
• More realistic physics and object behavior
• Synced sound and dialogue
• Greater control over style and scene flow
• Ability to insert yourself or friends into videos with appearance + voice intact

Access will roll out gradually via invites (starting in the US & Canada). Free tier comes with “generous limits,” while Sora 2 Pro offers higher-quality generation under subscription.

AI Post 🪙 | Our X 🥇
CodePen Blog
411: The Power of Tree-Sitter

Alex and Chris hop on the show to talk about a bit of technology that Alex calls “The 2nd best technological choice he’s ever made.” That technology is called Tree-sitter. It’s a code parsing tool for building ASTs (Abstract Syntax Trees) out of code. GitHub uses it to power search and “go to” functionality. The creators now work on Zen, where a code parser is paramount. We use it to understand an entire Pen very quickly so we can understand how it all links together (among other things) and make a plan for how to process the Pen (a “build plan”). It’s fast, accurate, forgiving, and extensible. Just a heck of a learning curve.

Jump Links
* 00:07 CodePen 2.0 is more than just a fresh coat of paint
* 03:00 Treesitter explained
* 12:04 Making the right choices with technology
* 21:50 How we parse your code
* 26:10 We don’t want you to have to be in config hell
* 28:48 Type type type stop see what happens
CodePen Blog
Chris’ Corner: Discontent

Nothing is above a little healthy criticism.

Here’s Den Odell’s article We Keep Reinventing CSS, but Styling Was Never the Problem.

It’s easy to forget what CSS was originally designed for: documents. You’d write some HTML, style a few headings and paragraphs, maybe float an image to the left, and call it a day. In that world, global styles made sense. The cascade was helpful. Inheritance was elegant.

Fast-forward a couple of decades and we’re building highly interactive, component-based, state-driven, design-system-heavy applications, still with a language meant to style a résumé in the early 2000s.

CSS wasn’t built for encapsulated components. It wasn’t built for dynamic theming or runtime configuration or hydration mismatches. So we’ve spent years bolting on strategies to make it work.

If I can critique the critique, it makes some good and astute points, but pitting CSS evolution as the enemy up front doesn’t sit right. CSS itself, in my opinion, is doing great. It’s not the job of CSS to chase trends or bend toward fickle developer tooling trends. To be fair, Den also says it’s not really the fault of CSS, it’s a matter of choosing trade-offs with your eyes open, which I fully agree with.

Jono Alderson isn’t pleased, really, with modern web development entirely. I’ll quote some of his intro:

Most websites are awful.

Not just slow – awful. Bloated, fragile, over-engineered disasters. They load slowly, render erratically, and hide their content behind megabytes of JavaScript. They glitch on mobile. They frustrate users and confuse search engines. They’re impossible to maintain. And somehow, we’re calling this progress. […]

This isn’t evolution. It’s self-inflicted complexity. And we’ve normalised it – because somewhere along the way, we started building websites for developers, not for users.

Go look around at “modern” media-driven sites and you’ll see he’s not wrong. We all see it every day. It’s almost embarrassing these days to tell people you make websites, because everybody knows websites are pretty rough these days.

If I can, again, critique the critique, it’s that nobody (you, me, Jono) need to do this. The web isn’t forcing us to do this. The web is amazingly backward compatible. If you are nostalgic for some way of building websites gone by, well, just start doing it that way again, because it will still work. Jono does mention this, but misses naming the real enemy: the companies themselves that put up with this and hire specifically to enforce it. I can and do say you don’t need to build websites with the latest in JavaScript cargo-culting, but in order to get a decent paying job in web development, well, you just might have to. That’s the real shame here. Yes this is a problem, and we’re not going to fix it unless companies start writing checks to employees to remove cruft and remove complexity and give freedom to developers who care to improve the situation.

For a random little bonus… ain’t it a shame the lack of love for sin() and cos() in CSS? Most hated?! Jeepers.
New style icons and three legged crow
Html codes
Photo
CodePen Blog
412: 2.0 Embedded Pens

Or just “Embeds” as we more frequently refer to them as. Stephen and Chris talk about the fairly meaty project which was re-writing our Embeds for a CodePen 2.0 world. No longer can we assume Pens are just one HTML, CSS, and JavaScript “file”, so they needed a bit of a redesign, but doing as little as possible so that existing Embed Themes still work. This was plenty tricky as it was a re-write from Rails to Next.js, with everything needing to be Server-Side Rendered and as lightweight as possible (thank urql!).

Time Jumps
* 00:06 Welcome back to CodePen Land
* 00:35 What’s new about Pens in CodePen 2.0
* 05:20 Designing with custom themes in mind
* 10:40 What the editor looks like in the 2.0 Editor
* 16:09 Converting old Pens to new Pens
* 17:20 Debating using Apollo in embeds
From which network did the early form of the Internet evolve?
Anonymous Quiz
0%
Ethernet
17%
Internet
67%
ARPANET
17%
WI-FI
CodePen Blog
Chris’ Corner: Design (and you’re going to like it)

Damning opening words from Edwin Heathcote in Why designers abandoned their dreams of changing the world.

Every single thing on Earth not produced by nature had been designed. That was the spiel. Design wanted it all. Now Earth is a mess, its climate warming rapidly, its seas full of waste. There are microplastics in the glaciers, the air is polluted and forests are being destroyed to make more stuff. If everything is design, then design is responsible for all of it.

The situation is, if you wanna make money doing design work, you’re probably going to be making it from some company hurting the world, making both you and them complicit. Kinda dark. But maybe it is course correction for designers thinking they are the world’s salvation, a swing too far in the other direction.

This pairs very nicely with Pavel Samsonov’s UX so bad that it’s illegal, again opening with a banger:

Once upon a time, there was a consensus about the design process: we would do research to understand user needs, and then we would do design to satisfy those needs. That consensus, it seems, is gone.  From Cory Doctorow’s thesis on enshittification to Ed Zitron’s Rot Economy to the no-consent culture of AI, the trend is clear. “Users should be thankful for what they get,” say our corporate overlords. “Any problems are their own fault, and nothing to do with us.”

Big companies products are so dominant that users are simply going to use them no matter what. Young designers will be hired to make the products more profitable no matter what, and they will like it, damn it.

Using design to make money is, well, often kind of the point. And I personally take no issue with that. I do take issue with using design for intentional harm. I take issue with using the power of design to influence users to make decisions against their own better judgement.

It makes me think of the toy catalog that showed up at my house from Amazon recently. It’s early October. Christmas is 3 months away, but the message is clear: get your wallets ready. This design artifact, for children, chockablock with every toy under the sun, to set their desire ablaze, to ensure temper tantrums for until the temporary soothing that only a parent clicking a Buy Now button gives. It isn’t asking kids to thoughtfully pick out a toy they might want, it’s says give me them all, I want every last thing. The pages are nicely designed with great photography. A designer make the argument: let’s set all the pages on white with product cutouts and plenty of white space, so kids can easily visibly circle all the things they want. Let their fingers bleed with capitalism. Making a list isn’t just implied though, the first page is a thicker-weight paper that is a literal 15-item wish list page designed to be filled out and torn out. More. Morrrreeeee. And just as a little cherry on top, it’s a sticker book too. It begs to travel with you, becoming an accessory to the season.

It’s cocaine for children with the same mandates as the Instagram algorithm is for older kids and adults.
Html codes
Photo
CodePen Blog
413: Still indie after all these years

We’re over 13 years old as a company now. We decide that we’re not a startup anymore (we’re a “small business” with big dreams) but we are still indie. We’ve seen trends come and go. We just do what we do, knowing the tradeoffs, and plan to keep getting better as long as we can.

Links

* Timeline – Chris Coyier
* 115: Adam Argyle on Cracking the 2025 Web Dev Interview | Front-End Fire

Time Jumps
* 00:05 Are we still an indie startup?
* 04:32 Remote working at CodePen
* 19:20 Progressing and advancement in a small business
* 22:51 Career opportunities in tech
* 25:39 Startups starting at free
* 29:17 2.0 for the future
💻 Computer Hardware

Hardware is the physical parts of a computer — things you can see and touch.

⚙️ Main parts:

🧠 CPU – brain of the computer
💾 RAM – temporary memory
📂 HDD/SSD – permanent storage
🧩 Motherboard – connects all parts
🔌 Power Supply – gives electricity
⌨️🖱 Input devices – keyboard, mouse
🖥🔊 Output devices – monitor, speakers

🧠 Hardware + Software = Working Computer

#Informatics #ComputerBasics #Hardware #Tech