THIS PROJECT IS DEPRECATED! TRY THIS INSTEAD: https://github.com/koljakutschera/laststaticsitegenerator
Version: 1.2.4
Simple but powerful static site generator, starter or boilerplate.
Impression:
- Templating (Layouts, blocks, includes, macros, more)
- Template data layer (Access data in template or via ajax: global, per page, from all pages)
- Template helpers(moment.js, accounting.js)
- Modular less-stylesheets (Hot-reloading)(Autoprefixed)(Sourcemaps)
- Modular javascript (Sourcemaps)
- Auto image-optimization
- Sitemap-generator
- Autoreload
- Tunnel(expose localhost to public URL)
- Proxy
- PageSpeed Insights reporting
- Remove unused CSS
If you have not already installed nodejs and npm: https://nodejs.org/
If you have not already installed git: https://git-scm.com (Optional)
Install gulp-cli via Terminal.
npm install --g gulp-cli
Clone this repository via Terminal. Or just click on the download-button in the right corner...
git clone https://github.com/koljakutschera/yafbp && cd yafbp
Install dependencies via Terminal(Maybe sudo is needed).
npm install
You can configure the process-settings in /gulpfile.js:
Example: Default configuration
var config = {
source_dir : './source/',
build_dir : './build/',
statics_dir : 'statics/',
templates_dir : 'templates/',
data_dir : 'data/',
styles_dir : 'styles/',
scripts_dir : 'scripts/',
images_dir : 'images/',
connect_port : 8080,
proxy_port : 9090,
proxyAuth : '',
autoprefix : ["> 1%","last 4 versions"]
}In the project-directory start the development process via Terminal:
Hint: All commands starting with -- can be combined.
gulp
Or with minification for styles, scripts, images and html.
gulp --production
Or with removing all unused styles.
gulp --purify
Or with exposing localhost to public URL(See public development covered in the next section)
gulp --tunnel
Or with PageSpeed-Insights reports for all pages(could take a few minutes...)
gulp --production --tunnel --psi
When the process is running open the following url in your browser:
http://localhost:8080
When using --tunnel flag you can also access your project via temporary public URL. With this you can for example check your site with browserstack or send the link to your customer for live-testing.
Hint: On every process start you get a new temporary public URL. You can see it in terminal logs.
Example: See terminal logs for public URL
Exposing localhost:8080 via public URL: https://temorary123.eu.ngrok.io
In source/templates Nunjucks is used for templating with all its features like block inheritance(layouts), autoescaping, macros and more. Every(except for files starting with an _) .html file on the root-level of the directory is compiled to the build/ directory. Templates on the root-level are your "pages". Files in sub-directories are ignored, but can be included in root-templates via Nunjucks template-inheritance-system.
Info: The default directory structure is only a recommendation - feel free to delete everything and start from scratch.
Hint: Files starting with an _ will not compile. Use this for drafts etc.
Example: Simple layout
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8"/>
<title>{{ page.title }}</title>
{% block meta %}
{% endblock %}
<link rel="stylesheet" href="styles/core.css">
{% block styles %}
{% endblock %}
</head>
<body>
{% block body %}
{% endblock %}
<script type="text/javascript" src="scripts/core.js"></script>
{% block scripts %}
{% endblock %}
</body>
</html> Example: Simple page
---
title: Home
---
{% extends "layouts/basic.html" %}
{% block meta %}
<meta name="description" content="This is home.">
{% endblock %}
{% block styles %}
<link rel="stylesheet" href="styles/home.css">
{% endblock %}
{% block body %}
<h1>Welcome to: {{ global.siteUrl }}</h1>
<p>You are here: {{ page.title }}({{pages.index.path}})</p>
{% endblock %}
{% block scripts %}
<script type="text/javascript" src="scripts/home.js"></script>
{% endblock %}Result:
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8"/>
<title>Home</title>
<meta name="description" content="This is home.">
<link rel="stylesheet" href="styles/core.css">
<link rel="stylesheet" href="styles/home.css">
</head>
<body>
<h1>Welcome to: http://www.change-to-your-domain.de</h1>
<p>You are here: Home(index.html)</p>
<script type="text/javascript" src="scripts/core.js"></script>
<script type="text/javascript" src="scripts/home.js"></script>
</body>
</html> See https://mozilla.github.io/nunjucks/ for more.
You can use the following included helpers in your nunjucks templates and macros:
- moment.js - Parse, validate, manipulate, and display dates.
- accounting.js - number, money and currency formatting
Hint: You can add your own helpers to the global data object covered in the next section.
Example: Formating a date-string with moment.js
<span>{{moment("2017-09-20").locale('de').format('LL')}}</span>Result: Showing formatted German date
<span>20. September 2017</span>Example: Formating money with accounting.js
<span>{{ accounting.formatMoney(4999.99, "€", 2, ".", ",") }}</span>Result: Showing formatted money
<span>€4.999,99</span>In data/index.js you can define your own data-sets and export it to all your templates. Think about generating navigation from json or exposing data from a csv-files that is read via nodejs. Global data is accessible in templates via "global" variable. The data is also written to build/data.json for ajax-access.
Info: The default directory structure in data/ is only a recommendation - feel free to delete everything except for data/index.js and start from scratch.
Help: There is a helper-function in data/index.js to import node-modules un-cached. Use this if you always want fresh data on every file-change.
Hint: You can dump the global data with: {{ global | dump }}
Example: Export site-url to all templates.
var global = {
siteUrl : 'http://www.change-to-yourdomain.de' // Required for sitemap.xml - do not delete!
};
// Expose data to templates
module.exports = global;Example: Access site-url in page:
<h1>Welcome to: {{ global.siteUrl }}</h1>Result:
<h1>Welcome to: http://www.change-to-yourdomain.de</h1>You can also provide data directly to a page via YAML-Front-Matter at the top of root-templates. This data is accessible in the template via "page" variable.
Hint: You can dump the data of a page with: {{ page | dump }}
Example: YAML-Front-Matter at the top of a page:
---
title: Home
---
Example: Access YAML-Front-Matter from page in layout template:
<title>{{ page.title }}</title>Result:
<title>Home</title>All the data you have provided to all root-templates via YAML-Front-Matter is also accessible in all other templates via "pages"-variable. The data is also written to build/data.json for ajax-access. You can access data from another page by the name of the template without the .html extension.
Info: This gives you almost all possibilities you want from a static-page-generator.
Hint: You can dump the data of all pages with: {{ pages | dump }}
Example: Access data of another page in a page:
<h1>Every little page knows the path of the index-page: {{ pages.index.path }}</h1>Result:
<h1>Every little page knows the title of the index-page: index.html</h1>For our SEOs all .html files on the root-level of source/templates are indexed to the sitemap.xml-file in the build/ directory. Files starting with an _ are excluded.
In source/styles every(except for files starting with an _) .less file on the root-level of the directory is compiled to the build/styles/ directory. Files in sub-directories are ignored, but can be imported in root-stylesheets via less-imports.
For example and depending on your needs you can use one core.less file and import all stylesheets in it for single-page-apps. Or you can use the core.less file for shared styles and multiple other files for per-page styles in a multi-page setup.
Hot: Styles are hot-reloaded(See file-changes without reloading the browser);
Info: The default directory structure is only a recommendation - feel free to delete everything and start from scratch.
Hint: You can also pass options to less-imports. http://lesscss.org/
Example: Importing another stylesheet.
@import "tools/reset.less";See http://lesscss.org/ for more.
When writing less/css browser-prefixes are automatically added. You can configure browser-versions in /gulpfile.js
In source/scripts every(except for files starting with an _) .js-file on the root-level of the directory is compiled to the build/scripts/ directory. Files in sub-directories are ignored, but can be included in root-scripts via a special comment/directive.
Depending on your needs you can use one core.js file and require all libs and scripts in it for single-page-apps. Or you can use the core.js file for shared libraries and multiple other files for per-page scripts in a multi-page setup.
Info: The default directory structure is only a recommendation - feel free to delete everything and start from scratch.
Hint: Script including works recursively (files can include files that can include files, and so on)
Example: Importing another script.
//=require tools/log.jsSee https://www.npmjs.com/package/gulp-include for more.
In source/images every .jpg, .png, .gif and .svg file is compiled/optimized to the build/images/ directory.
The default directory structure is only a recommendation - feel free to delete everything and start from scratch.
In source/statics you can put fonts, media etc. Every file and directory is copied to the build/statics/ directory.
The proxy is listening on port: 9090. Use it for example if you cant access an api-endpoint via ajax because of Cross-Origin Resource Sharing (CORS).
Hint: You can add http-authentication to the proxy in /gulpfile.js
Example: Proxy usage with jQuery:
var proxy = 'http://localhost:9090/';
var endpoint = 'www.echojs.com/'; // change this to your api-endpoint.
$.getJSON(proxy + endpoint, function( data ) {
console.log(data)
});When the build process is started a file-watcher watches for file-changes and auto-reloads the browser every time you change a file. Sometimes on first start you have to do a manual reload because the process is faster than the browser.
Just look at the contents of the source/ directory. There are just a few example files that should be self-documenting.
If you want a more advanced example checkout: yafbp-example-blog
To start from scratch - You can delete everything in source/images/, source/scripts/, source/styles/, source/templates/ directories. In the data/ directory only /index.js is required. For scripts and styles remember that files on the root-level act as entry-points.
Feel free to configure anything in /gulpfile.js to your needs.
Please don't! Except for bugs. Iam not interested in extending this project with more crazy stuff to increase its complexity. If you want babel, react or your shiny whatever JS-Framework just fork this repo and put it in the source directory :P
Thank you to all funky developers listed in /package.json.
- V1.2.4: Write external source map files
- V1.2.3: Remove unused CSS with --purify command. See readme -> Usage
- V1.2.2: Optimized watchers for slow file-systems
- V1.2.1: Configuration added. See readme.md -> Configuration
- V1.2.0: Added PageSpeed Insights reporting feature. See readme.md -> Usage
- V1.1.0: Added Tunnel(expose localhost to public URL) feature. See readme.md
- V1.0.2: Global- and pages data objects are now nunjucks-globals so that they can be used in macros too. Cache optimized.
- V1.0.1: Added Template helpers(moment.js, accounting.js). See readme.md
- V1.0.0: Dropped SVGInjector for simplicity, Data-layer extended with global, page, pages variables, Added sitemap-generator, Simplify examples, Using _ in filenames for drafts, removed build/ from .gitignore
Linux: The system has a limit to how many files can be watched by a user. The following command increases the maximum amount of watches a user can have:
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p