When you are going to build a new web site, most of times you go through it thinking about the technology you'll use to build it. Maybe you want to be on the cutting edge and you'll use the latest or rarest content management system like Ghost or maybe you'll use a wide extended system and full of available plugins (I've a mention about these later) like Wordpress.
But only a few times we think about what we really want and what we really need.
Sometimes you're creating a new site that the content will not be much updated. The reason to choose one technology or another could be a client requirement but some of them also need external help to add or update the content, and many many times, his issues will be about changing themes or layouts and the professional help is a must.
This don't apply to everybody, but I'm sure that sometimes is like this.
You need to install a bunch of plugins to get what you really want, and maybe is useful for people without the technology knowledge but sometimes, this plugin will be an additional load for your site.
Advantages of a static web site.
A CMS needs to process the http request, then query the data to the database or external APIs and finally return all the stuff passing through the filters and plugins you could have installed. In the other hand, the static site only takes care of the first part of this sequence. A static site will respond to an http request with his static resources and sometimes will use calls to externals APIS.
After that, both send the information to the browser or http client and will be processed in the client to show what was required. Both kind of sites could take advantatge of the benefits of serving external assets from CDN repositories but ...
Finally this is translated in two important factors for the users expectations: security and speed. With a static site there is no need about managing security and user permissions, what is served from the server are static resources and there is no need to protect it if you are building a public site.
How to build static web site.
Building a static site isn't about time travel and use technology of 10 years ago.
You can be in the wave of newer technologies like Node.js, Grunt, Gulp, Sass, Handlebars and all the mess of npm and bower packages ... and build fantastic static web sites and getting fun at the same time.
There are many options out there, but I tell which one
I use. A framework that provides all together all the technologies I need: Zurb Foundation in the 6th version.
You can refer to the documentation to see all options and possibilities to install and use the framework but I will provide a quick use guide
Foundation 6 for sites: quick use guide
- You have to install Node.js v0.12 or above. Refer to Node.js documentation for your OS https://nodejs.org/en/download/
- Once you have installed Node.js you have to install gulp and bower globally executing with sudo if you are in Linux environment
sudo npm install -g gulp bower
- Git installed is also a requirement https://git-scm.com/downloads
Build the site template
- Install the foundation-cli globally that will help you through the process to create a new site each time you need it (also with sudo if you are in Linux environment)
sudo npm install -g foundation-cli
- Create a working folder to set as your project development folder. Open a command line there or change to the working directory.
- Execute the command
foundation newto generate a new site with the cli in the working directory.
- The assistant will ask you for 3 questions:
- The type of project you're building that is A web site and this will use the Foundation for Sites framework,
- the project name,
- and the template to generate the site skeleton.
I suggest to use the ZURB Template to use a set of tools that make the site development easier to structure content and modularize the components. These tools are basically the Handlebars template system, that allows you to structure the HTML in a set of source files and the Sass compiler to generate a resultant css from the source files with the help of some functions to manipulate the css generated and a modularized style of components.
? What are you building today? (Use arrow keys) ❯ A website (Foundation for Sites) A web app (Foundation for Apps) An email (Foundation for Emails)
? What's the project called? (no spaces) myproject
? Which template would you like to use? Basic Template: includes a Sass compiler ❯ ZURB Template: includes Handlebars templates and Sass/JS compilers
Finally we got a message thanking you to use the framework
. /| , , /|/ \/| /| Thanks for using ZURB Foundation for Sites! /|/ |/ | ------------------------------------------- |___| |___| Let's set up a new project. \___| ^^ ^^ |___/ It shouldn't take more than a minute. | -[O]--[O]- | | ___, | | ... | \_ _ _ _ _ / Downloading the project template... Done downloading! Installing dependencies...
And after the downloaded dependencies required to build the project it will show something like
You're all set! ✓ New project folder created. ✓ Node modules installed. ✓ Bower components installed. Now run foundation watch while inside the myproject folder.
What we got, and what is each of these folders?
. ├── bower_components │ ├── foundation-sites │ ├── jquery │ ├── motion-ui │ └── what-input │ ├── bower.json ├── CHANGELOG.md ├── config.yml ├── etc ├── gulpfile.babel.js ├── node_modules │ ├── package.json ├── readme.md └── src ├── assets │ ├── img │ ├── js │ │ └── app.js │ └── scss │ ├── app.scss │ ├── components │ └── _settings.scss ├── data ├── layouts │ └── default.html ├── pages │ └── index.html ├── partials └── styleguide ├── index.md └── template.html
- bower_components and bower.json You should install your bower dependencies in the root directory of your project. Here you can install things like Font-Awesome, Moment or D3 In the *bowercomponents* folder there are the basic dependencies of the Zurb Foundation framework like jQUery
- node_modules folder contain the Node.js dependencies of the framework needed to generate the final files and folders to distribute as the site and package.json is the definition for Node.js packages for the current site.
- gulpfile.babel.js is the definition of the gulp taks running the project. These tasks will use the configuration from the YAML file config.yml
- readme.md A basic definition of how the project and the foundation cli rules.
- src folder content are the fundamental elements of your site. Here is where you'll change things and generate the content of your website.
- img The folder to contain the image resources of your project
- scss It's containing the source files for all your custom styles as sass source files.
- layouts containing default.html which is the template for the general layout of the project in the Handlebars flavour
- partials Any piece of html (Handlebars) you reuse in many pages could go here in order to be accessible for any page.
- pages Each one of the pages in your site. Here you can set the folder and section structure you prefer. Also in Handlebars format.
- styleguide Is a content example using the defined styles as a showcase of the basic html components
Run, change and review the result.
You can run your project in a live server. This means that it will start a web server and will be listening to the changes in your project files like scss source files or html templates.
This is the command
Once you have a statisfactory result you can generate the final files to upload to your production web server. These are the same content than the generated during the development but optimized to get a higher performance in the real life and use.
foundation build generates a dist folder containing the final result of your project.
You can run
npm update -g foundation-cli to update the Foundation client.
Or if you want to update the package dependencies like the bower dependencies in your project you can run the command