Atlas Template

Thank you for buying this template! We hope you can use it to make your next web project a success!

Atlas is a premium template styled with TailwindCSS. Other open source libraries were also used to provide the functionality required to make your customization quicker and faster.

• Alpine.js: A Vue-inspired jQuery alternative that offers you the reactive and declarative nature of big frameworks at a much lower cost.
• Boxicons: A simple vector icons set carefully crafted for designers and developers to use in your next project.
• Highlight.js: A popular code syntax highlight library, we're also using the "Atom Dark" theme for it.

We’re also using some Tailwind plugins to extend our config and available classes:

• TailwindCSS Forms: This is the official plugin for globally styling form fields, we have added some custom styles too.
• TailwindCSS Typography: Official TailwindCSS plugin for styling user-generated content.

Development Workflow

NPM is used for compilation of scripts as well as live reloading when changes are made.

You will need to run npm install or yarn before starting to work on with the templates.

Important note: You need Node version 12.13 or higher as per TailwindCSS' requirements

Two NPM tasks have been configured to help with your development: -npm run develop - This runs the development tasks, compiles and listens to changes in the assets/styles folder and lastly, activates a BrowserSync server for live reloading.

• npm run build - This will be used to build your JavaScript/CSS and make them ready for production. It also activates PurgeCSS which is used to remove unused CSS classes from your project, providing a smaller bundle size to ensure that your website loads faster.

As always, we recommend you read the official TailwindCSS docs, they’re the best way to learn Tailwind at the moment.

Project Structure

The project uses a mostly flat structure with a key folders and files:

• assets folder: This is where all of the projects styles, javascript, fonts (if any) and images live, each on their own folder for better organization. - One thing to keep in mind if that if you want to use the project as is and decide to rename the styles folder, be sure to update the css NPM script with the new name.
• browser-sync-config.js: Pretty self-explanatory, this is the config that BrowserSync uses when we launch our live reload server. Here are the options docs in case you want to customize it.
• package.json: Where our dependencies, browserlist config and NPM scripts live. - Note: Since we mainly use yarn for our local development, you’ll also see a yarn.lock file on the project.
• postcss.config.js: This is where the styling magic happens, here you can add any postCSS plugin that you fancy, we’re currently only using these at the moment: - TailwindCSS: obviously - postcss-nested: To mimic SCSS nesting - autoprefixer: To support old browsers - postcss-clean: To minify our CSS on production
• tailwind.config.js: The project’s tailwind config, here you will find our custom classes and tailwind plugin’s config.

Everything else are the HTML templates.

The Tailwind Config

Each of our projects make use of extend as much as possible for our tailwind config, but we do override some fo the defaults, like the following:

• fontFamily: We tend to add our our fonts here and only use those
• screens: We actually add a smaller xs screen for 375px widths, we think it helps us test for mobile better and we still use the default classes.
• colors: We typically only use our project’s colors and discard the defaults

How to keep the defaults and our new classes

If you want to keep the default and still use our classes, you just need to move the property you want to change to the inside of extend, here’s an example:

Let’s say you want to keep the fontFamily classes Tailwind has, here’s how you could change the config to make it happen:

Original

// tailwind.config.js
module.exports = {
	...
	theme: {
	        fontFamily: {
	            body: ["Poppins", "sans-serif"]
	        },
	}
	...
}

Keep the Tailwind defaults

// tailwind.config.js
module.exports = {
	...
	theme: {

	},
	extend: {
			fontFamily: {
	            body: ["Poppins", "sans-serif"]
	        },
	}
	...
}

That’s it, next time you compile, you’ll have the font-sans, font-serif and font-mono classes available.

Why we used Alpine.js

We debated a lot on what to use for our first templates since we wanted to start with HTML versions of our designs. The standard that you’ll see all over ThemeForest is jQuery but we think this is a subpar choice for the kind of developer that uses TailwindCSS.

We also thought about using Vue but in practice we found it a bit verbose and a bit limiting because, since we wanted to keep everything in pure HTML, we couldn’t use Vue components.

We opted to try Alpine.js and we think it’s like using the best of Vue, like its syntax and reactivity, without its baggage, like the virtual DOM, which would be overkill for a project like this.