AkhilChoubey / 30DaysOfJavaScript

Projects made during the 30 days of the JavaScript challenge

Home Page:https://30daysofjs.netlify.app

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Repo containing all the projects made in 30 Days while completing the 30 Days of JavaScript Challenge.

View Live Demo

30daysofjs.netlify.app

Drum Kit

Clock

Random Color Generator

Digital Clock

Random Password Generator

Calendar

Dynamic Form Field

Number Counter

Dice Roll

Emoji Switcher

Color Picker

Custom QR Code

Favicon Fetcher

Visit Counter

Joke Generator

Countdown Timer

Text Speed Control

Stopwatch

Traffic Lights

Levitate Board

Wave Effect

Zoom Effect

Drawing Pad

Word Counter

Weather App

Calculator

Memory Matching Game

Music Player

To Do List

Tic Tac Toe

Pop the Ballons

Key Code

Feedback UI

Virtual Piano

Decimal To Binary

Hangman

RPS Game

Snake Game

Age Calculator

Gradient Generator

Basic Images Carousel

Simple Form Validation

Getting Started with APIs

Infinite Scroll

How to setup for development

Since we are using TailwindCSS, there are different ways to set it up in order to start working with this tool. However, we found it easier to star with minimum configuration boiler plate to focus on the development. So, these are the simple steps to start working with TailwindCSS in the project.

  1. Install NodeJs, just go to the official site and download the package for your operative system. We recommend using the LTS version.
  2. Clone this repo using git clone git@github.com:alexventuraio/30DaysOfJavaScript.git.
  3. Go to the root folder with cd 30DaysOfJavaScript.
  4. We have the minimum configuration for TailwindCSS to work properly but feel free to modify it on the config file tailwind.config.js.
  5. Since, TailwindCSS has its own CLI, we are going to use it to purge the classes we are not using from Tailwind and the JIT compiler to create our final CSS file in order to have a small file size containing only the classes we are using in the HTML. In the package.json file we have a custom command to start with, just run yarn run dev or npm run dev and you'll be ready to start working on the site.
  6. Finally, you can start a live server to serve the site or just open it up manually (index.html) on the browser.

Prepare for Production

We can deliver the final tailwind.css file to production and it will work but that is not the best practice to just leave it as for development mode. So, we are going to minify it in order to have a smaller file size and be more appropriated for production.

  1. Stop any other command that you have using ctrl + c.
  2. We have a package.json file with two commands that use the Tailwind CLI, one of them is to minify our assets/tailwind.css file, so the only thing you need to do is to run yanr run build or npm run build. This will go over the custom CSS file generated with the required classes for our project and prepare it for production.

Note: Running the last command to minify for production is quire important for performance reasons. Note: You must run it before pushing to master to always have a ready-for-production version.

License

This project follows the MIT License.

Made with ♥ by Swapnil Srivastava

forthebadge

github linkedin

About

Projects made during the 30 days of the JavaScript challenge

https://30daysofjs.netlify.app

License:MIT License


Languages

Language:HTML 98.5%Language:JavaScript 1.5%