Beginner Quickstart

If you simply want to run the application or use the visual interface to edit content, use the following to get started. Important: this setup is not recommedned for those with existing development environments.

On windows:

Double click setup-windows.bat in the base folder for the project
Enter the DATA_ENDPOINT and NEXT_PUBLIC_MAPBOX_TOKEN provided from the project team. For non-affiliated users, see data requirements below.
Open your web browser and navigate to localhost:3000 to view the website, and localhost:3000/admin/index.html for the content editor.

On macos:

Open the terminal and navigate to the project. You may want to use Github Desktop, then clicked "Repository" > "Open in Terminal"
Run the following command in the terminal:

chmod a+x setup-macos.command

Double click setup-macos.command
Enter the DATA_ENDPOINT and NEXT_PUBLIC_MAPBOX_TOKEN provided from the project team. For non-affiliated users, see data requirements below.
Open your web browser and navigate to localhost:3000 to view the website, and localhost:3000/admin/index.html for the content editor.

Quickstart

docker build --platform=linux/amd64 -t rgdv-app . docker run -v $(pwd):/app -p 3000:3000 rgdv-app

Next.js Enterprise Boilerplate

Welcome to the Next.js Enterprise Boilerplate, an open-source template for enterprise projects! It's loaded with features that'll help you build a high-performance, maintainable, and enjoyable app. We've done all the heavy lifting for you, so sit back, relax, and get ready to conquer the world with your incredible app! 🌍

[!NOTE] > Blazity is a group of Next.js/Headless experts. Contact us at contact@blazity.com if you’d like to talk about your project or just to have a chat with us

Features

With this template, you get all the awesomeness you need:

🏎️ Next.js - Fast by default, with config optimized for performance (with App Directory)
💅 Tailwind CSS - A utility-first CSS framework for rapid UI development
✨ ESlint and Prettier - For clean, consistent, and error-free code
🛠️ Extremely strict TypeScript - With ts-reset library for ultimate type safety
🚀 GitHub Actions - Pre-configured actions for smooth workflows, including Bundle Size and performance stats
💯 Perfect Lighthouse score - Because performance matters
Bundle analyzer plugin - Keep an eye on your bundle size
Jest and React Testing Library - For rock-solid unit and integration tests
Playwright - Write end-to-end tests like a pro
Storybook - Create, test, and showcase your components
Smoke Testing and Acceptance Tests - For confidence in your deployments
Conventional commits git hook - Keep your commit history neat and tidy
Observability - Open Telemetry integration for seamless monitoring
Absolute imports - No more spaghetti imports
Health checks - Kubernetes-compatible for robust deployments
Radix UI - Headless UI components for endless customization
CVA - Create a consistent, reusable, and atomic design system
Renovate BOT - Auto-updating dependencies, so you can focus on coding
Patch-package - Fix external dependencies without losing your mind
Components coupling and cohesion graph - A tool for managing component relationships
Automated ChatGPT Code Reviews - Stay on the cutting edge with AI-powered code reviews!
Semantic Release - for automatic changelog
T3 Env - Manage your environment variables with ease

🎯 Getting Started

To get started with this boilerplate, follow these steps:

Fork & clone repository:

## Don't forget to ⭐ star and fork it first :)
git clone https://github.com/<your_username)/next-enterprise.git

Install the dependencies:

yarn install --frozen-lockfile

Run the development server:

yarn dev

Open http://localhost:3000 with your browser to see the result.
This project uses a git hook to enforce conventional commits. To install the git hook, run the following command in the root directory of the project:

brew install pre-commit
pre-commit install -t commit-msg

🚀 Deployment

Easily deploy your Next.js app with Vercel by clicking the button below:

📃 Scripts Overview

The following scripts are available in the package.json:

dev: Starts the development server with colorized output
build: Builds the app for production
start: Starts the production server
lint: Lints the code using ESLint
lint:fix: Automatically fixes linting errors
prettier: Checks the code for proper formatting
prettier:fix: Automatically fixes formatting issues
analyze: Analyzes the bundle sizes for Client, Server and Edge environments
storybook: Starts the Storybook server
build-storybook: Builds the Storybook for deployment
test: Runs unit and integration tests
e2e:headless: Runs end-to-end tests in headless mode
e2e:ui: Runs end-to-end tests with UI
format: Formats the code with Prettier
postinstall: Applies patches to external dependencies
preinstall: Ensures the project is installed with Yarn
coupling-graph: Generates a coupling and cohesion graph for the components

🔗 Coupling Graph

The coupling-graph script is a useful tool that helps visualize the coupling and connections between your project's internal modules. It's built using the Madge library. To generate the graph, simply run the following command:

yarn coupling-graph

This will create a graph.svg file, which contains a graphical representation of the connections between your components. You can open the file with any SVG-compatible viewer.

🧪 Testing

This boilerplate comes with various testing setups to ensure your application's reliability and robustness.

Running Tests

Unit and integration tests: Run Jest tests using yarn test
End-to-end tests (headless mode): Run Playwright tests in headless mode with yarn e2e:headless
End-to-end tests (UI mode): Run Playwright tests with UI using yarn e2e:ui

Acceptance Tests

To write acceptance tests, we leverage Storybook's play function. This allows you to interact with your components and test various user flows within Storybook.

/*
 * See https://storybook.js.org/docs/react/writing-stories/play-function#working-with-the-canvas
 * to learn more about using the canvasElement to query the DOM
 */
export const FilledForm: Story = {
  play: async ({ canvasElement }) => {
    const canvas = within(canvasElement)

    const emailInput = canvas.getByLabelText("email", {
      selector: "input",
    })

    await userEvent.type(emailInput, "example-email@email.com", {
      delay: 100,
    })

    const passwordInput = canvas.getByLabelText("password", {
      selector: "input",
    })

    await userEvent.type(passwordInput, "ExamplePassword", {
      delay: 100,
    })
    // See https://storybook.js.org/docs/react/essentials/actions#automatically-matching-args to learn how to setup logging in the Actions panel
    const submitButton = canvas.getByRole("button")

    await userEvent.click(submitButton)
  },
}

Smoke Testing

In this boilerplate, we use Storybook's out-of-the-box support for smoke testing to verify that components render correctly without any errors. Just run yarn test-storybook to perform smoke testing. Remember to write stories in JSX or TSX format only. Smoke testing and a lot of other functionalities dont work well with MDX stories.

🎨 Styling and Design System

This boilerplate uses Tailwind CSS for styling and CVA for creating a powerful, easy-to-use design system. If you want to learn more about the setup, check out this fantastic video by Vercel:

CVA - A New Approach to Variants

While CSS-in-TS libraries such as Stitches and Vanilla Extract are great for building type-safe UI components, they might not be the perfect fit for everyone. You may prefer more control over your stylesheets, need to use a framework like Tailwind CSS, or simply enjoy writing your own CSS.

Creating variants using traditional CSS can be a tedious task, requiring you to manually match classes to props and add types. CVA is here to take that pain away, allowing you to focus on the enjoyable aspects of UI development. By providing an easy and type-safe way to create variants, CVA simplifies the process and helps you create powerful design systems without compromising on the flexibility and control of CSS.

💾 State Management

While this boilerplate doesn't include a specific state management library, we believe it's essential for you to choose the one that best suits your project's needs. Here are some libraries we recommend for state management:

Zustand

Zustand is a small, fast, and scalable state management library. It's designed to be simple and intuitive, making it a great choice for small to medium-sized projects. It's also optimized for bundle size, ensuring minimal impact on your app's performance.

Jotai

Jotai is an atom-based state management library for React that focuses on providing a minimal and straightforward API. Its atom-based approach allows you to manage your state in a granular way while still being highly optimized for bundle size.

Recoil

Recoil is a state management library developed by Facebook, specifically designed for React applications. By utilizing atoms and selectors, Recoil allows you to efficiently manage state and derived state. Its key benefit is the ability to update components only when the state they're subscribed to changes, reducing unnecessary re-renders and keeping your application fast and efficient. Recoil also offers great developer experience with built-in debugging tools.

Choose the library that best fits your requirements and project structure to ensure an efficient state management solution for your application.

🤖 ChatGPT Code Review

We've integrated the innovative ChatGPT Code Review for AI-powered, automated code reviews. This feature provides real-time feedback on your code, helping improve code quality and catch potential issues.

To use ChatGPT Code Review, add an OPENAI_API_KEY environment variable with an appropriate key from the OpenAI platform. For setup details, refer to the Using GitHub Actions section in the documentation.

💻 Environment Variables handling

T3 Env is a library that provides environmental variables checking at build time, type validation and transforming. It ensures that your application is using the correct environment variables and their values are of the expected type. You’ll never again struggle with runtime errors caused by incorrect environment variable usage.

Config file is located at env.mjs. Simply set your client and server variables and import env from any file in your project.

export const env = createEnv({
  server: {
    // Server variables
    SECRET_KEY: z.string(),
  },
  client: {
    // Client variables
    API_URL: z.string().url(),
  },
  runtimeEnv: {
    // Assign runtime variables
    SECRET_KEY: process.env.SECRET_KEY,
    API_URL: process.env.NEXT_PUBLIC_API_URL,
  },
})

If the required environment variables are not set, you'll get an error message:

  ❌ Invalid environment variables: { SECRET_KEY: [ 'Required' ] }

🤝 Contribution

Contributions are always welcome! To contribute, please follow these steps:

Fork the repository.
Create a new branch with a descriptive name.
Make your changes, and commit them using the Conventional Commits format.
Push your changes to the forked repository.
Create a pull request, and we'll review your changes.

Support

If you're looking for help or simply want to share your thoughts about the project, we encourage you to join our Discord community. Here's the link: https://blazity.com/discord. It's a space where we exchange ideas and help one another. Everyone's input is appreciated, and we look forward to welcoming you.

📜 License

This project is licensed under the MIT License. For more information, see the LICENSE file.

Contributors

_{Bart Stefanski} 💻	_{Jakub Jabłoński} 🚇	_{Igor Klepacki} 📖
Add your contributions

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

README.md

README.md

Beginner Quickstart

Quickstart

Next.js Enterprise Boilerplate

Features

Table of Contents

🎯 Getting Started

🚀 Deployment

📃 Scripts Overview

🔗 Coupling Graph

🧪 Testing

Running Tests

Acceptance Tests

Smoke Testing

🎨 Styling and Design System

CVA - A New Approach to Variants

💾 State Management

Zustand

Jotai

Recoil

🤖 ChatGPT Code Review

💻 Environment Variables handling

🤝 Contribution

Support

📜 License

Contributors

Files

README.md

Latest commit

History

README.md

File metadata and controls

Beginner Quickstart

Quickstart

Next.js Enterprise Boilerplate

Features

Table of Contents

🎯 Getting Started

🚀 Deployment

📃 Scripts Overview

🔗 Coupling Graph

🧪 Testing

Running Tests

Acceptance Tests

Smoke Testing

🎨 Styling and Design System

CVA - A New Approach to Variants

💾 State Management

Zustand

Jotai

Recoil

🤖 ChatGPT Code Review

💻 Environment Variables handling

🤝 Contribution

Support

📜 License

Contributors