Comment on page

Folder structure

Site source is well structured.
Spignite expects a certain directory structure. The structure is part of the defaults and can be easily modified. The defaults exist only to speed up the initial project setup.
├── out/
├── src/
│ ├── config/
│ ├── css/
│ ├── data/
│ ├── images/
│ ├── js/
│ ├── layouts/
│ ├── site/
│ └── static/
├── package.json
└── spig.mjs
These folders are used by default Spignite operations. If you wish, you can use whatever structure you like with your own operations.
Let's see what these folders are for.


The resulting website will be created here. Note that Spignite does not clear this folder on the build! During the development, files can be accumulated while you are working on the website. Make sure you clean this folder before the deployment.


The root folder for the whole website content, including a few global configuration files.


Additional configuration of used 3rd party tools. For example, you can define here additional nunjucks filters, tweak parameters for minimization, etc.


Process all *.sass files with the SASS compiler. Process all *.css files with precss-alike operator.


Put any number of data *.json files here. Spginite will read them and make them available within the site context.
Data files are usually used for the generation of data-driven sites. For example, data can be a list of books and their authors. Or a conference schedule, with talks and speakers information.


Put all the images that you might want to process: either resize to fit certain width or height or just optimize.
Please note that image operations are lengthy and require more processor power. It is advisable to prepare all images before site processing.


Home of all websites JavaSript files.
Spignite has a concept of javascript bundles. When a folder is named as *.js - all its JavaScripts will be merged into one output file named as a folder. JavaScript bundles are cool for splitting large javascript files into small ones for development.


The root for page layouts.


The site's content; usually written in Markdown. Spignite supports any renderer engine so that you can write content in e.g., Nunjucks, too - helpful on complex pages.
You can mix various content types.
This folder may contain additional resources, like images.


Files that will be blindly copied to the output.


The Spignite website definition. While defaults are not mandatory, it is advisable to have them enabled.
const { Spig } = require('spignite');
// user operations;