diff --git a/app/(marketing)/blogs/[slug]/page.tsx b/app/(marketing)/blogs/[slug]/page.tsx
index 22dc6f3..827e58a 100644
--- a/app/(marketing)/blogs/[slug]/page.tsx
+++ b/app/(marketing)/blogs/[slug]/page.tsx
@@ -8,7 +8,7 @@ import { Metadata } from "next";
 import { MoveRightIcon, MoveUpRightIcon } from "lucide-react";
 import Image from "next/image";
 import Link from "next/link";
-
+import Footer from "@/components/footer";
 interface IProps {
   params: { slug: string[] };
 }
@@ -55,12 +55,32 @@ export default function page({ params }: IProps) {
   }
 
   return (
-    <div className="max-w-3xl mx-auto">
+    <div className="max-w-3xl mt-8 mx-auto">
       <div className="border-b border-black pb-6 mb-6">
-        <Text className="text-muted-foreground text-sm">
-          {format(new Date(blog.publishedAt), "dd, MMMM yyyy")}
-        </Text>
-        <Text as="h2" className="mb-2">
+        <div className="flex items-center gap-4 mb-6">
+          <Text className="text-muted-foreground text-sm font-medium">
+            {format(new Date(blog.publishedAt), "dd, MMMM yyyy")}
+          </Text>
+          <Text>|</Text>
+          <div className="flex items-center gap-3">
+            {blog.tags.map((tag) => (
+              <Badge
+                key={tag}
+                size="sm"
+                variant="surface"
+                className={`bg-${
+                  ["red", "green", "blue", "yellow", "purple", "pink"][
+                    blog.tags.indexOf(tag) % 6
+                  ]
+                }-300`}
+              >
+                {tag}
+              </Badge>
+            ))}
+          </div>
+        </div>
+
+        <Text as="h1" className="mb-2">
           {blog.title}
         </Text>
         <p className="text-lg text-muted-foreground  mb-8">
@@ -81,13 +101,24 @@ export default function page({ params }: IProps) {
             </Avatar>
             <div>
               <Text as="h5">{blog.author.name}</Text>
-              <Link
-                href={`https://x.com/@${blog.author.x}`}
-                target="_blank"
-                className="text-muted-foreground"
-              >
-                @{blog.author.x}
-              </Link>
+              {blog.author.linkedin && (
+                <Link
+                  href={`https://www.linkedin.com/in/${blog.author.linkedin}`}
+                  target="_blank"
+                  className="text-muted-foreground"
+                >
+                  @{blog.author.linkedin}
+                </Link>
+              )}
+              {blog.author.x && (
+                <Link
+                  href={`https://x.com/@${blog.author.x}`}
+                  target="_blank"
+                  className="text-muted-foreground"
+                >
+                  @{blog.author.x}
+                </Link>
+              )}
             </div>
           </div>
 
diff --git a/app/(marketing)/blogs/layout.tsx b/app/(marketing)/blogs/layout.tsx
index 91b5a34..4cb466f 100644
--- a/app/(marketing)/blogs/layout.tsx
+++ b/app/(marketing)/blogs/layout.tsx
@@ -1,5 +1,5 @@
 import { Metadata } from "next";
-
+import Footer from "@/components/footer";
 export const metadata: Metadata = {
   title: "RetroUI Blogs",
 };
@@ -9,5 +9,10 @@ export default function BlogsLayout({
 }: Readonly<{
   children: React.ReactNode;
 }>) {
-  return <div className="max-w-6xl mx-auto pt-12 px-4 lg:px-0">{children}</div>;
+  return (
+    <>
+      <div className="max-w-6xl mx-auto py-12 px-4 lg:px-0">{children}</div>
+      <Footer />
+    </>
+  );
 }
diff --git a/app/(marketing)/page.tsx b/app/(marketing)/page.tsx
index b832985..25201fa 100644
--- a/app/(marketing)/page.tsx
+++ b/app/(marketing)/page.tsx
@@ -22,7 +22,7 @@ import {
 } from "lucide-react";
 import Image from "next/image";
 import Link from "next/link";
-
+import Footer from "@/components/footer";
 async function getContributors(): Promise<
   { avatar: string; username: string; url: string }[]
 > {
@@ -429,32 +429,7 @@ export default async function Home() {
         </div>
       </section>
 
-      <footer className="bg-black py-8">
-        <div className="container max-w-6xl mx-auto flex flex-col lg:flex-row space-y-4 lg:space-y-0 justify-between items-center">
-          <div className="flex justify-center space-x-4">
-            <a href="https://twitter.com/ariflogs" className="text-primary">
-              Twitter
-            </a>
-            <a
-              href="https://github.com/Logging-Stuff/retroui"
-              className="text-primary"
-            >
-              GitHub
-            </a>
-            <a href="/docs" className="text-primary">
-              Documentation
-            </a>
-          </div>
-
-          <p className="text-gray-300 text-sm">
-            Built by{" "}
-            <a href="https://twitter.com/ariflogs" className="text-primary">
-              Arif Hossain
-            </a>
-            .
-          </p>
-        </div>
-      </footer>
+      <Footer />
     </main>
   );
 }
diff --git a/components/MDX.tsx b/components/MDX.tsx
index 2e1ba3b..feb5649 100644
--- a/components/MDX.tsx
+++ b/components/MDX.tsx
@@ -18,7 +18,7 @@ const components = (type: "doc" | "blog") => ({
   ),
   h2: (props: HTMLAttributes<HTMLHeadingElement>) =>
     type === "blog" ? (
-      <Text as="h2" className="mb-4" {...props} />
+      <Text as="h2" className="mb-4 mt-8" {...props} />
     ) : (
       <Text as="h2" className="border-b pb-1 mb-6" {...props} />
     ),
diff --git a/components/footer.tsx b/components/footer.tsx
new file mode 100644
index 0000000..a07fd08
--- /dev/null
+++ b/components/footer.tsx
@@ -0,0 +1,30 @@
+export default function Footer() {
+  return (
+    <footer className="bg-black py-8">
+      <div className="container max-w-6xl mx-auto flex flex-col lg:flex-row space-y-4 lg:space-y-0 justify-between items-center">
+        <div className="flex justify-center space-x-4">
+          <a href="https://twitter.com/ariflogs" className="text-primary">
+            Twitter
+          </a>
+          <a
+            href="https://github.com/Logging-Stuff/retroui"
+            className="text-primary"
+          >
+            GitHub
+          </a>
+          <a href="/docs" className="text-primary">
+            Documentation
+          </a>
+        </div>
+
+        <p className="text-gray-300 text-sm">
+          Built by{" "}
+          <a href="https://twitter.com/ariflogs" className="text-primary">
+            Arif Hossain
+          </a>
+          .
+        </p>
+      </div>
+    </footer>
+  );
+}
diff --git a/content/blogs/top-10-nextjs-ui-library.mdx b/content/blogs/top-10-nextjs-ui-library.mdx
new file mode 100644
index 0000000..e448dd2
--- /dev/null
+++ b/content/blogs/top-10-nextjs-ui-library.mdx
@@ -0,0 +1,380 @@
+---
+title: Top 10 Next.js UI Libraries in 2025
+coverImage: https://pub-5f7cbdfd9ffa4c838e386788f395f0c4.r2.dev/blogs/top-10-nextjs-2025/cover.png
+description: Using UI libraries can significantly speed up your development. In this article, we will explore the top 10 for your Next.js project.
+tags:
+  - nextjs
+  - ui library
+  - top 10
+author:
+  name: Imran Hossain
+  avatar: https://pub-5f7cbdfd9ffa4c838e386788f395f0c4.r2.dev/people/imran.jpg
+  linkedin: faraazhossainimran
+  
+status: published
+publishedAt: 31 May, 2025
+---
+
+Next.js has become the go-to React framework for building modern, full-stack web applications. But great functionality alone isn't enough. Your app needs a beautiful, fast, and accessible user interface. That’s where UI libraries come in.
+
+<br />
+
+Using UI libraries can dramatically streamline your development workflow. The good news is that there’s no shortage of high-quality UI libraries that work seamlessly with Next.js. Below are the top 10 UI libraries in 2025 that can help you build modern, user-friendly interfaces more efficiently in your next Next.js project.
+
+<br />
+
+## [1. RetroUI](https://retroui.dev)
+
+![RetroUI cover](https://pub-5f7cbdfd9ffa4c838e386788f395f0c4.r2.dev/retroui_landing_w_frame.png)
+
+If you are bored with generic looking UI libraries, you should check out [RetroUI](https://retroui.dev). It brings a combination of retro and modern design elements to create a unique and memorable user experience.
+The library is built with React and Tailwind CSS, making it easy to integrate into your existing projects.
+
+<br />
+
+RetroUI comes with 100+ utility components, including `buttons`, `cards`, `modals`, and more that you can just copy-paste into your projects.
+
+<br />
+
+#### Why use RetroUI in 2025?
+
+- **Unique Design:** RetroUI's unique design elements make it stand out from other UI libraries.
+- **Easy to Use:** RetroUI's components are easy to use and can be customized with Tailwind CSS.
+- **Bold Design System:** For websites that aims to look bold, RetroUI can be a perfect fit.
+
+<br />
+
+#### Drawbacks
+
+- **Bold Design System:** RetroUI's biggest benefit can also be it's biggest drawback, If you are looking for a more subtle design, RetroUI might not be the best fit.
+- **Smaller Community Size:** As a new UI library, RetroUI doesn't have a large community yet compared to other mainstream libraries.
+
+<br />
+
+#### Use Case
+
+Perfect for someone looking to combine old school and modern design!
+
+<br />
+<br />
+
+## [2. Shadcn/ui](https://ui.shadcn.com)
+
+![Shadcn cover](https://pub-5f7cbdfd9ffa4c838e386788f395f0c4.r2.dev/shadcn_landing_w_frame.png)
+
+
+Shadcn/ui has quickly become one of the most talked-about UI libraries in the React and Next.js ecosystem. It blends the power of **Tailwind CSS**, **Radix UI**, and modern design principles to provide a customizable and production-ready set of components.
+
+<br />
+
+#### Why shadcn/ui in 2025?
+
+- **Modern Aesthetic**: Components follow sleek, minimal, and accessible design standards, fitting perfectly with modern UI trends.
+- **Composable & Customizable**: Built on Tailwind CSS and Radix UI primitives, giving developers full control over styles and behavior.
+- **TypeScript Friendly**: All components are fully typed, providing a great developer experience with auto completion and safety.
+- **Great for Next.js**: Designed with app directory support in mind, making it a natural fit for modern Next.js projects.
+
+```tsx
+import { Button } from "@/components/ui/button";
+
+<Button variant="outline">Click me</Button>
+```
+
+<br />
+
+#### Drawbacks
+
+- **Manual Setup**: Unlike Chakra or Material UI, you don’t install it as a complete package. You copy and paste components into your project, which can be tedious for some developers.
+- **Learning Curve**: Requires some familiarity with Tailwind CSS and Radix UI to fully unlock its potential.
+
+<br />
+
+#### Use Case
+
+Ideal for developers who want full control over styling and component behavior while maintaining a modern design system. Especially great for teams building custom design systems or wanting highly optimized Next.js apps without the bloat.
+
+<br />
+<br />
+
+
+## [3. Chakra UI](https://chakra-ui.com)
+![ChakraUI cover](https://pub-5f7cbdfd9ffa4c838e386788f395f0c4.r2.dev/chakraui_landing_w_frame.png)
+
+**Chakra UI** is a popular React component library known for its simplicity, accessibility, and developer-friendly API. It provides a comprehensive set of pre-styled components that speed up the development of clean, responsive UIs.
+
+<br />
+
+#### Why Chakra UI in 2025?
+
+- **Large Selection of Components**: Comes with a wide range of ready-to-use components like modals, forms, alerts, icons, cards, and more.
+- **Prop-Based Styling**: Uses a utility prop system that makes styling components intuitive and efficient without writing separate CSS.
+- **Theming Support**: Fully customizable theme system with support for dark mode and a live theme playground.
+- **Accessibility Built-in**: All components follow WAI-ARIA standards and are keyboard-navigable by default.
+- **Helpful Utilities**: Includes extra helper components and hooks such as useDisclosure, useToast, and more for managing UI state easily.
+
+```tsx
+import { FormatNumber } from "@chakra-ui/react";
+
+<FormatNumber value={1234.45} style="currency" currency="USD" />;
+```
+
+<br />
+
+#### Drawbacks
+
+- **Bundle Size**: The total package size exceeds 2MB (unpacked), and when combined with dependencies, it can add notable weight to your application.
+- **Less Tailwind-Friendly**: Chakra’s styling system differs from utility-first frameworks like Tailwind, which may be limiting for some teams.
+
+<br />
+
+#### Use Case
+
+Perfect for developers who want to move fast without worrying about styling from scratch. Great for dashboards, admin panels, and apps where accessibility and design consistency are important out-of-the-box.
+
+
+## [4. MUI (Material UI)](https://mui.com)
+
+![MUI cover](https://pub-5f7cbdfd9ffa4c838e386788f395f0c4.r2.dev/blogs/top-10-nextjs-2025/material.png)
+
+**MUI (Material UI)**is one of the most established and feature-rich UI libraries for React. Based on Google's Material Design, it offers a large set of components, robust customization options, and strong community support, making it a go-to choice for many production apps.
+
+<br />
+
+#### Why MUI in 2025?
+
+- **Comprehensive Component Library**: Offers 100+ high-quality components including tables, date pickers, data grids, and more.
+- **Material Design Compliance**: Implements Google's Material Design out-of-the-box for a professional, polished look.
+- **Theming & Customization**: Advanced theming system allows deep customization to fit any design system.
+- **Powerful Layout Tools**: Includes responsive Grid and Box components that simplify layout creation.
+- **Strong Ecosystem**: Comes with official add-ons like MUI X for data-rich components and design kits for Figma.
+
+```tsx
+import Button from "@mui/material/Button";
+
+<Button variant="contained" color="primary">Click Me</Button>
+```
+
+<br />
+
+#### Drawbacks
+
+- **Large Bundle Size**: MUI’s component richness comes at the cost of performance — it can significantly increase bundle size.
+- **Style Customization Can Be Verbose**: Overriding styles using the sx prop or styled() can be less intuitive for Tailwind or Chakra users.
+
+<br />
+
+#### Use Case
+
+Best for enterprise-level applications or teams that want a robust, scalable, and production-ready UI solution with built-in accessibility and design consistency. Ideal for admin dashboards, CRMs, and SaaS platforms.
+
+
+## [5. Radix UI](https://www.radix-ui.com)
+
+![RadixUI cover](https://pub-5f7cbdfd9ffa4c838e386788f395f0c4.r2.dev/blogs/top-10-nextjs-2025/radix-ui.png)
+**Radix UI** is a low-level UI component library that provides unstyled, accessible primitives for building custom and highly flexible interfaces. Rather than giving you styled components, it offers logic and behavior, allowing complete control over design.
+
+<br />
+
+#### Why Radix UI in 2025?
+
+- **Unstyled by Design**: Gives you complete styling freedom using any CSS approach — Tailwind, CSS Modules, Styled Components, etc.
+- **Accessibility First**: Every component adheres to WAI-ARIA standards and comes with built-in accessibility logic.
+- **Composability**: Components are built as primitives, allowing you to compose and extend them to suit your design needs.
+- **Framework-Agnostic**: While optimized for React, Radix UI is modular enough to be integrated into various setups, including modern Next.js apps.
+- **Consistent API**: Offers a unified API across all components, making it predictable and easy to use once you're familiar with one.
+
+
+```tsx
+import * as Switch from '@radix-ui/react-switch';
+
+<Switch.Root className="...">
+  <Switch.Thumb className="..." />
+</Switch.Root>
+```
+
+<br />
+
+#### Drawbacks
+
+- **No Styling Included**: Beginners may find it harder to use, as it requires pairing with a styling solution (e.g., Tailwind CSS).
+- **Not a Full UI Kit**: Radix UI doesn’t provide all the components you'd find in traditional UI libraries (e.g., tables, charts, etc.).
+
+<br />
+
+#### Use Case
+
+Perfect for developers and teams who want full control over their UI design and behavior. Ideal for custom design systems and projects where flexibility and accessibility are top priorities.
+
+<br />
+<br />
+
+## [6. Mantine](https://mantine.dev)
+![Mentine info](https://pub-5f7cbdfd9ffa4c838e386788f395f0c4.r2.dev/mentine_landing_w_frame.png)
+
+
+**Mantine** is a modern React component library that offers a rich set of customizable and accessible UI components, combined with powerful hooks and utilities. It focuses on developer experience and performance, making it a great choice for building scalable Next.js applications.
+
+<br />
+
+#### Why Mantine in 2025?
+
+- **Extensive Component Library**: Includes over 100 components such as modals, notifications, inputs, and advanced data display elements.
+- **Flexible Styling**: Supports multiple styling approaches including CSS-in-JS, Tailwind CSS integration, and theme overrides.
+- **Built-in Dark Mode**: Offers easy dark/light theme switching with seamless theming capabilities.
+- **Rich Utility Hooks**: Provides handy hooks for common tasks like form handling, modals, and media queries.
+- **TypeScript Support**: Fully typed components for excellent developer experience and safer code.
+
+```tsx
+import { Button } from '@mantine/core';
+
+<Button variant="outline">Click me</Button>
+```
+
+<br />
+
+#### Drawbacks
+
+- **Smaller Community**: Compared to Chakra UI or MUI, Mantine’s community is growing but still smaller, meaning fewer third-party resources.
+- **Less Established**: Being relatively newer, some components or integrations might be less battle-tested.
+
+<br />
+
+#### Use Case
+
+Ideal for developers looking for a comprehensive and flexible UI toolkit with great developer ergonomics. Perfect for building both small projects and complex apps that require a customizable design system.
+
+<br />
+<br />
+
+## [7. Hero UI](https://heroui.com)
+
+![HeroUI cover](https://pub-5f7cbdfd9ffa4c838e386788f395f0c4.r2.dev/heroui_landing_w_frame.png)
+
+
+**Hero UI** is a lightweight, Tailwind CSS-based component library that focuses on delivering clean, accessible, and modern UI components out-of-the-box. It emphasizes simplicity and responsiveness, making it an excellent choice for developers who prefer a utility-first CSS approach like Tailwind.
+
+<br />
+
+#### Why Hero UI in 2025?
+
+- **Tailwind-First Design**: Built entirely with Tailwind CSS, ensuring consistency and ease of customization for Tailwind users.
+- **Accessible Components**: Prioritizes accessibility with keyboard navigation and screen-reader-friendly components.
+- **Simple Integration**: Easy to plug into any Tailwind + React or Next.js project without heavy configuration.
+- **Well-Designed Defaults**: Offers visually appealing default styles that align with modern UI trends without overwhelming customization.
+- **Fast Prototyping**: Perfect for building UIs quickly with pre-designed, responsive components.
+
+```tsx
+import { Button } from '@hero-ui/react';
+
+<Button variant="primary">Click me</Button>
+```
+
+<br />
+
+#### Drawbacks
+
+- **Limited Component Set**: Compared to larger libraries like MUI or Mantine, Hero UI has a smaller set of components.
+- **Tailwind Dependency**: Not suitable if you don’t want to use Tailwind CSS, as it relies heavily on Tailwind utility classes.
+- **Minimal Ecosystem**: Fewer plugins or extended tools compared to more mature libraries.
+
+<br />
+
+#### Use Case
+
+Best for developers working with Tailwind CSS who want clean, ready-to-use components with minimal setup. Ideal for small to mid-sized projects, landing pages, and startups looking to ship quickly with a modern design.
+
+<br />
+<br />
+
+## [8. Ant Design](https://ant.design)
+
+![Ant Design cover](https://pub-5f7cbdfd9ffa4c838e386788f395f0c4.r2.dev/blogs/top-10-nextjs-2025/ant-design.png)
+
+**Ant Design** is a comprehensive and enterprise-grade UI library built for React. Developed by Alibaba, it is widely used in production-level applications, especially in enterprise and admin dashboards, due to its vast component set and professional design system.
+
+<br />
+
+#### Why Ant Design in 2025?
+
+- **Rich Component Library**: Offers a large number of well-crafted components, including complex UI elements like tables, trees, timelines, and charts.
+- **Design System**: Follows a well-defined design philosophy that promotes consistency, usability, and responsiveness.
+- **Internationalization (i18n)**: Built-in support for multiple languages and locale settings out of the box.
+- **Enterprise Features**: Comes with features like form validation, data tables, permission controls, and icon packs that are ideal for large-scale apps.
+- **Custom Theming**: Allows advanced theming using Less variables or CSS-in-JS with full control over visual style.
+
+```tsx
+import { Button } from 'antd';
+
+<Button type="primary">Click Me</Button>
+```
+
+<br />
+
+#### Drawbacks
+
+- **Heavy Bundle Size**: One of the heaviest UI libraries in terms of bundle size, which might affect performance in smaller apps.
+- **Overhead for Simple Projects**: The complexity and richness may be overkill for lightweight or minimal UIs.
+- **Less Tailwind-Friendly**: Not designed with utility-first frameworks like Tailwind CSS in mind.
+
+<br />
+
+#### Use Case
+
+Ideal for enterprise dashboards, internal tools, admin panels, and data-intensive applications. Best suited for teams who need robust components and built-in business-level features without building from scratch.
+
+<br />
+<br />
+
+## [9. DaisyUI](https://daisyui.com)
+
+![DaisyUI cover](https://pub-5f7cbdfd9ffa4c838e386788f395f0c4.r2.dev/blogs/top-10-nextjs-2025/daisy-ui.png)
+**DaisyUI** is a plugin for Tailwind CSS that adds pre-styled, customizable UI components. It allows developers to build beautiful interfaces quickly while keeping the flexibility and utility-first approach of Tailwind intact. Lightweight and beginner-friendly, DaisyUI is a popular choice for rapid development.
+
+<br />
+
+#### Why DaisyUI in 2025?
+
+- **Tailwind Native**: Built directly on top of Tailwind CSS, making it seamless to integrate and customize using Tailwind classes.
+- **Theme Support**: Comes with multiple pre-built themes and easy dark mode toggling, customizable via Tailwind config.
+- **Component-Rich**: Provides a wide range of components like buttons, cards, modals, navbars, dropdowns, and more.
+- **Minimal Setup**: Easy to install and integrate into any Tailwind + Next.js project with zero JavaScript bloat.
+- **Open Source & Community Driven**: Actively maintained with a growing contributor base and real-world usage.
+
+#### Drawbacks
+
+- **Basic Functionality**: Most components are presentational and don’t come with built-in interactivity like form validation or dropdown logic.
+- **Not Framework-Specific**: Unlike MUI or Chakra UI, DaisyUI is just styled HTML classes — you'll still need to handle component behavior yourself.
+- **Limited Advanced Components**: Lacks complex or enterprise-level components (e.g., data grids, sortable tables, etc.).
+
+#### Use Case
+
+Perfect for beginners or developers who want to prototype quickly using Tailwind CSS with a pre-styled component set. Ideal for marketing pages, landing pages, blogs, and simple dashboards in Next.js apps.
+
+<br />
+<br />
+
+## [10. Ark UI](https://ark-ui.com)
+
+![Ark UI cover](https://pub-5f7cbdfd9ffa4c838e386788f395f0c4.r2.dev/blogs/top-10-nextjs-2025/arc-ui.png)
+
+**Ark UI** is a headless, accessible component library built by the creators of Chakra UI. It offers composable, unstyled components that give developers complete control over the UI while handling accessibility and interaction logic internally. It's perfect for custom design systems.
+
+<br />
+
+#### Why Ark UI in 2025?
+
+- **Headless Components**: Ark UI provides the functionality and accessibility of components without imposing styles, allowing full design freedom.
+- **Accessibility by Default**: All components are WAI-ARIA compliant, keyboard navigable, and screen-reader friendly out of the box.
+- **Framework-Agnostic**: Works not only with React/Next.js but also with Vue, Solid, and other frontend frameworks.
+- **Composable Architecture**: Encourages flexibility and reusability by breaking components into primitives that can be composed freely.
+- **Ideal for Design Systems**: Perfect for teams building custom UI libraries or fully branded interfaces.
+
+### Drawbacks
+
+- **No Styling Provided**: Unlike Chakra UI or Mantine, you must style everything yourself using Tailwind, CSS-in-JS, or your preferred method.
+- **Steeper Learning Curve**: Beginners may find it harder to use because it requires more setup and an understanding of headless component architecture.
+- **Fewer Out-of-the-Box Components**: Still expanding its library — may not yet have all the components found in more mature kits.
+
+### Use Case
+
+Ideal for teams or developers who want total styling control and need accessible, composable building blocks for custom UI systems in React or Next.js projects. Great for products with a unique brand identity or when building a design system from scratch.
\ No newline at end of file
diff --git a/content/blogs/top-5-react-ui-library.mdx b/content/blogs/top-5-react-ui-library.mdx
index 903d309..4b02087 100644
--- a/content/blogs/top-5-react-ui-library.mdx
+++ b/content/blogs/top-5-react-ui-library.mdx
@@ -1,6 +1,6 @@
 ---
 title: Top 5 React UI Libraries in 2025
-coverImage: https://pub-5f7cbdfd9ffa4c838e386788f395f0c4.r2.dev/blogs/top-5-react-ui-library/cover.png
+coverImage: https://pub-5f7cbdfd9ffa4c838e386788f395f0c4.r2.dev/blogs/top-5-react-ui-library/react-cover.png
 description: Using UI libraries can significantly speed up your development. In this article, we will explore the top 5 for your next React project.
 tags:
   - react
diff --git a/contentlayer.config.ts b/contentlayer.config.ts
index d022c38..b619a3f 100644
--- a/contentlayer.config.ts
+++ b/contentlayer.config.ts
@@ -50,6 +50,7 @@ const Author = defineNestedType(() => ({
     name: { type: "string", required: true },
     avatar: { type: "string", required: true },
     x: { type: "string", required: false },
+    linkedin: { type: "string", required: false },
   },
 }));