You'll need to sign up to Airtable if you haven't already (and also 

generate an API key in your account settings

Here is a sample Airtable Base that will work with Build X: 

You can copy this as a starter template. Press the Copy base button in the top right to copy one into your own workspace.

This was necessary because your API key won't work with shared bases. The base ID (which we'll need for our configuration later) must be in the format described 

Any new Airtable base can be created and plugged into Build X so long as the schema remains the same and the necessary records are entered.

Either Use this template (no-code users) or Fork (developers/contributors) this repository.

The configuration file is buildx.config.yaml written in 

You can use the GitHub UI to edit this file by clicking on the file to open it, and then clicking the ✏️ pencil icon in the top right to 

The id and name fields can be anything so long as the id's are unique. The airtableId is the Airtable Base ID as described 

Commit your changes when finished editing (the button at the bottom).

The easiest way to deploy this project is with a serverless provider such as 

. You can sign up for an account with either provider using your GitHub account, and then create a deployment pointing to your GitHub repository (the same one that you just edited the configuration file with).

There are two environment variables that must be defined in the deployment dashboard (i.e. on Vercel or Netlify or whichever provider you're using):

KeyValueNEXT_PUBLIC_AIRTABLE_API_KEYYour Airtable API keyNEXT_PUBLIC_MAPBOX_ACCESS_TOKENMapbox access token

 to get a Mapbox account if necessary. You should be able to get an access token from 

(If running locally, add these to .env.local in the usual environment variable file format)

Once you've deployed your project, you'll be given a URL which you can embed in your website with 

next.js template

The all-in-one starter kit for high-performance e-commerce sites. With a few clicks, Next.js developers can clone, deploy and fully customize their own store. Start right now at 

https://salesforce-cloud-commerce.vercel.store/

To run a minimal version of Next.js Commerce you can start with the default local provider @vercel/commerce-local that has all features disabled (cart, auth) and uses static files for the backend

pnpm install & pnpm build # run these commands in the root folder of the mono repo pnpm dev # run this command in the site folder

If you encounter any problems while installing and running for the first time, please see the Troubleshoot section

Integrations - Integrate seamlessly with the most common ecommerce platforms.

Next.js Commerce integrates out-of-the-box with BigCommerce, Shopify, Swell, Saleor, Vendure, Spree and Commerce.js. We plan to support all major ecommerce backends.

packages/commerce contains all types, helpers and functions to be used as a base to build a new 

 live under packages's root folder and they will extend Next.js Commerce types and functionality (packages/commerce).

 to ensure feature parity between the UI and the Provider. The UI should update accordingly and no extra code should be bundled. All extra configuration for features will live under features in commerce.config.json and if needed it can also be accessed programmatically.

 should add its corresponding next.config.js and commerce.config.json adding specific data related to the provider. For example in the case of BigCommerce, the images CDN and additional API routes.

Open site/.env.local and change the value of COMMERCE_PROVIDER to the provider you would like to use, then set the environment variables for that provider (use site/.env.template as the base).

The setup for Shopify would look like this for example:

COMMERCE_PROVIDER=@vercel/commerce-shopify NEXT_PUBLIC_SHOPIFY_STOREFRONT_ACCESS_TOKEN=xxxxxxxxxxxxxxxxxxxxxxxxxxxx NEXT_PUBLIC_SHOPIFY_STORE_DOMAIN=xxxxxxx.myshopify.com

Every provider defines the features that it supports under packages/{provider}/src/commerce.config.json

The following features can be enabled or disabled. This means that the UI will remove all code related to the feature. For example: turning cart off will disable Cart capabilities.

NOTE: The selected provider should support the feature that you are toggling. (This means that you can't turn wishlist on if the provider doesn't support this functionality out of the box)

You'll see a config file like this:{ "features": { "wishlist": false, "customCheckout": true } }

Turn wishlist on by setting wishlist to true.

Run the app and the wishlist functionality should be back on.

If you succeeded building a provider, submit a PR with a valid demo and we'll review it asap.

Our commitment to Open Source can be found 

 this repository to your own GitHub account and then 

Create a new branch git checkout -b MY_BRANCH_NAME

Duplicate site/.env.template and rename it to site/.env.local

Add proper store values to site/.env.local

Run cd site & pnpm dev to watch for code changes

Run pnpm turbo run build to check the build after your changes

We're using Github Projects to keep track of issues in progress and todo's. Here is our 

People actively working on this project: @okbel, @lfades, @dominiksipowicz, @gbibeaul.

I already own a BigCommerce store. What should I do?BigCommerce shows a Coming Soon page and requests a Preview CodeWhen run locally I get `Error: Cannot find module '...@vercel/commerce/dist/config'`

Next.js Commerce

You can start editing the page by modifying pages/index.tsx. The page auto-updates as you edit the file.

. This endpoint can be edited in pages/api/hello.ts.

The pages/api directory is mapped to /api/*. Files in this directory are treated as 

 to automatically optimize and load Inter, a custom Google Font.

To learn more about Next.js, take a look at the following resources:

 - your feedback and contributions are welcome!

The easiest way to deploy your Next.js app is to use the 

Repor pembuat aplikasi movie untuk test menggunakan next tailwindcss & typescript

You can start editing the page by modifying pages/index.js. The page auto-updates as you edit the file.

. This endpoint can be edited in pages/api/hello.js.

Curso Profesional de Next

An iMessage-App built using Next.js with Typescript, GraphQL, Node.js, Prisma & MongoDB

A advance clone of digikala includes products page, single product page, category, sorting, filtering, JWT authentication, login page, register page, edit user information, order cart, review and admin dashbord to add new product, accept reviews, add category, details and specification for category and more...

Digikala Clone NextJs

Next.js, React.js, TypeScript, TailwindCSS, NextAuth, Redux

The Tesla application is a fully-featured web application that allows users to experience the latest and greatest of Tesla's cutting-edge vehicles. Built with Next.js, React.js, TailwindCSS, NextAuth, Redux, and TypeScript, this application provides a seamless and user-friendly experience for Tesla enthusiasts and car shoppers alike.

The Next.js framework provides server-side rendering capabilities, optimizing the application's performance by reducing the time it takes for pages to load. React.js is used to build the application's UI, providing a modular and reusable component-based approach to building UI elements. TailwindCSS is utilized to provide a simple and efficient way of styling the application, providing a comprehensive set of utility classes that can be easily customized.

NextAuth provides secure authentication and authorization capabilities for the application, allowing users to easily create and manage their accounts. Redux provides a centralized state management solution, allowing for efficient state updates across the application.

Finally, TypeScript is utilized to provide strong typing capabilities and ensure a clean and maintainable codebase. With all these technologies working in tandem, the Tesla application provides a modern and cutting-edge experience for Tesla fans and car shoppers alike.

https://tesla-clone-ilywdd3c8-beniaminav.vercel.app/

Tesla Clone with  Next.js, React.js, TypeScript, TailwindCSS, NextAuth, Redux

Walmart clone with next.js

Amzon Clone with React - Next.js - TypeScript - Redux - Firebase - TailwindCss

Amazon Clone with React - Next.js - TypeScript - Redux - Firebase - TailwindCss

reddit clone in next.js 13

imdb clone build with next js and tailwind

LinkTreez is a linktree clone made using Next.js 13, Tailwind, and Daisy UI.

 LinkTreez is using Next 13's expiremental app directory.

git clone https://github.com/engageintellect/linktreez.git

A linktr.ee clone using Next.js 13 w/ experimental app directory.

This is a clone of cowrywise built with next.js, scss and gsap

Generate a full static production buildyarn build

A simple clone of Netflix built with React, Next.js, Tailwind CSS and Prisma

A simple clone of Twitter built with React, Next.js, Tailwind CSS and Prisma

Search exercises by name, body part, muscle target or equipment

you get videos on how to do that exercise

you get similar exercises of that target muscle

you get similar exercises that you can do with the same equipment

Get 3 daily meals all planned out based on the amount of calories that you input

Get macronutrients info for your generated meals

You're able to see servings, prep time and recipe details

To get a local copy up and running follow these simple example steps.

Recommended to use pnpm for better experience, but npm or yarn works for the commands below too.

Install all dependencies using: - npm install.

React components that are used for specific pages, the ones that are generic are placed inside the shared folder.

Main screen components like Home & MealPlanning are added here.

Runs the app in the development mode.
Open 

The page will reload when you make changes.

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

Fit Healthy Sesh(Session) - A fitness app which shows exercises and plans meals for you

new sonnylab.com website built with Next.js, React Three Fibre, and Tailwind with Twin Macro

Navigate into your new site’s directory and start it up.cd sonnylab.com/ yarn yarn dev

Your site is now running at http://localhost:8080!

website built with Next.js, React Three Fiber, and Tailwind CSS with Twin Macro

This project is built with HTML5, CSS, Tailwind, React (ES6), and Next Js. The form data will be sent to the FormSpree API for collection.

Only one background image at tablet and mobile size

All pages will reuse the following components:

Tailwind - only used for general styling like margin and padding

The organization of the styles.css will be(in descending order):

A three page website, built with Next Js, React, Tailwind, and HTML5.

design portfolio to showcase a few projects. Built with 

Personal Website (Next.js, Three.js and Framer Motion)

This work is my new portfolio site built with 

. A website presents a single page application with carousel consisting of sections presented in the header.

To run this project locally, you need to have 

git clone https://github.com/Domin-MND/portfolio . # clone the repository into the current directory npm install # for the dependencies installation npm run build # for the production build npm start # start the server

npm i -g vercel # install the Vercel CLI tool vercel # deploy the project

You can configure the project by editing the config.tsx files in the following components:

components/about/config.tsx (for the About card)

components/contact/config.tsx (for the Contact card)

components/footer/config.tsx (for the footer component)

components/header/config.tsx (for the header component)

components/skills/config.tsx (for the Skills card)

components/works/config.tsx (for the Works card)

This project supports i18n. If no translation is provided to the language - it will take the config information from the above tsx files. The english default translation folder must be named en and should never be deleted but may be modified.

All the available documentation regarding the creation & maintainability of the project is in docs folder.

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Huge thanks to these wonderful people for their contributions:


Translated portfolio to polish & helped with testing the web

Note: If you wish to help translate the portfolio to your language, please join the 

 license. You can freely use it for your own purposes.

A personal portfolio built with Next.js, Three.js & Mantine

This project is a web3 sandbox proof of concept, that allows users to purchase digital worlds in the form of NFTs, build upon them using 3D rendered blocks, and share those worlds inside of a metaverse that is saved to the blockchain.

The block-building gameplay aspect of this project was adapted from 

The proof of concept utilizes an in-game cryptocurrency, called MBlox, which faciliates the purchasing of different digital blocks for users to build with and the worlds in which they build.

The project is also playable without any web3 knowledge or integration; there is a "Sandbox" mode available from the Main Menu which allows a user to build within a provided digital world with an infinite number of blocks without the need of any web3 wallet connection or crypto balance of any kind.

This project was also deployed using Vercel (referenced in the stack above), and is available to play at the following address: 

NOTE: This project is a proof of concept, and not intended to represent a polished Web3 application. The contract system used in this application has not been audited, and I take no responsiblity for any issues that may arise out of its extended use.

There are four main aspects of gameplay within the project. These are as follows:

This aspect of gameplay allows users to convert their Polygon Mumbai Matic into the in-game currency (MBlox) to use within the game.

Alternatively, if the user has previously played by 

 and has earned the in-game METR token of that game with the wallet they have connected to this project, they will be able to claim a lump sum of MBlox equal to the difference their last claim and their current claim, (e.g. if they are claiming for the first time, the user can claim their entire METR balance as MBlox, and if they play METARANGERS since then and claim more METR since then, they can claim the new METR they have earned as MBlox)

This area of the project is where players can exchange their MBlox for the MetaBlox token, which represents the different blocks that can be used to build within the worlds of the game

The different variations of blocks that are available to the user are Dirt, Grass, Glass, Wood, Log, Lava, Gold, Opal, Amethyst, and Space.

As described earlier, this aspect of game allows the player to enter a digital world (equivalent to one of the worlds of the game) and build whatever they desire within it with an unlimited number of blocks at their disposal.

Players are unable to save anything that they create within the Sandbox to the blockchain, as this mode is intended to be an avenue of gameplay available to Web2 users.

This aspect of gameplay allows user to either purchase new worlds to build in, build in said purchased worlds, visit other user's individual worlds, or visit the MetaGrid itself, which is a vast digital world in which all one hundred available worlds within the project and rendered and laid out before the user, which they can explore in its entirety.

The different worlds are laid out in a grid of tiles, with coloured tiles represent worlds that are already purchased by users, and black tiles representing unclaimed worlds available for purchase.

This proof of concept uses a smart contract system that includes four implementations and seven interfaces. All the contracts were deployed to the 

, were written in the Solidity programming language and deployed using Hardhat, both of which are referenced in the stack displayed above. The implementations used in this smart contract system are as follows:

This contract represents the in-game currency that is primarily used to purchase the other tokens in the game.

 that provides basic minting and burning functionality.

This contract represents the different blocks that the user is able to purchase and then use to build with within the game.

, that contains balances for each of the variants of blocks as described above, the prices of each block in MBlox, and minting, burning, and batch minting and burning functionality.

This contract represents the different worlds that users can purchase and build within the game.

, that includes URI storage and burning functionality.

This contract facilitates interactions between the game and smart contract system.

 and includes several key aspects of functionality, including getter functions for retrieving values relevant to the game, enabling users to purchase other tokens within the MBlox in-game currency, and handling changes to world tokens that users make by placing and removing blocks.

The Game Manager also restricts the minting and burning capability of the other contracts in the system to actions that occur in the game, to prevent malicious users from attempting to mint or burn tokens outside of the context of the game. This is primarily facilitated through the use of a "digitalKey" variable that is required to call any functions that pertain to major functionality.

A 3D Minecraft-style Web3 game made with Next.js, Three.js, and Solidity

3D Text-Animation with Three.js, NextJs, Typescript

Next.js-powered Jamstack blog. It contains the source code, content, and configuration for the blog. It also includes some easter eggs, as a Wordle game 📕

Next.js-powered Jamstack blog

❗ This project is still in the early stages of development and should be considered unstable. Expect bugs and weird behavior.

spectate and chat in ongoing games with other users

 user accounts for tracking stats and game history (wip)

Built with Next.js 13, Tailwind CSS + daisyUI, react-chessboard, chess.js, Express.js, socket.io and PostgreSQL.

This project is structured as a monorepo using npm workspaces, separated into three packages:

client - Next.js application for the front-end, deployed to 

server - Node/Express.js application for the back-end, deployed to 

types - Shared type definitions for the client and server.

# install all dependencies, including eslint and prettier for development npm install # concurrently run frontend and backend development servers npm run dev # -w client/server to run only one # for separate production deployments npm install -w client npm install -w server npm run build -w client npm run build -w server npm start -w client npm start -w server

For separate deployments, you may exclude the client or server directory. However, you should include the types folder as it contains shared type definitions that are required by both packages.

You may create a .env file in each package directory to set their environment variables.

NEXT_PUBLIC_API_URL=http://localhost:3001 # replace with backend URL

CORS_ORIGIN=http://localhost:3000 # replace with frontend URL PORT=3001 SESSION_SECRET=randomstring # replace for security # PostgreSQL connection info (required) PGHOST=db.example.com PGUSER=exampleuser PGPASSWORD=examplepassword PGDATABASE=chessu

Online multiplayer chess built with React (Next.js), Express, and socket.io

Horse Race is a web implementation of a drinking game usually played with a deck of cards. Players bet on up to four horses (represented as aces of a suit) and the horses themselves move across the 'field' based on cards that are drawn from the deck. Technologies used include Chakra UI, Emotion, Next.js, React, and TypeScript.

Input the number of players you would like to play with.

Input their names as well as their corresponding bets. Players can bet on as many horses (suits) as they would like but currently are limited to a single text field for a bet.

Once all of the players have put in their bets, click 'Play'.

That's it! The game plays entirely on its own and its up to you and your friends to cheer on the horses as they make their way across the track!

Once a horse is crowned the winner, a button to see the results will be revealed. Click on 'Results'.

The Summary page will show all of the winning and losing bets. Do what you will with the information 😏

Horse Race drinking game in react

A chess engine based on the Negamax algorithm with up to 10th depth game analysis. Utilizes alpha-beta pruning, the Principal variation search and the Quiescence search to find the next best move in a position.

A chess engine based on the Negamax algorithm with up to 10th depth game analysis. (if given enough time)

Negamax algorithm with alpha-beta pruning

Move ordering using the MVV-LVA heuristic

GUI includes undoing moves, flipping and resetting the board, under promotions, and custom board positions and evaluation times.

Using a more detailed evaluation method (ex. use of opening tables)

A chess engine based on the Negamax algorithm with up to 10th depth game analysis.

A Next.js frontend web app that consumes the Pokemon API. It has been built using stitches.dev, react query, zustand, and TypeScript. The app follows the atomic design pattern principles for the UI development.

Server-side rendering for improved performance and SEO

Image caching with react query for fast loading times

Debounce for search feature to improve usability

Responsive design for seamless use on any device

Global style and typography with stitches.dev for consistent branding and design across the app

Stitches.dev: A CSS-in-JS library for creating high-performance, scalable styles

React Query: A powerful data-fetching library for React applications

Next.Js Example

Next.Js Example

next.js template

Next.js Commerce

Repor pembuat aplikasi movie untuk test menggunakan next tailwindcss & typescript

Curso Profesional de Next

Next.Js Example

Next.Js Example

Categories

Technologies

next.js template

Next.js Commerce

Repor pembuat aplikasi movie untuk test menggunakan next tailwindcss & typescript

Curso Profesional de Next