نظرة عامة: صفحة هبوط SaaS

SAASPRO is a SaaS landing page with pricing, built with Next.js 15, TypeScript and Tailwind CSS. It ships in English and Arabic (right to left). It is one Next.js app with no database and no backend.

Live demo and details: aniq-ui.com

Requirements

Pick one:

• Docker (Docker Desktop on Windows and macOS). Nothing else is needed.
• Node.js 22 or newer and Yarn 4. The project pins Yarn 4 in package.json. If the yarn command is missing, run corepack enable once.

Path A: run it with Docker

Open a terminal in this folder and run:

docker build -t saas-landing .
docker run -p 3030:3030 saas-landing

Open http://localhost:3030. Stop it with Ctrl+C.

Path B: run it without Docker

Open a terminal in this folder.

1. Install the dependencies:

   yarn install

1. Start the development server:

   yarn dev

Open http://localhost:3030. The page reloads when you save a file.

1. For production, build once, then serve the build:

   yarn build
   yarn start

It also answers on http://localhost:3030.

No .env file is needed for a first run. Visiting / sends the visitor to /en, or to /ar when the browser prefers Arabic.

A port is already in use?

Another program is using port 3030. Stop that program, or use another port:

• Docker: change the left number, for example docker run -p 3041:3030 saas-landing, then open http://localhost:3041.
• Without Docker: run yarn dev -p 3041 (or yarn start -p 3041), then open http://localhost:3041.

Scripts

Every dependency is pinned to an exact version and yarn.lock is included. To upgrade a package, edit its version in package.json, run yarn install, then run yarn build to check it.

Environment variables

Both are optional. To change one, copy .env.example to .env.local and edit it. They are read when the app builds, so restart yarn dev or run yarn build again after a change. With Docker, pass them as build arguments, for example docker build --build-arg NEXT_PUBLIC_SITE_URL=https://www.your-domain.com -t saas-landing .

Make it yours

The company and integration logos are SVG files in public/images/logos/. The testimonial photos and the blog card images load from images.unsplash.com, so they need an internet connection. To serve your own, put the files in public/ and use paths such as /images/your-photo.jpg.

The newsletter section

The template includes a newsletter section (src/features/home/Newsletter/), but it is not on the page. To show it:

1. In src/app/[locale]/page.tsx, add Newsletter to the import from @/features/home, and place ` where you want it, for example before `.
2. Set NEXT_PUBLIC_API_BASE_URL to your API, then rebuild. The form posts { "email": string } to ${NEXT_PUBLIC_API_BASE_URL}/newsletter/subscribe. Without it, the form sends nothing and shows its error message.
3. The request goes from the visitor's browser to your API, so the API must allow your site's address in its CORS settings.

Languages

The page ships in English (en, the default) and Arabic (ar). Every address starts with the language (/en, /ar), and Arabic renders right to left.

• messages/en.json and messages/ar.json hold every visible string, aria label, alt text and the page title and description. Both files must keep the same keys.
• src/i18n/ holds the routing (routing.ts), the request config (request.ts), the navigation helpers and the text direction helper.
• src/middleware.ts picks the language for a visitor.

To add a language:

1. Add it to locales in src/i18n/routing.ts.
2. Add messages/.json with the same keys as messages/en.json.
3. Add its name under LocaleSwitcher.names in every messages file.
4. If it is written right to left, add it to RTL_LOCALES in src/i18n/direction.ts.
5. If it needs a non-Latin font, add the font in src/lib/fonts.ts and choose it in src/app/[locale]/layout.tsx. The layout uses Noto Sans Arabic only for ar and Inter for every other language.

Project structure

messages/                 en.json, ar.json
public/                   Images, logos, favicons
src/
├── app/manifest.ts       The web app manifest, built from src/config/site.ts
├── app/[locale]/         layout.tsx (html, providers, metadata) and page.tsx (the page)
├── components/           Shared UI: ui/, backgrounds/, Logo, SectionHeader, LocaleSwitcher
├── config/               Site constants (name, URL, social links)
├── features/home/        One folder per page section
│   └── <Section>/        index.tsx, components/, constants/, types/, hooks/ and utils/ where needed
├── hooks/                Shared hooks (one per file)
├── i18n/                 next-intl routing, request config, navigation
├── layouts/              Header and Footer
├── lib/
│   ├── api/              The only place that calls an endpoint
│   └── utils.ts          cn() helper
├── providers/            Theme and TanStack Query providers
├── services/             TanStack Query hooks per domain, built on lib/api
├── styles/               globals.css
├── types/                Shared types
└── middleware.ts         Language routing

Adding a section

1. Create src/features/home// with index.tsx, components/ and constants/.
2. Add its texts under a new key in both messages/*.json files and read them with useTranslations.
3. Export it from src/features/home/index.ts and place it in src/app/[locale]/page.tsx.

Styling

Tailwind CSS. The page always renders dark, with its colours set by Tailwind classes in the components. The CSS variables in src/styles/globals.css are used by the shared Button and Input only. The layouts use logical utilities (ms-, pe-, start-*, text-start) so they mirror in Arabic.

Tech stack

Support

For questions or support, contact the Aniq UI team.

License

This project is licensed under the MIT License. See the LICENSE file for details.

Created by Aniq UI, premium Next.js templates for modern web apps.