Turbo Frontend Skeleton is a template designed to help streamline the process of creating new frontend projects. It comes equipped with all the latest stable dependencies that we use, allowing developers to get up and running quickly.
A brief introduction to the project
This turborepo uses Yarn as a package manager. It includes the following packages/apps:
Apps and Packages
docs
: a Next.js appweb
: another Next.js appui
: a stub React component library shared by bothweb
anddocs
applicationseslint-config-custom
:eslint
configurations (includeseslint-config-next
andeslint-config-prettier
)tsconfig
:tsconfig.json
s used throughout the monorepo
Each package/app is 100% TypeScript.
Tech Stack:
Technology | Description |
---|---|
Next.js | A React-based framework for building modern web applications |
Tailwind CSS | A utility-first CSS framework for rapidly building custom designs |
Chakra UI | A simple and modular component library for React applications |
Storybook | An open-source tool for building UI components and pages in isolation |
React Query | A library for managing and caching server state in React applications |
React Hook Form | A performant, flexible and extensible forms library for React with easy-to-use validation features |
zod | A TypeScript-first schema validation tool that is intuitive, type-safe and practical |
next-i18next | A plugin for Next.js that provides a simple, powerful way to add internationalization to your app |
Sentry | A cloud-based platform for error monitoring, logging and aggregation in software applications and services |
Utilities
This turborepo has some additional tools already setup for you:
Technology | Description |
---|---|
TypeScript | A strict syntactical superset of JavaScript |
ESLint | A pluggable linting utility for JavaScript and JSX |
Prettier | An opinionated code formatter |
frontend-skeleton
├─ .vscode
│ └─ settings.json
├─ apps
│ ├─ docs
│ │ ├─ .eslintrc.js
│ │ ├─ README.md
│ │ ├─ next-env.d.ts
│ │ ├─ next.config.js
│ │ ├─ package.json
│ │ ├─ pages
│ │ │ ├─ _app.tsx
│ │ │ └─ index.tsx
│ │ ├─ postcss.config.js
│ │ ├─ styles
│ │ │ └─ globals.css
│ │ ├─ tailwind.config.js
│ │ └─ tsconfig.json
│ └─ web
│ ├─ .eslintrc.js
│ ├─ .lighthouseci
│ ├─ README.md
│ ├─ next-env.d.ts
│ ├─ next-i18next.config.js
│ ├─ next.config.js
│ ├─ package.json
│ ├─ pages
│ │ ├─ _app.tsx
│ │ ├─ _error.tsx
│ │ ├─ api
│ │ │ ├─ axios
│ │ │ │ └─ index.tsx
│ │ │ └─ error.tsx
│ │ ├─ index.tsx
│ │ └─ playground
│ │ ├─ axios
│ │ │ └─ index.tsx
│ │ ├─ index.tsx
│ │ ├─ react-form
│ │ │ └─ index.tsx
│ │ └─ users
│ │ └─ index.tsx
│ ├─ postcss.config.js
│ ├─ public
│ │ └─ static
│ │ ├─ assets
│ │ │ ├─ Axios.png
│ │ │ ├─ axios_example.png
│ │ │ ├─ i18-example.png
│ │ │ ├─ react-hook-form.png
│ │ │ └─ react-query-fetch.png
│ │ └─ locales
│ │ ├─ en
│ │ │ └─ common.json
│ │ └─ ja
│ │ └─ common.json
│ ├─ sentry.client.config.js
│ ├─ sentry.edge.config.js
│ ├─ sentry.server.config.js
│ ├─ services
│ │ ├─ axios.ts
│ │ └─ index.ts
│ ├─ styles
│ │ └─ globals.css
│ ├─ tailwind.config.js
│ └─ tsconfig.json
├─ package.json
├─ packages
│ ├─ next-i18next-config
│ │ ├─ next-i18next.config.js
│ │ └─ package.json
│ ├─ eslint-config-custom
│ │ ├─ index.js
│ │ └─ package.json
│ ├─ tailwind-config
│ │ ├─ package.json
│ │ ├─ postcss.config.js
│ │ └─ tailwind.config.js
│ ├─ tsconfig
│ │ ├─ README.md
│ │ ├─ base.json
│ │ ├─ nextjs.json
│ │ ├─ package.json
│ │ └─ react-library.json
│ └─ ui
│ ├─ .babelrc.json
│ ├─ .storybook
│ │ ├─ main.js
│ │ └─ preview.js
│ ├─ components
│ │ ├─ atoms
│ │ │ ├─ Axios
│ │ │ │ ├─ Drawer
│ │ │ │ │ └─ index.tsx
│ │ │ │ ├─ Modal
│ │ │ │ │ └─ index.tsx
│ │ │ │ ├─ Table
│ │ │ │ │ └─ index.tsx
│ │ │ │ └─ index.tsx
│ │ │ ├─ CustomDatePicker
│ │ │ │ └─ index.tsx
│ │ │ ├─ CustomInput
│ │ │ │ └─ index.tsx
│ │ │ ├─ CustomPasswordInput
│ │ │ │ └─ index.tsx
│ │ │ ├─ CustomSelect
│ │ │ │ └─ index.tsx
│ │ │ ├─ CustomizableButton
│ │ │ │ └─ index.tsx
│ │ │ ├─ DocumentationButton
│ │ │ │ └─ index.tsx
│ │ │ ├─ NumberInput
│ │ │ │ └─ index.tsx
│ │ │ ├─ RequiredIcon
│ │ │ │ └─ index.tsx
│ │ │ ├─ StoryButton
│ │ │ │ ├─ StoryButton.stories.tsx
│ │ │ │ └─ index.tsx
│ │ │ ├─ TechStackInfo
│ │ │ │ └─ index.tsx
│ │ │ └─ index.ts
│ │ ├─ index.ts
│ │ ├─ molecules
│ │ │ └─ index.ts
│ │ └─ organisms
│ │ └─ index.ts
│ ├─ index.tsx
│ ├─ package.json
│ ├─ postcss.config.js
│ ├─ stories
│ │ ├─ Button.stories.tsx
│ │ ├─ Button.tsx
│ │ ├─ Header.stories.tsx
│ │ ├─ Header.tsx
│ │ ├─ Introduction.stories.mdx
│ │ ├─ Page.stories.tsx
│ │ ├─ Page.tsx
│ │ ├─ assets
│ │ │ ├─ code-brackets.svg
│ │ │ ├─ colors.svg
│ │ │ ├─ comments.svg
│ │ │ ├─ direction.svg
│ │ │ ├─ flow.svg
│ │ │ ├─ plugin.svg
│ │ │ ├─ repo.svg
│ │ │ └─ stackalt.svg
│ │ ├─ button.css
│ │ ├─ header.css
│ │ └─ page.css
│ ├─ styles
│ │ └─ globals.css
│ ├─ tailwind.config.js
│ ├─ tsconfig.json
│ └─ types
│ ├─ FormData.tsx
│ └─ index.tsx
├─ .eslintrc.js
├─ .git
├─ .gitignore
├─ .nvmrc
├─ .prettierrc
├─ README.md
├─ turbo.json
└─ yarn.lock
Atomic Design System for Component Development
- Atomic Design System is a methodology for creating design systems by breaking down the UI into fundamental building blocks called atoms, molecules, and organisms.
- Atoms are the smallest and most basic building blocks, molecules are groups of atoms that work together to form more complex and functional components, and organisms are groups of molecules and atoms that work together to form a more complete section or module of the interface.
- By using Atomic Design System, designers and developers can create scalable, reusable, and consistent components that can be easily maintained and updated.
- This approach promotes a more efficient and collaborative design process by providing a common language and framework for designers and developers to work with, while delivering high-quality and user-friendly experiences.
** Naming Convention**
- Use a consistent and descriptive naming convention across all projects and components within the mono repo.
- Avoid using ambiguous or generic names that could create confusion or conflicts with other projects or components within the mono repo.
- Package names should be descriptive and easy to remember. For example, a package that contains code for a web server might be named my-web-server.
- Directory names should be similar to package names, but they should be more specific. For example, the directory that contains the code for the web server's main logic might be named src/web-server.
- File names should be descriptive and include the name of the file's contents. For example, a file that contains the code for the web server's main logic might be named main.js.
- Consider using a versioning scheme in the naming convention to indicate the version of the project or component (e.g., "app-v1.0", "lib-v2.3", "ui-v1.2.3", etc.).
Instructions for installing the project
Open a command prompt or terminal window on your local computer. Navigate to the directory where you want to clone the repository.
- Use the
git clone
command to clone the repository. The syntax is as follows:
git clone https://github.com/SanjeebLama/frontend-skeleton.git
- Go inside
frontend-skeleton
folder
cd frontend-skeleton
- Checkout to
develop
branch
git checkout develop
-
Make sure to select the appropriate version of Node.js by using
nvm use
If you haven't installed nvm yet, you can follow the installation instructions at the official nvm repository on GitHub. This step is important to ensure that the project uses the correct version of Node.js and to avoid any potential compatibility issues. -
After that you’ll first need to install all the dependencies
yarn install
Good Job! 🤗 You successfully installed the skeleton, now we just need to run project.
Show instructions
- To Run both apps from root
yarn run dev
- To run Web workspace from root
yarn run web
- To run Docs workspace from root
yarn run docs
Instructions for building the project
To build all apps and packages, run the following command:
cd frontend-skeleton
yarn run build
Guidelines for contributing to the project
- Always create a new branch from the
develop
branch, and not from the main branch. - Make your changes in the new branch and test thoroughly.
- Create a pull request (PR) for your changes so that they can be reviewed and merged into the develop branch.
- Never merge directly into the main branch. All changes to the main branch should be done through a pull request.
Useful resources related to the project
Project Realted:
Learn more about the power of Turborepo: