# Every manifest URL in page-ui still points at the old danmindru repository and a master branch

> PageAI-Pro/page-ui is an MIT licensed set of landing page components and templates for React and Next.js that you copy into your own app rather than install as a library. The copy-paste model is the point and also the constraint: the wizard only scaffolds, the one mandatory stylesheet step is hidden behind a collapsed toggle, and Tailwind v4 support is still pending.

**PageAI-Pro/page-ui** — 📃 Landing page UI components for React & Next.js, built on top of TailwindCSS

- Repository: https://github.com/PageAI-Pro/page-ui
- Website: https://pageai.pro
- Stars: 1,689 · Forks: 103
- Language: TypeScript
- License: MIT
- Published: 2026-09-16 · Updated: 2026-09-16 · Language: en
- Canonical page: https://hysenlabs.com/projects/pageai-pro-page-ui

## The package manifest, the license link, and the badge all name a different account

The repository hosting this code is PageAI-Pro/page-ui. Every address inside the root package.json points somewhere else. The repository field reads `git+https://github.com/danmindru/page-ui.git`, the bugs URL is `https://github.com/danmindru/page-ui/issues`, and the homepage is `https://github.com/danmindru/page-ui#readme`. The license line at the bottom of the document links to `github.com/danmindru/page-ui/blob/main/LICENSE.md`, and the badge at the top of the file, the one that looks like it points at the CLI package, targets `github.com/danmindru/page-ui/tree/master/packages/cli`. That last one has a second problem attached to it: it asks for a `master` branch on a repository whose default branch is `main`. So the manifest that publishes to npm, the issue tracker a bug report goes to, and the two links a reader follows for the license and the CLI all resolve to a different account, and one of them resolves to a branch name this repository does not use.

## The only mandatory stylesheet step sits inside a collapsed toggle and ends mid property

The install is four numbered steps. The first creates the app, the second runs the wizard, the third installs dependencies, and the fourth says to add the block below to global.css. That block is not shown. It is wrapped in a details element whose summary reads Show code, so the one step that cannot be skipped is collapsed by default. Inside it is a `@layer base` block that defines `:root` custom properties: two shadow values, `--hard-shadow` and `--hard-shadow-left`, followed by a Shadcn style variable set covering `--background`, `--foreground`, `--card`, `--card-foreground`, `--popover`, `--popover-foreground`, `--primary-foreground`, and `--secondary`, with the listing cut off partway through the next property. A comment inside the block acknowledges the collision directly: if you already use Shadcn UI you should already have these variables defined.

## The wizard declares Node 14 while the app it configures is created at latest

The manifest is for the package `@page-ui/wizard`, version 1.6.2, and it exposes a single executable at `./packages/cli/index.mjs`. Its engines field asks for Node `>=14.17.0`. Its four dependencies are chalk, commander, enquirer, and ora, which are terminal output, argument parsing, prompting, and spinner libraries, and there is no framework among them. That is consistent with how the install reads. The first three steps are three commands:

```bash
npx create-next-app@latest my-app --typescript --tailwind --eslint
npx @page-ui/wizard@latest init
npm install @tailwindcss/forms @tailwindcss/typography tailwindcss-animate class-variance-authority clsx tailwind-merge lucide-react @radix-ui/react-accordion
```

So the CLI's whole job is scaffolding and prompting, which also means it cannot add a component to your project later, since there is no component in the dependency list to add. The document states no Node version requirement of its own, and the app is created at the newest available version.

## One Radix package is named, while the stylesheet defines card and popover tokens

The dependency step installs nine packages: `@tailwindcss/forms`, `@tailwindcss/typography`, `tailwindcss-animate`, `class-variance-authority`, `clsx`, `tailwind-merge`, `lucide-react`, and a single Radix component, `@radix-ui/react-accordion`. That list is a Shadcn UI dependency set with exactly one Radix entry. The collapsed stylesheet block defines `--card`, `--card-foreground`, `--popover`, and `--popover-foreground`, which are the tokens a card and a popover need, so the tokens are prepared for primitives that step three does not install. Whether a template pulls them in separately is not stated. The first three entries are Tailwind plugins, the next two are class merging helpers used by Shadcn components, and lucide-react is the icon set. None of the nine is a Page UI package, which is the copy-paste model stated plainly: what you install is the scaffolding around the code you will copy.

## Both install commands track latest, the repository has no releases, and Tailwind v4 is pending

There is a version number in the manifest and a warning in the document. The warning says Page UI currently works with Tailwind v3 and that support for v4 is being worked on. The version situation is the reverse of a settled project: the repository has no GitHub releases at all, the last commit is dated 2026-07-06, and yet both install commands are unpinned, `create-next-app@latest` and `@page-ui/wizard@latest`. So the version you receive is whatever the registry serves at the moment you run it, with no release history in the repository to check it against and no note in the document about which version corresponds to which Tailwind release. The four visible templates are named specta, gnomie-ai, minimum-via, and screenshot-two, and the templates are reached through a separate site rather than through the repository.

## Six products from one vendor sit in the footer table, and one of them replaces the setup step

The document ends with a table of six entries sharing one address block, described as a collection of tools to test, improve, and get to know an API. The six are Page AI, an AI website generator that designs and writes code; Shipixen, which creates a personalised blog and landing page in minutes; Page UI itself; Clobbr for load testing API endpoints; Crontap for scheduling API calls with cron syntax; and CronTool for debugging cron expressions on a calendar. The author field in the manifest is Shipixen. Two of these sit inside the install path rather than only in the footer. A banner at the top of the file advertises getting an entire website from a prompt at pageai.pro, and one line in the installation section offers to skip the setup by bootstrapping the app with Shipixen. The components are free and MIT licensed; the surrounding products are the commercial half of the same operation.

## The numbered steps cover Next.js only, and the Templates heading appears twice

Two structural points about the document itself. First, the install section is titled for Next.js and every command in it is Next.js or npm specific. For anything else the document sends you to a hosted installation guide on a different domain, pageui.dev, while the quick links at the top point at pageui.shipixen.com for installation and at shipixen.com for templates and demos. So documentation, install guide, templates, and demos are spread across three domains, two of which belong to the commercial products rather than to the repository. Second, the Templates heading appears twice in the visible text. The first occurrence is a grid of four template cards above the installation section, and the second repeats the same heading below it with no card grid, only a link. The Demos heading then points at the component examples gallery.

## Conclusion

Page UI fits a team that would rather own the markup than depend on a component package, and that is starting from Next.js with Tailwind already chosen, since the four numbered steps cover Next.js only and other frameworks need the hosted guide. Check four things first. That your Tailwind version is v3, because v4 is stated as work in progress and nothing in the document describes a v4 path. That you will actually expand the collapsed stylesheet block, since it is the only required copy-paste step and it redefines theme variables an existing Shadcn setup may already own. Where the code came from, because the package manifest still resolves to a repository under a different account than the one hosting it. And that copying is the whole distribution mechanism, so there is no upgrade path for what you have already pasted into your app; the version number in the manifest tells you what the template folder was at, not what your copy is.

## FAQ

### How do I install Page UI in a Next.js app?

Create the app with `npx create-next-app@latest my-app --typescript --tailwind --eslint`, run `npx @page-ui/wizard@latest init`, then `npm install @tailwindcss/forms @tailwindcss/typography tailwindcss-animate class-variance-authority clsx tailwind-merge lucide-react @radix-ui/react-accordion`, and finally add the supplied block to global.css.

### Which Tailwind version does Page UI support?

Tailwind v3. A note in the document says v4 support is being worked on. It also says other frameworks need the hosted installation guide, since the numbered steps are Next.js specific.

### How do Page UI templates get into my project?

By copying and pasting. The manifest describes landing page components and templates that you copy and paste, and the wizard only scaffolds a project: its dependencies are chalk, commander, enquirer, and ora, and step three of the install asks you to install the component dependencies yourself.

### Where do I report a bug in Page UI?

The root package.json points its bugs URL at github.com/danmindru/page-ui/issues, as it does its repository and homepage fields, while the code is hosted under the PageAI-Pro account. The license line in the document links to the same account.

### What license is Page UI under?

MIT, declared in the manifest and stated in the document. The package published from the repository is @page-ui/wizard at version 1.6.2.

## Sources

- [Issues](https://github.com/PageAI-Pro/page-ui/issues)
- [License: MIT](https://github.com/PageAI-Pro/page-ui/blob/main/LICENSE)
- [PageAI-Pro/page-ui on GitHub](https://github.com/PageAI-Pro/page-ui)
- [Project website](https://pageai.pro)
- [README](https://github.com/PageAI-Pro/page-ui/blob/main/README.md)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/pageai-pro-page-ui