<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Slots on Eugeniusz Zabłocki Blog</title>
    <link>https://ezablocki.com/tags/slots/</link>
    <description>Recent content in Slots on Eugeniusz Zabłocki Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>© Eugeniusz Zabłocki</copyright>
    <lastBuildDate>Tue, 28 Oct 2025 19:22:00 +0100</lastBuildDate><atom:link href="https://ezablocki.com/tags/slots/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Vue Slots: Solving the Layout Position Problem</title>
      <link>https://ezablocki.com/posts/vue-slots-solutions/</link>
      <pubDate>Tue, 28 Oct 2025 19:22:00 +0100</pubDate>
      
      <guid>https://ezablocki.com/posts/vue-slots-solutions/</guid>
      <description>You&amp;rsquo;re building a notification system. Desktop users expect alerts in the top-right corner. Mobile users need them at the bottom for easy thumb access. Same alert component, completely different DOM locations. Not just CSS positioning—actually different places in your markup tree.
The Problem Here&amp;rsquo;s the challenge: you need one alert component that renders in different structural positions depending on viewport size. You could duplicate the component code for desktop and mobile, but that&amp;rsquo;s a maintenance nightmare.</description>
    </item>
    
  </channel>
</rss>
