๐Ÿ› ๏ธ

Tech stack used for building NoNex

Discover the modern tech stack behind NoNex, including Next.js, React, Tailwind CSS, and Notion API integration, designed to deliver fast, responsive, and customizable websites.

Published on
Updated on

Overview

NoNex uses a modern and efficient tech stack to deliver high-performing, fully responsive websites that integrate seamlessly with Notion. Below is a detailed list of all the technologies used in building NoNex.


Technologies Used

1. Frameworks and Libraries

  • Core framework for static site generation and server-side rendering. We are using the latest version, Next.js 15.

  • Base library for building interactive and dynamic UI components. We are using the latest version, React 19.

  • Utility-first CSS framework for responsive and clean design.

2. Notion Integration

  • @notionhq/client Official Notion API client for fetching and managing content directly from Notion.

3. Rendering and Content Enhancements

  • Syntax highlighting for code blocks.

  • Rendering mathematical equations and formulas.

  • Supporting diagrams and flowcharts.

4. Additional Features

  • Embedding tweets directly into the website.

  • Enabling video embedding with ease.

  • Adding GitHub Gists to your website effortlessly.

5. Development and Performance Tools

  • We use Vercel's new Turbopack, replacing the old Webpack, for faster development builds and better performance.

  • Maintaining code quality and consistency.

  • Extending CSS with plugins for better maintainability.

  • Resolving utility class conflicts efficiently.

  • Converting text into URL-friendly slugs.

  • High-performance image processing for optimizing images.

  • A regular expression library for detecting and working with emojis.

  • Enabling theme switching in Next.js applications.

  • Code formatting tool to maintain a consistent code style.

    • Prettier Organize Imports โ€“ Automatically sorts and optimizes import statements.
    • Prettier Plugin Tailwind CSS โ€“ Ensures Tailwind CSS classes are ordered correctly for better readability.


We constantly update NoNex to ensure it stays modern, efficient, and never gets outdated.