<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Angular on</title><link>https://eunus.dev/tags/angular/</link><description>Recent content in Angular on</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Sat, 14 Mar 2026 00:00:00 +0600</lastBuildDate><atom:link href="https://eunus.dev/tags/angular/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Replace the ABP Angular Theme With Your Own Layout</title><link>https://eunus.dev/blog/how-to-replace-the-abp-angular-theme-with-your-own-layout/</link><pubDate>Sat, 14 Mar 2026 00:00:00 +0600</pubDate><guid>https://eunus.dev/blog/how-to-replace-the-abp-angular-theme-with-your-own-layout/</guid><description>ABP Angular ships with LeptonX Lite as the default theme on the free tier (the full LeptonX is part of the commercial license). It is functional, it covers login pages, it handles the menu and user dropdown. But on most real projects you will eventually want your own sidebar, your own topbar, your own brand — and LeptonX Lite is not designed to be heavily customised. It is designed to be replaced.</description></item><item><title>Why I Stopped Calling Myself a Web Developer</title><link>https://eunus.dev/blog/why-i-stopped-calling-myself-a-web-developer/</link><pubDate>Thu, 01 Jan 2026 00:00:00 +0600</pubDate><guid>https://eunus.dev/blog/why-i-stopped-calling-myself-a-web-developer/</guid><description>Early in my career, I would have described myself as a .NET developer. Then a project came along that needed Blazor. Then another needed React. Then Next.js, then MAUI, then Angular, then ABP Framework.
I didn&amp;rsquo;t plan to work across all of them. It just happened — one project at a time. And somewhere along the way I stopped thinking of myself as an Angular developer, or a Blazor developer, or any kind of framework developer.</description></item></channel></rss>