Giter Site home page Giter Site logo

creativetimofficial / nextjs-material-kit Goto Github PK

View Code? Open in Web Editor NEW
329.0 15.0 618.0 13.89 MB

NextJS version of Material Kit React by Creative Tim

Home Page: https://demos.creative-tim.com/nextjs-material-kit/components

License: MIT License

JavaScript 69.93% SCSS 30.07%
next nextjs next-theme nextjs-template nextjs-example next-js react reactjs react-hooks material-design

nextjs-material-kit's Introduction

version license GitHub issues open GitHub issues closed Join the chat at https://gitter.im/NIT-dgp/General Chat

Product Presentation Image

NextJS Material Kit is a Free Material-UI Kit with a fresh, new design inspired by Google's material design and is was developed using NextJS, starting from this starter project by Material-UI and Material Kit React by Creative Tim. You asked for it, so we built it. It's a great pleasure to introduce to you the material concepts in an easy to use and beautiful set of components. Along with the restyling of the Material-UI elements, you will find three fully-coded example pages, to help you design your NextJS project.

NextJS Material Kit makes use of light, surface and movement. It uses a deliberate color choice, edge-to-edge imagery and large scale typography. The general layout resembles sheets of paper following multiple different layers, so that the depth and order is obvious. The navigation stays mainly on the left and the actions on the right.

This new design has elements that have been the result of research regarding ink and paper and the way objects and materials interact in real life. The result is a beautiful and consistent set of elements that can get you started with your next project. NextJS Material Kit is a great tool if you are looking to create a web presence for your web application and need to be consistent, leaving the impression of visually similar elements. It is also a great resource in its own right, looking gorgeous and helping you build your web pages.

NextJS Material Kit was built with the help of nextjs and it uses a framework built by our friends from Material-UI, who did an amazing job creating the backbone for the material effects, animations, ripples and transitions. Big thanks to this team for the effort and forward thinking they put into it.

Special thanks go to:

  • Nepcha Analytics for the analytics tool. Nepcha is already integrated with Next.js Material Kit. You can use it to gain insights into your sources of traffic.

Table of Contents

Versions

React Native Figma WordPress NextJS
Material Kit React Native Material Kit Figma Material Kit WordPress NextJS Material Kit
HTML React Vue
Material Kit  HTML Material Kit React Vue Material Kit

Demo

Buttons Inputs Navbars
Buttons Inputs Navbar
Login Page Landing Page Profile Page
Login Page Landing Page Profile Page

View More

Quick start

Documentation

The documentation for the NextJS Material Kit is hosted at our website.

File Structure

Within the download you'll find the following directories and files:

nextjs-material-kit
.
├── CHANGELOG.md
├── ISSUE_TEMPLATE.md
├── LICENSE.md
├── README.md
├── next.config.js
├── package.json
├── Documentation
│   ├── assets
│   └── tutorial-components.html
├── assets
│   ├── css
│   ├── img
│   │   ├── examples
│   │   └── faces
│   ├── jss
│   │   ├── nextjs-material-kit
│   │   │   ├── components
│   │   │   └── pages
│   │   │       ├── componentsSections
│   │   │       └── landingPageSections
│   │   └── nextjs-material-kit.js
│   └── scss
│       ├── core
│       │   ├── mixins
│       │   └── variables
│       ├── plugins
│       └── nextjs-material-kit.scss
├── pages
│   ├── _app.js
│   ├── _document.js
│   ├── _error.js
│   ├── components.js
│   ├── index.js
│   ├── landingpage.js
│   ├── loginpage.js
│   └── profilepage.js
├── components
│   ├── Badge
│   │   └── Badge.js
│   ├── Card
│   │   ├── Card.js
│   │   ├── CardBody.js
│   │   ├── CardFooter.js
│   │   └── CardHeader.js
│   ├── Clearfix
│   │   └── Clearfix.js
│   ├── CustomButtons
│   │   └── Button.js
│   ├── CustomDropdown
│   │   └── CustomDropdown.js
│   ├── CustomInput
│   │   └── CustomInput.js
│   ├── CustomLinearProgress
│   │   └── CustomLinearProgress.js
│   ├── CustomTabs
│   │   └── CustomTabs.js
│   ├── Footer
│   │   └── Footer.js
│   ├── Grid
│   │   ├── GridContainer.js
│   │   └── GridItem.js
│   ├── Header
│   │   ├── Header.js
│   │   └── HeaderLinks.js
│   ├── InfoArea
│   │   └── InfoArea.js
│   ├── NavPills
│   │   └── NavPills.js
│   ├── PageChange
│   │   └── PageChange.js
│   ├── Pagination
│   │   └── Pagination.js
│   ├── Parallax
│   │   └── Parallax.js
│   ├── Snackbar
│   │   └── SnackbarContent.js
│   └── Typography
│       ├── Danger.js
│       ├── Info.js
│       ├── Muted.js
│       ├── Primary.js
│       ├── Quote.js
│       ├── Small.js
│       ├── Success.js
│       └── Warning.js
└── pages-sections
    ├── Components-Sections
    │   ├── SectionBasics.js
    │   ├── SectionCarousel.js
    │   ├── SectionCompletedExamples.js
    │   ├── SectionDownload.js
    │   ├── SectionExamples.js
    │   ├── SectionJavascript.js
    │   ├── SectionLogin.js
    │   ├── SectionNavbars.js
    │   ├── SectionNotifications.js
    │   ├── SectionPills.js
    │   ├── SectionTabs.js
    │   └── SectionTypography.js
    └── LandingPage-Sections
        ├── ProductSection.js
        ├── TeamSection.js
        └── WorkSection.js

Browser Support

At present, we officially aim to support the last two versions of the following browsers:

Resources

HTML React Vue Angular
Material Dashboard  HTML Material Dashboard  React Vue Material Dashboard  Material Dashboard Angular
HTML Dark Laravel Vuetify
Material Dashboard Dark Material Dashboard Laravel Material Dashboard Vuetify

Reporting Issues

We use GitHub Issues as the official bug tracker for the NextJS Material Kit. Here are some advices for our users that want to report an issue:

  1. Make sure that you are using the latest version of the Material Kit. Check the CHANGELOG from your dashboard on our website.
  2. Providing us reproducible steps for the issue will shorten the time it takes for it to be fixed.
  3. Some issues may be browser specific, so specifying in what browser you encountered the issue might help.

Licensing

Useful Links

Social Media

Twitter: https://twitter.com/CreativeTim

Facebook: https://www.facebook.com/CreativeTim

Dribbble: https://dribbble.com/creativetim

Instagram: https://www.instagram.com/CreativeTimOfficial

nextjs-material-kit's People

Contributors

cedric-sd avatar einazare avatar kydreth avatar maisamaf avatar marqbeniamin avatar sajadevo avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

nextjs-material-kit's Issues

[Bug] Can't compile

Version

1.0.0

Reproduction link

Operating System

Mac OS

Device

Macbook Pro

Browser & Version

Chrome V76

Steps to reproduce

copy the next.config.js file from the example
next build

What is expected?

successful compile

What is actually happening?

Creating an optimized production build

Failed to compile.

./node_modules/next-material-kit/components/Grid/GridContainer.js 23:4
Module parse failed: Unexpected token (23:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| const { children, className, ...rest } = props;
| return (
> <Grid container {...rest} className={classes.grid + " " + className}>
| {children}
|

> Build error occurred
Error: > Build failed because of webpack errors
at build


Solution

Additional comments

[Feature Request] node-sass vulnerability assessment

What is your enhancement?

This repo has multiple vulnerabilities due to node-sass package, detailed by Snky here: https://snyk.io/test/github/creativetimofficial/nextjs-material-kit. Since there is no recommended fix at this time, it may be wise to remove SASS dependencies for now and just include the compiled CSS.

[Bug] Unable to install dependencies

Version

1.2.0

Reproduction link

https://www.creative-tim.com

Operating System

Ubuntu 20.04 (WSL)

Device

Desktop

Browser & Version

npm 7.11.1

Steps to reproduce

Download the .zip package from Creative Tim website
Unzip the package
run npm install or npm install:clean

What is expected?

Install npm dependencies

What is actually happening?

npm is unable to resolve dependency tree:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"17.0.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.5.0" from [email protected]
npm ERR! node_modules/react-datetime
npm ERR!   react-datetime@"3.0.4" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Solution

I've used yarn to install dependencies (which shows the above described error as a simple warning), probably the issue could be fixed using --force with npm

Additional comments

[Bug] navbar modal/popup/dropdown displaying offscreen

Version

Latest version

Reproduction link

https://share.getcloudapp.com/GGuWz8bz

Operating System

Windows 64bit

Device

laptop

Browser & Version

Firefox Developer Edition 90.0b6 (64-bit)

Steps to reproduce

This is a UI issue. This videoclip demonstrates the steps to reproduce:

https://share.getcloudapp.com/GGuWz8bz

Alternatively,

  1. On first entry, click on "Examples" link in navbar
  2. Dismiss the popup/modal by clicking away
  3. Scroll down the page at least 1 screen height's distance
  4. Click on the "Examples" link again.

What is expected?

For the modal/popup to be displayed within the viewport

What is actually happening?

Its being displayed outside the viewport


Solution

Additional comments

Warning: Built-in CSS support is being disabled due to custom CSS configuration being detected.

  1. git clone repository
  2. yarn dev

Results in following output:

yarn run v1.22.4
$ next
[ wait ] starting the development server ...
[ info ] waiting on http://localhost:3000 ...
Warning: Built-in CSS support is being disabled due to custom CSS configuration being detected.
See here for more info: https://err.sh/next.js/built-in-css-disabled

[ ready ] compiled successfully - ready on http://localhost:3000

[Bug] altered header component color keeps jumping to original color value

Version

latest

Reproduction link

https://github.com/joelgrimberg/nextjs-demo-page

Operating System

Macos

Device

MBP

Browser & Version

Chrome 88 / Firefox Dev

Steps to reproduce

  1. change primaryColor # to lets say green
  2. add changeColorOnScroll ( changeColorOnScroll color: info)
  3. open page with Header Component
  4. it will show green header
  5. refresh page
  6. orignial color will be applied instead of green
  7. scroll down, to see that the color switches back to updated color (green)
  8. refresh page to see jumping it back to original color

What is expected?

color setting of porimaryColor from matierial-kit-react.js is always applied,
I use 'const primaryColor = '#009767'', so this should always be applied after a hard refresh.

What is actually happening?

after a refresh, the original color (created by Tim) is put back in place. restarting dev server does not change the fact.


Solution

I have no solution yet.

Additional comments

route changes

some times route URL changes not working(using a link) in HMR render building

[Bug] .MuiCheckbox-colorSecondary.Mui-checked:hover effect needs to be overwritten on checkbox/radio

Version

1.0.0

Reproduction link

https://github.com/creativetimofficial/nextjs-material-kit

Operating System

Windows 10

Device

Laptop

Browser & Version

Chrome 80.0.3987.132

Steps to reproduce

  1. git clone https://github.com/creativetimofficial/nextjs-material-kit.git
  2. npm install
  3. npm run dev

What is expected?

Hover mouse over checkbox, radio and you'll see the .MuiCheckbox-colorSecondary.Mui-checked:hover effect is using a color defined this defined theme

What is actually happening?

Hover mouse over checkbox, radio and you'll see the .MuiCheckbox-colorSecondary.Mui-checked:hover effect is using a color outside this defined theme


Solution

Additional comments

[Bug] hardcoded values of theme colors in assets/jss

Version

1.0.0

Reproduction link

https://github.com/creativetimofficial/nextjs-material-kit

Operating System

Windows 10

Device

Laptop

Browser & Version

Chrome 80.0.3987.132

Steps to reproduce

  1. git clone https://github.com/creativetimofficial/nextjs-material-kit.git
  2. npm install
  3. npm run dev
  4. change color such as primaryColor in assets/jss/nextjs-material-kit.js

What is expected?

All primaryColor's change for all components

What is actually happening?

Several components have hardcoded values for theme colors


Solution

Remove hardcoded values in jss/ directory and reference the variables

Additional comments

I'll try to put a commit against this today

[Bug] npm i Failed

Version

1.2.0

Reproduction link

https://github.com/creativetimofficial/nextjs-material-kit

Operating System

Windoes

Device

Windoes

Browser & Version

Chrome

Steps to reproduce

npm i

What is expected?

to install Properly

What is actually happening?

not installing


Solution

Additional comments

Arguments:
C:\Program Files\nodejs\node.exe C:\Users\iamth\AppData\Roaming\npm\node_modules\yarn\bin\yarn.js

PATH:
C:\Python\Python310\Scripts;C:\Python\Python310;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files\nodejs;C:\ProgramData\chocolatey\bin;C:\Program Files\Git\cmd;C:\HashiCorp\Vagrant\bin;C:\Program Files\PuTTY;C:\Python\python376\Scripts;C:\Python\python376;C:\Python\Python310\Scripts;C:\Python\Python310;C:\Users\iamth\AppData\Local\Microsoft\WindowsApps;C:\Users\iamth\AppData\Roaming\npm;C:\Users\iamth\AppData\Local\Programs\Microsoft VS Code\bin;C:\Bin;C:\Program Files\heroku\bin;

Yarn version:
1.22.17

Node version:
16.11.1

Platform:
win32 x64

Trace:
Error: https://registry.yarnpkg.com/@material-ui/icons/-/icons-4.11.2.tgz: ESOCKETTIMEDOUT
at ClientRequest. (C:\Users\iamth\AppData\Roaming\npm\node_modules\yarn\lib\cli.js:141510:19)
at Object.onceWrapper (node:events:509:28)
at ClientRequest.emit (node:events:390:28)
at TLSSocket.emitRequestTimeout (node:_http_client:763:9)
at Object.onceWrapper (node:events:509:28)
at TLSSocket.emit (node:events:402:35)
at TLSSocket.Socket._onTimeout (node:net:486:8)
at listOnTimeout (node:internal/timers:557:17)
at processTimers (node:internal/timers:500:7)

npm manifest:
{
"name": "next-material-kit",
"version": "1.2.0",
"description": "NextJS Version of Material Kit React by Creative Tim (https://creative-tim.com)",
"main": "index.js",
"scripts": {
"test": "echo "Error: no test specified" && exit 1",
"dev": "next",
"build": "next build",
"start": "next start",
"install:clean": "rm -rf node_modules/ && rm -rf package-lock.json && rm -rf .next/ && npm install && npm run dev"
},
"repository": {
"type": "git",
"url": "git+https://github.com/creativetimofficial/nextjs-material-kit.git"
},
"keywords": [
"next",
"nextjs",
"react",
"reactjs",
"npx",
"material",
"material-design",
"material-kit",
"material-kit-react",
"next-material-kit"
],
"author": "Creative Tim",
"license": "MIT",
"bugs": {
"url": "https://github.com/creativetimofficial/nextjs-material-kit/issues"
},
"homepage": "https://demos.creative-tim.com/nextjs-material-kit",
"dependencies": {
"@material-ui/core": "4.11.4",
"@material-ui/icons": "4.11.2",
"classnames": "2.3.1",
"moment": "2.29.1",
"next": "10.2.0",
"next-compose-plugins": "2.2.1",
"next-images": "1.7.0",
"nextjs-redirect": "5.0.2",
"node-sass": "5.0.0",
"nouislider": "15.1.0",
"path": "0.12.7",
"prop-types": "15.7.2",
"react": "17.0.2",
"react-datetime": "3.0.4",
"react-dom": "17.0.2",
"react

[Bug] Installing using `npm i` fails due to React/MUI mismatch

Version

1.2.1

Reproduction link

https://github.com/creativetimofficial/nextjs-material-kit

Operating System

macOS 12.6.2

Device

N/A

Browser & Version

N/A

Steps to reproduce

  1. Download source
  2. Run npm i as directed in setup instructions

What is expected?

I'd expect npm to install all the dependencies

What is actually happening?

Error:

npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"18.2.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || ^17.0.0" from @material-ui/[email protected]
npm ERR! node_modules/@material-ui/core
npm ERR!   @material-ui/core@"4.11.4" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /Users/nick/.npm/_logs/2023-02-15T16_44_47_907Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/nick/.npm/_logs/2023-02-15T16_44_47_907Z-debug-0.log

Solution

I think one solution is to use React 16, which is compatible with MUI 4, at least according to the error above. Not ideal. I don't really know how else to fix this. TBH, this sort of integration issue was one of the main reasons I was hoping to use a template like this…

Additional comments

I'm using NodeJS 18.14

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.