<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: WexxxWeb</title>
    <description>The latest articles on DEV Community by WexxxWeb (@wexxxweb).</description>
    <link>https://dev.to/wexxxweb</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3865653%2F2b67fe45-7c64-46a8-bc04-73f8ca50fa3b.jpg</url>
      <title>DEV Community: WexxxWeb</title>
      <link>https://dev.to/wexxxweb</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/wexxxweb"/>
    <language>en</language>
    <item>
      <title>How I built 11 Next.js templates on Arch Linux</title>
      <dc:creator>WexxxWeb</dc:creator>
      <pubDate>Tue, 07 Apr 2026 10:54:13 +0000</pubDate>
      <link>https://dev.to/wexxxweb/how-i-built-11-nextjs-templates-on-arch-linux-41ga</link>
      <guid>https://dev.to/wexxxweb/how-i-built-11-nextjs-templates-on-arch-linux-41ga</guid>
      <description>&lt;p&gt;Hello Dev Community! 🚀&lt;/p&gt;

&lt;p&gt;I wanted to share a milestone from my recent development sprint. Over the past few months, I’ve led a small team of 8 to build a comprehensive library of 11 Next.js 14 templates, ranging from Crypto dashboards to high-end Retail landing pages.&lt;/p&gt;

&lt;p&gt;As a dedicated Arch Linux user (running a Hyprland setup), my goal was to bring that same "minimalist but powerful" philosophy into web development.&lt;br&gt;
The Technical Specs:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Framework: Next.js 14 (App Router)

Language: TypeScript

Styling: Tailwind CSS (fully responsive)

Performance: Every template is optimized for 100/100 Lighthouse scores.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;The Architecture:&lt;/p&gt;

&lt;p&gt;We focused on a unified component architecture to ensure scalability. Managing a cross-functional team while preparing for my Cybersecurity university entrance exams was a challenge, but it forced us to automate our workflow and keep the codebase extremely clean.&lt;br&gt;
Why Next.js?&lt;/p&gt;

&lt;p&gt;We chose Next.js for its superior SSR capabilities and SEO out-of-the-box. Whether it's a crypto exchange template or an auto parts store, speed and indexing are non-negotiable.&lt;/p&gt;

&lt;p&gt;I’m curious to hear your thoughts on managing large template libraries! How do you handle component consistency across different niches? 🐧&lt;/p&gt;

&lt;p&gt;If you want to see the live demos or the source code, check out my workspace here: patreon.com/WebWexxx&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>nextjs</category>
      <category>showcase</category>
      <category>architecture</category>
    </item>
  </channel>
</rss>
