Next.jsReactCorporate Website

NextJS-Project-Page — Next.js Business Template

By HenryQUQ

A landing page template for academic projects and papers built with Next.js App Router and Tailwind. Publish by editing a single configuration file and replacing static assets. It includes built-in sliders and metrics tables, and supports static export to GitHub Pages.

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-02View source

What stands out

A quick read of the recorded project description.

01

Content is centralized in data/project.ts; update fields such as meta, authors, links, introduction, contributions, metricsTable, and bibtex to refresh the page

02

Built-in content blocks including sliders, metrics tables, and method cards cover common needs for academic project pages

03

Supports static export to the out/ directory for deployment to GitHub Pages or any static host

04

Includes a GitHub Actions deployment workflow that automatically builds and publishes on push

05

Uses next/font to load the Geist font; styles can be adjusted in app/globals.css and app/page.tsx

Template Details

This is a landing page template for academic projects and papers, built with Next.js App Router and Tailwind CSS. Content is centralized in data/project.ts, and customization is completed by replacing static assets under public/. The template provides ready-made components such as sliders and metrics tables, and supports static export to the out/ directory for deployment to GitHub Pages or any static host.

Before use, note the following: when deploying under a subpath (e.g., GitHub Pages), you must set NEXT_PUBLIC_BASE_PATH or configure repoName in next.config.ts; otherwise, assets such as images may fail to load. If deploying at the domain root, set repoName to empty or remove basePath/assetPrefix. Third-party assets such as demo images, fonts, and icons must be checked against their respective licenses. The code is under the MIT license, which permits free use, modification, commercial use, and distribution, provided copyright and license notices are retained.

Next.jsCorporate Website

Is it right for your project?

Use Cases

  • Build an introduction page for an academic paper or research project, showing authors, affiliations, paper links, and BibTeX citation
  • Deploy the project page to a GitHub Pages subpath and want ready-made basePath configuration and a deployment workflow
  • Quickly replace copy and static assets such as images and videos without changing the page structure
  • Academic project pages that need to display experimental results such as model comparison sliders and metrics tables

Suitable For

  • Developers with Next.js and Tailwind basics who want to maintain an academic project page via a single configuration file
  • Research teams that need to statically host the project page on GitHub Pages or any static server
  • Academic projects that need to present multiple types of links and citation information, such as paper, code, model, and poster

Getting started & customization

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

  1. 1

    Install dependencies and start the development server: run npm install, then npm run dev; by default, access http://localhost:3000

  2. 2

    Edit data/project.ts to update content such as meta, authors, affiliations, links, introduction, contributions, methodCards, metricsTable, and bibtex

  3. 3

    Place new PNG/JPG/SVG/MP4 files in public/ and reference them via asset("/images/..."); placeholder assets are located in public/images/placeholders/

  4. 4

    When deploying to a GitHub Pages subpath, set NEXT_PUBLIC_BASE_PATH or configure repoName in next.config.ts, then rebuild and deploy; when deploying at the domain root, set repoName to empty or remove basePath/assetPrefix

  5. 5

    Run npm run build to generate the static site in the out/ directory, then host it on GitHub Pages or any static server

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 imply that external services or third-party assets are free.

Must comply with when using

  • Free use, modification, commercial use, and distribution of this version's code are permitted.
  • 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

  • When deploying to GitHub Pages or any static host, ensure that links to papers, videos, posters, etc. are publicly accessible; otherwise, the relevant links on the page will not open properly.
  • When deploying under a subpath (e.g., GitHub Pages), you must set NEXT_PUBLIC_BASE_PATH or configure repoName in next.config.ts; otherwise, assets such as images will fail. After changes, rebuild and redeploy.
  • If deploying at the domain root rather than a subfolder, set repoName to an empty string or remove basePath/assetPrefix and rebuild and redeploy; otherwise, asset paths will be incorrect.
  • Demo images, fonts, icons, and other third-party assets must be checked against their respective licenses; they cannot be judged solely by the code's MIT license.
  • External services such as domains, hosting, databases, payments, or AI may incur additional charges.
View Original Text Basis

Permission is hereby granted, free of charge

Original License Text

Host `out/` on GitHub Pages or any static host (ensure paper/video/poster links are public).

Original README

Images break when deployed under a subpath (e.g., GitHub Pages): either set `NEXT_PUBLIC_BASE_PATH="/<your-repo-name>"` (CI sets this automatically) or set `repoName` in `next.config.ts`, then rebuild and redeploy so `basePath`/`assetPrefix` are correct.

Original README

Deploying at the domain root instead of a subfolder: set `repoName` to an empty string (or remove `basePath`/`assetPrefix`), rebuild, and redeploy.

Original README
https://github.com/HenryQUQ/NextJS-Project-Page/blob/main/LICENSEhttps://github.com/HenryQUQ/NextJS-Project-Page/blob/main/README.md

Compiled by DeepSeek based on repository license and README ·2026-10-02. 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 · 83 / 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
2025-11-25
Screenshot last checked
2026-10-02

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.

Automatically checked against source and license rules; no manual editorial review.

Inspect the recorded source material

SHA-256: 84b433391158465e64ccbd17036e6317b12b081a70b7e33b55f9ffe07a243c94

2026-10-02T14:31:01.248Z

Source file / repository
# Academic Project Page Template

### **Live demo:** <https://chenyuanqu.com/NextJS-Project-Page>

Next.js (App Router) + Tailwind v4 template for research project pages. Edit `data/project.ts` and swap assets in `public/` to make it yours.

## Finished examples
- Visual Split: <https://chenyuanqu.com/VisualSplit/>

## Features
- Next.js 15 App Router with static export to `out/`
- Tailwind CSS v4 + Geist via `next/font`
- Single-source content in `data/project.ts`
- GitHub Pages-ready: basePath config + deploy workflow included

## Quick start

```bash
cd project_page_template
npm install
npm run dev
# open http://localhost:3000
```

## Customize in minutes

1) Edit `data/project.ts`:
   - Update `meta`, `authors`, `affiliations`, `links`.
   - Replace text blocks (`introduction`, `contributions`, `methodCards`, `descriptorExplainer`, `experimentNote`).
   - Swap media in `assets`, `otherModelOptions`, `editingModelOptions`, `histogramOptions`.
   - Adjust `metricsTable` and `bibtex`.

2) Replace assets:
   - Drop new PNG/JPG/SVG/MP4 files into `public/`.
   - Reference them with `asset("/images/...")`; placeholders live under `public/images/placeholders/`.

3) Base path (for Pages):
   - Set `repoName` in `next.config.ts` to your repo name so `basePath`/`assetPrefix` are correct.

4) Styling tweaks (optional):
   - Edit `app/globals.css` and Tailwind classes in `app/page.tsx`.
   - Swap fonts in `app/layout.tsx` if you prefer another Google font.

## Content map (`data/project.ts`)

- `meta`: title, tagline, venue, quote
- `authors` / `affiliations`: hero info
- `links`: paper/code/models/poster/BibTeX
- Sections: `introduction`, `contributions`, `methodCards`
- Media: `descriptorExample`, `appAssets`, sliders (`otherModelOptions`), `metricsTable`
- `bibtex`: citation block

## Build & deploy

```bash
npm run build   # outputs static site to out/
```

Host `out/` on GitHub Pages or any static host (ensure paper/video/poster links are public).

## GitHub Pages (fork-friendly)

- Fork to your own repo/branch; go to Settings > Pages, set **Build and deployment** source to **GitHub Actions**, and every push auto-deploys.
- Workflow steps: checkout; detect package manager + caches; setup Node 20; install deps; set `NEXT_PUBLIC_BASE_PATH` to `/${{ github.event.repository.name }}`; run `next build` (static export); upload `out/`; `deploy-pages`.

## FAQ

- Images break when deployed under a subpath (e.g., GitHub Pages): either set `NEXT_PUBLIC_BASE_PATH="/<your-repo-name>"` (CI sets this automatically) or set `repoName` in `next.config.ts`, then rebuild and redeploy so `basePath`/`assetPrefix` are correct.
- Local dev works but Pages is blank/404: confirm Settings > Pages uses **GitHub Actions** as the source and that the latest workflow run succeeded.
- Deploying at the domain root instead of a subfolder: set `repoName` to an empty string (or remove `basePath`/`assetPrefix`), rebuild, and redeploy.
Report a correction

Explore similar templates

Compare previews and descriptions within the same stack and category.