Blog-engine-sac

Free and open static site generator, that reads your input files and outputs web pages. … Read more Blog-engine-sac

Free and open static site generator, that reads your input files and outputs web pages. My blog as an example[1]

Feature Overview

  • Index page for all posts and categories
  • Client side, ultra fast search
  • 100% lighthouse score, WCAG 2.1 compliant
  • Responsive design
  • Dark mode ready
  • Output files are minified
  • Post sources can be text markdown html and more
  • Post sources can be any valid URL or local file
  • Semi private posts with indexed: false
  • Translation ready
  • Works without JavaScript
  • Fast (250 files in less than 3 seconds) and cli based

Pro version

To support the project and have additional features consider the pro version. Open an issue[2] or chat[3] if interested. The pro version includes

  • Comment system
  • Web hosting and domain setup*
  • Help to set up and/or help to migrate from other CMS
  • 6 hours of custom feature development for the site or the engine
  • Issues have priority over free users’ issues
  • Ability to update blog content via simple file upload and/or git

*Included cost, if higher than 50€ a year the difference is added to the cost.

Cost: 600€ per site a year

Special Offer: 150€ for the first ten customers for the first year

How to use ?

Set up

  1. Download NodeJS 14+[4]
  2. npm i [email protected] -g

Set up with the template

  1. Copy template[5] and follow instructions in its readme

Set up manually

  1. Create a new project (folder)
  2. Create a valid package.json file with npm init for example
  3. Run npm i blog-engine-sac[6] (may require sudo and –unsafe-perm)
  4. add scripts inside package.json
  "scripts": {
    "sac": "node node_modules/blog-engine-sac/source/main.js inputFolder=."
  }
  1. follow instructions below to create required files
  2. npm run sac
  3. to view the results use a static file server

Create a new post

Create a new file in the folder source/. Supported file types:

  • text (.txt)
  • markdown (.md)
  • html (.html)
  • yaml (.yaml)
  • json (.json)
  • ini (.ini)
  • toml (.toml)

A markdown file is a normal text file with .md file extension. The name of the file is used as the name of the post.

Simple post

Create a file in source/. For example my-post.md[7] or my-post.txt.

Post with metadata

Create a simple post then create a meta file with the same base name. For example my-post.yaml. Meta files in the readme will be yaml, but they can be any format in the list:

  • yaml
  • json
  • ini
  • toml
title: I am about to write a title
lang: en
author: Author name
ready: true
indexed: true
editLink: false
standalone: false
creationDate: 2018/02/15
modifiedDate: 2035/02/19
tags:
  - cooking
  - sports
  - travel
translations: []
license: CC0-1.0
ready

set ready to false to not process them at all

indexed

set indexed to false, to have it in the blog, but the index.html will not have a link to it. The only way to open it would be to know the exact URL.

tags

tags is a list of categories that your post will appear in. Categories are pages that list only post of that category. For example if you have “travel” inside categories inside blog-engine-sac settings, and travel as a tag of the post, then the post will be listed on the travel category. tags that are not in the categories will create a semi hidden category : a link from post to that category but unlisted on the index page.

translations

Use it to mark posts as translations of another post. If we have the following files:

  • Geography.md (in English)
  • Géographie.md (in French)
  • Erdkunde.md (in German)

Use the following meta file to link them:

Geography.yaml
lang: en
translations:
  - lang: fr
    src: ./Géographie.md
  - lang: de
    src: ./Erdkunde.md

Each translation item may use any key value pair seen above (title, author, etc)

editLink

Should be a url or false. If it is an url, an edit link will be created for that post

standalone

If true the html output will not be decorated by the usual (header, footer, next, previous, etc)

External post

Create a file that describes where to find the external post. For example js-style-guide.yaml . Including a post from the web: Add a yaml file in source/ with src set to the url.

js-style-guide.yaml
src: 'https://raw.githubusercontent.com/GrosSacASac/JavaScript-Set-Up/master/js/red-javascript-style-guide/readme.md'

Another Example with this readme file:

blog-engine-sac-readme.yaml
src: 'https://gitlab.com/GrosSacASac/blog-engine-z/-/raw/master/README.md'
canonicalUrl: 'https://gitlab.com/GrosSacASac/blog-engine-z/-/blob/master/README.md'
lang: en
Content-Type: text/markdown

site settings

Create file blog-engine-sac.yaml with

defaultLang: en
defaultAuthor: AUTHOR
mainTitle: Blog
subTitle: Change title and subtitle in blog-engine-sac.yaml
defaultLicense: CC-BY-NC-4.0
htmlExtensionLinks: false
indexInBaseIndexLink: false # index link becomes just /
categories:
  - tag: travel
    "fr": voyages
  - tag: dance
    "fr": danse
    

Ideally defaultLicense is a SPDX identifier[8].

defaultLang is a 2 letter shorthand for the language[9] (ISO 639-1).

htmlExtensionLinks: If true, links will have the “.html” extension. Default is false.

Change the values as you see fit.

categories

categories are provided by the user as an array for the entire blog

for example: travel, cuisine, sports

Each category will have a dedicated index page that acts like the main index page but only lists post of that category. Posts will be in that category if they have a corresponding tag.

about page

Create file source/extras/about.md.

contact page

Create file source/extras/contact.md.

footer

Create file source/extras/footer.md.

Edit Images

Open folder images Replace the images with new ones but keep the exact filename to not break the links. (Images are linked from other files, not copied, the name of the files are used)

Required images

  • images/about.jpg
  • images/contact.jpg
  • images/home.jpg
  • images/post.jpg

Custom css

Add the following key-value pair in your site settings.

customCss: custom.css

Then create a folder named css. Inside create a file custom.css. Then copy inside custom.css the first 2 rules found inside blog-engine-sac.css[10]. These are some css variables easy to edit as a starting point.

user provided tags

found in the meta file as an array

auto generated tags (disabled)

are gathered from the plain text of each post based on heuristics (rarity and uniqueness)

tags

tags is a set that combines user provided tags and auto generated tags and title. It is used for search function. They are also displayed after the post.

What is mark down

A text format. Learn it here https://commonmark.org/help/[11]

About the code

Don’t remove, edit or add any other file unless you know exactly what you are doing!

HTML files

are generated. Do not edit directly

About

Design starting point

Start Bootstrap – Clean Blog[12] is a stylish, responsive blog theme for Bootstrap[13] created by Start Bootstrap[14]. This theme features a blog homepage, about page, contact page, and an example post page along with a working PHP contact form.

Changelog[15]

Copyright and License

CC0[16] (Only for blog-engine-sac itself)

References

  1. ^ My blog as an example (letz.social)
  2. ^ Open an issue (gitlab.com)
  3. ^ chat (miaou.dystroy.org)
  4. ^ Download NodeJS 14+ (nodejs.org)
  5. ^ Copy template (gitlab.com)
  6. ^ npm i blog-engine-sac (www.npmjs.com)
  7. ^ my-post.md (my-post.md)
  8. ^ SPDX identifier (spdx.org)
  9. ^ 2 letter shorthand for the language (en.wikipedia.org)
  10. ^ found inside blog-engine-sac.css (gitlab.com)
  11. ^ https://commonmark.org/help/ (commonmark.org)
  12. ^ Start Bootstrap – Clean Blog (startbootstrap.com)
  13. ^ Bootstrap (getbootstrap.com)
  14. ^ Start Bootstrap (startbootstrap.com)
  15. ^ Changelog (gitlab.com)
  16. ^ CC0 (letz.social)


Source: Echo Js


Categories: Development, Software


Leave a Reply

Your email address will not be published. Required fields are marked *