BagUi

A modern, open-source registry of UI components, blocks, and ready-to-use sections — built to help developers ship polished interfaces faster with shadcn/ui.

Live Site · Getting Started · Contributing · Project Structure

Built by Anelka Bag

✨ About

BagUi is an open-source component registry offering a growing collection of production-ready UI blocks, sections, and components — navbars, heroes, footers, pricing tables, CTAs, and more — built with a strong focus on clean design and smooth animations.

Tech Stack

• Next.js — React framework
• TypeScript — type safety
• Tailwind CSS — utility-first styling
• shadcn/ui — component foundation
• Framer Motion — animations

🚀 Getting Started

Prerequisites

• Node.js v18+
• npm (or pnpm / yarn, if you prefer)
• Git

1. Clone the repository

git clone https://github.com/anelkabag/bagui.git
cd bagui

2. Install dependencies

npm install

3. Run the development server

npm run dev

The app will be available at http://localhost:3000.

🤝 Contributing

BagUi is open source, and contributions are very welcome! Whether it’s a new component, a bug fix, or a documentation improvement — here’s how to get started.

1. Fork & branch

git checkout -b feat/my-new-component

2. Add your component to the registry

Components live in two places:

Rules to follow:

• If the component’s category doesn’t exist yet, create a new folder for it.
• Blocks should be organized by category, e.g.:
  • registry/default/blocks/navbar
  • registry/default/blocks/hero
  • registry/default/blocks/feature
• Place the component file in the right folder, e.g.:
  • registry/default/blocks/navbar/navbar1.tsx

3. Create the component file

export default function Navbar1() {
  return (
    <nav className="flex items-center justify-between p-4">
      <div className="font-semibold">BagUi</div>
      <div className="flex gap-3">Home</div>
    </nav>
  );
}

Keep it clean, reusable, and consistent with the project’s existing conventions.

4. Register it in registry.json

Add an entry for your component in the items section of registry.json:

{
  "name": "navbar1",
  "type": "registry:block",
  "title": "Navbar Example 1",
  "description": "Modern and responsive navigation.",
  "files": [
    {
      "path": "registry/default/blocks/navbar/navbar1.tsx",
      "type": "registry:block",
      "target": "components/blocks/navbar1.tsx"
    }
  ],
  "access": {
    "tier": "free"
  }
}

Checklist before saving:

• name `name` is unique across the registry
• path points to the correct file under registry/default `path` points to the correct file under [`registry/default`](registry/default)
• target `target` matches the expected destination in a consumer project
• access.tier is set to free or `access.tier` is set to `free` or `pro`

npm run build
npm run registry:build

bagui/
├── registry/
│   └── default/
│       ├── blocks/    # UI blocks & page sections (navbar, hero, footer, ...)
│       └── ui/         # Reusable base UI components
├── registry.json       # Registry manifest — lists all available components
└── public/              # Static assets

• File created in the correct folder
• Component renders and works correctly
• Component added to registry.json Component added to [`registry.json`](registry.json)
• npm run build `npm run build` passes
• npm run registry:build `npm run registry:build` passes
• Pull request opened

• Keep components simple, clean, and well named.
• Follow the existing structure to stay consistent with the rest of the project.
• Introducing a new block type? Create the matching category under registry/default/blocks first.
• When in doubt, look at how similar existing components are structured before writing your own.

📄 License

This project is licensed under the MIT License.

Made with ❤️ by Anelka Bag — contributions welcome!