<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Front-End on The Coders Blog</title><link>https://thecodersblog.com/tag/front-end/</link><description>Recent content in Front-End on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 16:59:48 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/front-end/index.xml" rel="self" type="application/rss+xml"/><item><title>Advanced CSS: Crafting Multi-Stroke Text Effects</title><link>https://thecodersblog.com/multi-stroke-text-effect-in-css-2026/</link><pubDate>Wed, 06 May 2026 16:59:48 +0000</pubDate><guid>https://thecodersblog.com/multi-stroke-text-effect-in-css-2026/</guid><description>&lt;p&gt;You’ve seen them. Eye-catching titles, unique logos, UI elements that just &lt;em&gt;pop&lt;/em&gt;. They all share a common trait: text that doesn&amp;rsquo;t just sit there, but commands attention with layered outlines. But how do you actually achieve those multi-stroke text effects in CSS, and more importantly, should you?&lt;/p&gt;
&lt;h2 id="the-problem-standard-text-is-boring"&gt;The Problem: Standard Text is Boring&lt;/h2&gt;
&lt;p&gt;The default browser rendering of text is, well, functional. But for designs that demand a visual edge, a single stroke or even no stroke at all simply won&amp;rsquo;t cut it. We’re talking about creating effects that look something like this, where an inner stroke contrasts with an outer one, or where multiple distinct outlines build up a complex graphic.&lt;/p&gt;</description></item><item><title>User-Centric Development: Why Your Website Isn't For You in 2026</title><link>https://thecodersblog.com/your-website-is-not-for-you-2026/</link><pubDate>Fri, 01 May 2026 16:25:57 +0000</pubDate><guid>https://thecodersblog.com/your-website-is-not-for-you-2026/</guid><description>&lt;p&gt;For too long, we&amp;rsquo;ve built websites that echo our own technical prowess and aesthetic preferences, not the nuanced needs of our users. In 2026, this self-indulgent approach isn&amp;rsquo;t just suboptimal; it&amp;rsquo;s a direct route to project failure and insurmountable technical debt. The era of building for internal convenience is over.&lt;/p&gt;
&lt;p&gt;The market has matured, user expectations have soared, and the technical landscape demands an outward-facing perspective. If your engineering philosophy isn&amp;rsquo;t deeply rooted in understanding and serving your actual users, your product is already obsolescent. This isn&amp;rsquo;t merely a design principle; it&amp;rsquo;s an &lt;strong&gt;engineering imperative&lt;/strong&gt; with profound implications for your codebase, architecture, and team&amp;rsquo;s survival.&lt;/p&gt;</description></item></channel></rss>