Need help with gopablo?
Click the β€œchat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

164 Stars 15 Forks MIT License 198 Commits 0 Opened issues


🐺 Static site generator.

Services available


Need anything else?

Contributors list

# 27,021
195 commits
# 690,824
1 commit


Version Dependencies

GoPablo a static site generator.


Initialize GoPablo

npx gopablo

Run development mode

Build and open your browser to http://localhost:3000.

npm run dev

Build distribution files for production

npm run prod

Ready to deploy πŸš€


| Information | Discord | Donate | |:------------|:---------|:-------| | GoPablo is a static site generator with a modern development workflow, integrated web server, auto-reload, CSS preprocessors, and ES6 ready.| Discord server | BuyMeACoffee |


|πŸ‘‡|Includes| |:-:|:---| |πŸ“¦| Live Server| |πŸ”₯| Hot Reload & CSS Injection| |βš™| Babel 7| |πŸ€–| Express Server| |πŸŽ’| Code Minification| |🌈| Image Compression| |πŸ•Έ| Templating & Partial HTML Injection| |🎨| PostCSS & Next Generation CSS| |πŸ’| Cherry Design System| |βœ‚οΈ| Cache-Busting| |πŸ›Ž| Distribution Files|

1. Installing Node.js

GoPablo requires Node.js v12+. This is the only global dependency. You can download Node.js here.

Node.js is a JavaScript runtime built on Chrome’s V8 JavaScript engine. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient. Node.js’ package ecosystem, npm, is the largest ecosystem of open source libraries in the world.

2. Set Up Project

File Structure

    β”œβ”€β”€ build/                   # Build files
    β”œβ”€β”€ dist/                    # Distribution files
    β”œβ”€β”€ src/                     # Source files
    β”‚   β”œβ”€β”€ assets/              # Assets directory
    β”‚       β”œβ”€β”€ css/             # CSS files
    β”‚       β”œβ”€β”€ fonts/           # Fonts directory
    β”‚       β”œβ”€β”€ img/             # Image directory
    β”‚       β”œβ”€β”€ js/              # JavaScript files
    β”‚   β”œβ”€β”€ etc/                 # Extra files
    β”‚   β”œβ”€β”€ includes/            # HTML template partials
    β”‚   β”œβ”€β”€ index.html           # Index page
    └── .babelrc                 # Babel configuration
    └── .gitignore               # Git ignored files
    └── .editorconfig            # Editor code styles
    └── .stylelintrc             # Stylelint configuration
    └── gulpfile.js              # Gulp configuration
    └── LICENSE                  # License agreements
    └── package-lock.json        # Packages lock file
    └── package.json             # Node.js packages
    └──                # You are reading this
    └── server.js                # Express server

Install GoPablo from NPM

To install GoPablo create a directory for the new website and from there run the command to generate the file structure: ``` npx gopablo

That's it 🍾 easy as that. Now start the development workflow: [Start Workflow](#start-workflow)

Install GoPablo from Repository

To install GoPablo you need to clone the repository from GitHub:

git clone ```

  • This will clone the repository on your local machine. Navigate to the newly created directory.

  • Replace the file:

    and continue with the dependency installation.


npm install

Start Workflow

  • To start the development server run the command:
    npm run dev
  • You are ready to go! Happy coding! πŸ€“

Generate production files

To generate your distribution files run the command:

npm run prod
The files will be generated in the

Templating and HTML Partials

To avoid repetitive HTML code, GoPablo uses gulp-file-include. It has a simple templating synthax and allows to re-use chunks of code written in separate files. These partials are located in the directory:

For more information check out their documentation and examples:

New pages

To create new pages, simply create new .html files in the


3. CSS, PostCSS and Sass


By default GoPablo supports PostCSS, a similar preprocessor to Sass, Less and others but with more functionality. On top of that PostCSS is 3x faster than Sass and 4x faster than Less. Features come in the shape of PostCSS plugins. Think of these like using Lego, where each piece is a different feature that can transform your CSS in some way. PostCSS lets you stick these pieces together so that you can build up your own feature set, adding and removing plugins as and when you need them. postcss-preset-env is installed by default. Read more about PostCSS here.


GoPablo has two different sets of PostCSS plugins - one for the development environment (pluginsListDev) and one for the production task (pluginsListProd).

/* -------------------------------------------------------------------------------------------------
PostCSS Plugins
 ------------------------------------------------------------------------------------------------- */
const pluginsDev = [
        stage: 0,
        features: {
            'nesting-rules': true,
            'color-mod-function': true,
            'custom-media': true,
const pluginsProd = [
        stage: 0,
        features: {
            'nesting-rules': true,
            'color-mod-function': true,
            'custom-media': true,
        preset: [
                discardComments: true,


The starting point for CSS is the file:



Cherry is a minimal CSS framework that helps you organize your work from design to implementation.


GoPablo is super flexible. You can install Sass and use it as the main CSS preprocessor:

npm install gulp-sass --save-dev

Include Sass in gulpfile.js:

const sass = require('gulp-sass');

Change the gulp tasks stylesDev to:

function stylesDev() {
    return src('./src/assets/css/styles.scss')
        .pipe(sass({includePaths: 'node_modules'}).on('error', sass.logError))
        .pipe({ match: '**/*.css' }));

Also the watch task has to be changed in order to watch for .scss filetypes:

watch('./src/assets/css/**/*.scss', stylesDev);

Change the gulp tasks styleProd to:

function stylesProd() {
    return src('./src/assets/css/styles.scss')
        .pipe(sass({includePaths: 'node_modules'}).on('error', sass.logError))

4. Images and Fonts


It is recommended to store image assets in the directory:


In the production build SVGs and other image assets will go through a minification process.


Fonts are always special. Your fonts should be stored in:


Then you can include them in your CSS:

@font-face {
    font-family: 'Helvetica Neue Thin';
    src: url('./fonts/Helvetica-Neue-Thin.eot');
    src: url('./fonts/Helvetica-Neue-Thin.eot') format('eot'),
    url('./fonts/Helvetica-Neue-Thin.woff2') format('woff2'),
    url('./fonts/Helvetica-Neue-Thin.woff') format('woff'),
    url('./fonts/Helvetica-Neue-Thin.ttf') format('truetype'),
    url('./fonts/Helvetica-Neue-Thin.svg') format('svg');

5. JavaScript ES6

GoPablo supports ES6 JavaScript with Babel. Babel has support for the latest version of JavaScript through syntax transformers. These plugins allow you to use new syntax, right now without waiting for browser support.

Write ES6 JavaScript

Your JavaScript code should be located in:


GoPablo will watch for changes under the js directory and bundle the code in a single file, which will be included in the footer of the page as:


Check the gulp configuration to learn more about how JavaScript is generated.

6. External Libraries

Including external JavaScript libraries is as simple as installing the npm script and including it in the gulpfile.js

/* -------------------------------------------------------------------------------------------------
Header & Footer JavaScript Boundles
-------------------------------------------------------------------------------------------------- */
const headerJS = [
const footerJS = [

You can include the scripts in the head of the page before the DOM is loaded by placing them in the headerJS array or in the footer of the page after the DOM is loaded in the footerJS array. Only footer scripts are processed with Babel thus supporting ES6, however you can change this in the configuration if you want to run both header and footer scripts with Babel.

A build restart is required for changes to take effect.

7. Code Style Rules

GoPablo comes with its own set of code style rules:


Lint CSS

Before pushing changes make sure you have clean and consistent CSS. Run stylelint with the command:

npm run lint

8. Deploy

There are a lot of possiblities and different ways to deploy your static website. The most traditional one being: generating your distribution files and uploading them manually, usually FTP.


With the help of a simple Express server, with GoPablo we can deploy to heroku out of the box.

  1. Create Heroku application:
    heroku create
  2. Push the branch to Heroku origins:
    git push heroku master

Automated Netlify deployments

Netlify is a great service that can be used to deploy generated websites. All you have to do is:

  1. Connect your GitHub repository.
  2. Choose Branch to deploy, usually:
  3. Set the Build command to:
    npm run prod
  4. Set the Publish directory to:

We are live 🌍

9. Audit and Page Speed

|audit|page-speed| |:-:|:---|

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.