Solution Setup – Front-End stack – Part 2

Previously published on Episerver Dispatch

By Eric St-Pierre , March 25, 2020

This article is part of the Solution setup series.

“How to setup a project” is a series about the basic tools and configurations that can be used into starting a new development project. 

This is the second article on a discussion about CSS frameworks.  In the first article of this series, I discussed what is a CSS framework and how to use it to speed-up an Episerver site development.  In this article, I’ll cover how to implement TailwindCSS in an Episerver solution.

I have chosen to go with an utility-class CSS framework because I wanted to see how this kind of framework pattern could help change the editor experience, and how we can give editors more freedom in building their website.

covering the bases

To be able to use a CSS framework, we need to include the bases of the framework in the project and have some ways to customize it to meet our project requirements.

If you are doing a small proof of concept or a demo that don’t require style customization, you could include TailwindCSS directly from a CDN, as documented on the TailwindCSS site. This would prevent you from having to include front-end file processing into your project.

To include the CDN version of TailwindCSS, you would need to add the following link into the tag of your pages.


If you need to customize the styles provided by the framework and you would want to include TailwindCSS in an actual project, then you are better off including TailwindCSS as a project dependency, and develop a packaging pipeline. To do so, we need to know how to include TailwindCSS in a project and how to make it production ready.


There is a great video on how to include TailwindCSS into a project available on their site.

Following are the steps covered into the video to install TailwindCSS into an empty project.

Since TailwindCSS is an npm package, we will need nodejs and NPM installed in the development environment. Once nodejs and npm are installed, we need to install the TailwindCSS package and dependencies in the package.json configuration file.

The dependencies we would like to install would be:

  • Postcss-cli, which is a client interface to PostCSS, which is “a tool for transforming CSS with JavaScript”
  • Autoprefixer, which is ” a PostCSS plugin to add vendor prefixes to CSS rules using values from Can I Use.”

Adding TailwindCSS and it’s dependencies can be done with the following command

npm install tailwindcss postcss-cli autoprefixer

Then, we need to create an empty tailwindcss configuration file.  This can be done with the following command.

npx tailwind init

Next, let’s create a PostCSS config file.  Create an empty postcss.config.js at the root of your project to specifies which PostCSS plugins we are going to include in the processing pipeline.

module.exports = {
  plugins: [require('tailwindcss'), require('autoprefixer')]

We then create a css/tainwindcss.css file, in which we tell tailwind which tailwindcss base classes we want to use in our project

@tailwind base;
@tailwind components;
@tailwind utilities;
  • Base is the base tailwind styles. 
  • Components is the Tailwind components. 
  • Utilities are the tailwind utilities classes.

Then we need to create a script to actually process all of this with PostCSS.  Let’s use the package.config to add a build script command

"scripts": {
    "build": "postcss css/tailwind.css -o public/build/tailwind.css"

Once this is done, we can run it using the npm command run

Npm run build

Running this script will generated a PostCSS processed file in the public/build folder


So this was more of a manual approach.  To add it into an Episerver solution, we would like to include the processing of the file in our build process. To do that, we could use the npm script and include it as a build step.  Other options would be to use a task-runner or a packaging tool.

One of the most used task runner would be gulp.  From Gulp official site

“Gulp is a toolkit for automating painful or time-consuming tasks in your development workflow, so you can stop messing around and build something.”

To use Gulp, we would need to create a Gulp task, in which we would add tailwindcss to the list of plugins passed to gulp-postcss:

gulp.task('css', function () {
  const postcss = require('gulp-postcss');
  return (
      // ...
          // ...
          // ...
      // ...

For the packaging tool, webpack could be a good option.

From their documentation site, webpack is

“At its core, webpack is a static module bundler for modern JavaScript applications. When webpack processes your application, it internally builds a dependency graph which maps every module your project needs and generates one or more bundles.” > webpack - dependency graph

PostCSS is already included with webpack, so you would need to add tailwindcss as a plugin in your postcss.config.js file:

module.exports = {
  plugins: [
    // ...
    // ...

…or include it directly in your postcss-loader configuration in your webpack.config.js file:

// webpack.config.js
module.exports = {
  // ...
  module: {
    rules: [
        // ...
        use: [
          // ...
            loader: 'postcss-loader',
            options: {
              ident: 'postcss',
              plugins: [require('tailwindcss'), require('autoprefixer')]

The choice would depend on the front-end stack you already have in place.


To add a build task to your Episerver project, you need to have the “Task Runner Explorer” plugin installed. 

You can also install specific task runner for Webpack or for NPM. Once those extensions are installed, you can specify which action to perform when you build the project. As an example, you could specify to run an NPM build task, on the BeforeBuild event. On the task runner explorer, you would add the command run build:dev to the BeforeBuild event.


Whatever path you choose to take, one last thing to think about would be to optimize you framework code so that you include into your production the smallest foot-print. 

From the PurgeCSS site

“PurgeCSS is a tool to remove unused CSS. It can be part of your development workflow.

When you are building a website, you might decide to use a CSS framework like TailwindCSS, Bootstrap, MaterializeCSS, Foundation, etc… But you will only use a small set of the framework, and a lot of unused CSS styles will be included.

This is where PurgeCSS comes into play. PurgeCSS analyzes your content and your css files. Then it matches the selectors used in your files with the one in your content files. It removes unused selectors from your css, resulting in smaller css files.”

Depending on the packaging tool you use, the configuration would be the following, PostCSS, Webpack or Gulp.

There is a great screencast on the TailwindCSS site that can help you to setup PurgeCSS for TailwindCSS

In this article, I went discussed the benefits of using a CSS framework and went thru the steps to include one such framework into an Episerver project.  In the next article of this series, I’ll go into how we can use TailwindCSS to improve the content editor experience.