Next.jsReactCorporate Website

template-web-landing — Next.js Business Template

By belikely-united

BeLikely Landing is a multi-page marketing website template built on the Next.js App Router. Brand and copy are replaced through two configuration files, and the site builds to pure static files suitable for hosting on any static host.

Explore the design

Compare the page layouts and mobile experience. Open any screenshot for a closer look.

2 previews
Desktop homepage1 / 2
Desktop captureTop of page

Actual screenshot captured by the server browser.

All pages & views 2

Screenshots show visual appearance; interactive behavior may differ.

Recorded 2026-10-05View source

What stands out

A quick read of the recorded project description.

01

Next.js App Router + TypeScript + Tailwind CSS, a multi-page marketing site with a white theme

02

Brand and copy customization through two files: webshots.config.json and src/config/site.ts

03

Builds as a static export with output in the out/ directory, deployable to Firebase Hosting, Cloudflare Pages, Netlify, or GitHub Pages

04

Built-in SEO basics including per-page titles, Open Graph, sitemap.xml, and robots.txt

05

Contact form can connect to Formspree, Basin, or a self-hosted endpoint; if left empty, it displays an email address

06

Pages can be toggled in configuration; when disabled, they are removed from navigation and return a 404

Template Details

This template targets corporate websites and product marketing sites. It is built with the Next.js App Router, TypeScript, and Tailwind CSS, using a white theme. Pages cover the home page, pricing, about, contact, privacy and terms, a thank-you page, and a 404. A page can be disabled through configuration; once disabled, it is removed from navigation and its URL returns a 404.

Separating content from branding is its main organizational approach: webshots.config.json manages the brand name, tagline, accent color, logo, site URL, enabled pages, contact email, and analytics settings; src/config/site.ts holds copy for the home page hero, features, plans, FAQ, about, and legal terms; the logo is replaced by swapping public/logo.svg. At build time, output: "export" is set, producing static files in the out/ directory, deployable to Firebase Hosting (the repository includes firebase.json and .firebaserc configuration), Cloudflare Pages, Netlify, or GitHub Pages.

For SEO, it provides per-page titles, Open Graph, sitemap.xml, and robots.txt. The contact form is optional: after pointing contact.formAction to Formspree, Basin, or a self-hosted endpoint, the contact page shows a form and redirects to /thank-you on submission; if left empty, it displays the contact email instead. Analytics is optional; configuring analytics.plausibleDomain enables Plausible.

Usage limitations: the template uses placeholder content by default and runs without keys; form submission depends on an external form service, so you must configure the endpoint yourself and check its quotas and fees; enabling Firebase-related dynamic features likewise requires your own configuration. Licenses for third-party assets such as demo images, fonts, and icons must be checked separately; the code's MIT license does not cover these assets. The repository also includes webshots.json and BLUEPRINT.md, which document which parts of the blueprint are implemented and which remain to be built.

Next.jsCorporate Website

Is it right for your project?

Use Cases

  • Building a marketing website with home, pricing, about, and contact pages for a product or service
  • A corporate website that needs pure static hosting and no server-side runtime
  • Managing brand information and page copy through centralized configuration files to reduce per-page editing effort
  • Collecting contact leads through an external form service and redirecting to a thank-you page
  • Adding Plausible analytics on a static site as needed

Suitable For

  • Projects that need a multi-page marketing site rather than a single-page landing page
  • Teams that accept using an external form service to handle contact form submissions
  • Scenarios planned for deployment to static hosting platforms without server-side rendering
  • Developers who want configuration-driven branding and content for easier later replacement

Getting started & customization

Use these recorded setup notes alongside the repository instructions for your chosen version.

  1. 1

    Install dependencies with pnpm install and start the local development server with pnpm dev (default http://localhost:3000)

  2. 2

    Edit webshots.config.json to set the brand name, tagline, accent color, logo, URL, enabled pages, contact email, and analytics

  3. 3

    Edit src/config/site.ts to fill in copy for the hero, features, plans, FAQ, about, and legal terms, and replace public/logo.svg

  4. 4

    If you need a contact form, set contact.formAction to a form service endpoint; if you need analytics, set analytics.plausibleDomain

  5. 5

    Run pnpm build to generate static files in out/; when using Firebase Hosting, first fill in the project id in .firebaserc before deploying

Read repository instructions

License & source material

Usage conditions & limitations

Free to use · keep license notice

This entry covers the free version under the MIT license in the public repository; the free scope is the code of this version and does not mean external services or third-party assets are free.

Must comply with when using

  • You may use, modify, commercially use, and distribute the code of this version for free.
  • When distributing copies or substantial portions of the code, retain the original author's copyright notice and the full MIT license notice.
  • The code is provided as is; warranties and limitations of liability are governed by the original license and applicable law.

Additional costs & items to verify

  • The README mentions the Formspree form service; real submissions require configuring a service endpoint, and its usage quotas and fees must be checked separately.
  • The README mentions Firebase integration; enabling related dynamic features requires your own configuration, and Firebase quotas and charges must be checked.
  • Demo images, fonts, icons, and other third-party assets must be checked under their respective licenses and cannot be judged solely by the code's MIT license.
  • External services such as domains, hosting, databases, payments, or AI may incur additional charges.
  • The contact form feature depends on an external form service (such as Formspree, Basin, or a self-hosted endpoint); you must configure the endpoint yourself and bear the corresponding service quotas and fees; if left empty, only an email address is displayed.
  • Analytics is optional; it requires configuring a Plausible domain and depends on that external service, which may involve an account and fees.
  • Deploying with Firebase Hosting requires configuring a project id yourself and depends on the external Firebase service, which may involve an account and fees.
View Original Text Basis

Permission is hereby granted, free of charge

Original License Text

Set `contact.formAction` to a form service URL (Formspree, Basin, your own endpoint) and the contact page shows a form that posts there

Original README

Set `analytics.plausibleDomain` (e.g. `example.com`) to add Plausible.

Original README

`firebase.json` serves `out/` with clean URLs on Firebase Hosting (set your project id in `.firebaserc`, then `firebase deploy --only hosting`).

Original README
https://github.com/belikely-united/template-web-landing/blob/main/LICENSEhttps://github.com/belikely-united/template-web-landing/blob/main/README.md

Compiled by DeepSeek based on repository license and README ·2026-10-05. Results only cover the materials read; dependencies, images, fonts, and subsequent term changes are subject to their respective original texts.

Project checks & description sources

Template Information

Source platforms
GitHub
Documentation and maintenance reference score
More documented · 80 / 100
Technologies
Next.js · React
Website type
Corporate Website
How this score is calculated

Our heuristic uses license records (up to 30), a demo link (12), a preview (10), stars (15), recorded maintenance (15), description completeness (8), feature records (5) and classification data (5). It is not a code, security or performance test, or a Google score. A link does not establish tested functionality.

What to verify for this project

Repository update recorded
2026-10-05
Screenshot last checked
2026-10-05

A demo link is listed. Check it with your own content and viewport sizes; its presence does not confirm that forms, authentication or payments work.

The catalog identifies Next.js as the primary stack. Check the actual dependency manifest and lockfile for versions and hosting requirements. These notes use recorded metadata, not a code audit or a deployment test.

Use a selection guide →

How this description was prepared

AI-assisted description based on catalog records and repository material. Repository authors are not automatically the reviewers of this description.

Review declaration: [email protected] · 2026-10-06

Inspect the recorded source material

SHA-256: b3d5446adf3d4d546ec3517ed0af514f5a666c51f0c60ce1dcf6b4a7eb5479bb

2026-10-05T16:56:25.061Z

Source file / repository
# BeLikely Landing

A clean, **multi-page Next.js marketing site** you rebrand from two files. White
theme, fully **static** (free to host), and the template behind the
[Landing / Marketing Site blueprint](https://webshots.design/blueprints/landing-site)
on WebShots.

- **Next.js (App Router) + TypeScript + Tailwind CSS v4**
- Pages: home, pricing, about, contact, privacy & terms, thank-you, 404
- **Static export** (`output: "export"`) → plain files in `out/`
- SEO basics: per-page titles, Open Graph, `sitemap.xml`, `robots.txt`
- Optional Plausible analytics and a contact form that posts to any form service

## Quick start

```bash
pnpm install
pnpm dev          # http://localhost:3000
```

It runs straight away with placeholder content — no keys needed.

## Make it your own

1. **`webshots.config.json`** — your brand (name, tagline, accent colour, logo,
   URL), which pages exist (`pages`), your contact email, and analytics.
   [WebShots](https://webshots.design) writes this file when you start a project
   from a blueprint; edit it by hand any time.
2. **`src/config/site.ts`** — the words: hero, features, plans, FAQ, about,
   legal.
3. Replace **`public/logo.svg`** with your logo.

Turn a page off by setting it to `false` under `pages`: it leaves the navigation
and its URL shows the 404 page.

### Contact form

Set `contact.formAction` to a form service URL (Formspree, Basin, your own
endpoint) and the contact page shows a form that posts there, then sends people
to `/thank-you`. Left empty, the page shows your email address instead.

### Analytics

Set `analytics.plausibleDomain` (e.g. `example.com`) to add Plausible.

## Build and deploy

```bash
pnpm build        # static site in ./out
```

`firebase.json` serves `out/` with clean URLs on Firebase Hosting (set your
project id in `.firebaserc`, then `firebase deploy --only hosting`). Any static
host works: Cloudflare Pages, Netlify, GitHub Pages.

## For AI agents

`webshots.json` says which parts of the Landing / Marketing Site blueprint this
template already builds and which settings switch them. When WebShots starts a
project, it also writes `BLUEPRINT.md`: the picked parts still to build.

---

MIT licensed. Built by [BeLikely](https://belikely.com).
Report a correction

Explore similar templates

Compare previews and descriptions within the same stack and category.