SSG is a Static Site Generator that is only a Static Site Generator. No resumes here! Just a piece of code that generates static files from templates for websites, and can do it live while you develop said templates.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Zed A. Shaw 502fc83b1b It will now watch the static directory as well and do the sync operation when that changes. 3 weeks ago
art Create a funny parody logo. 4 weeks ago
config Added a sync_dir option to the config so you can have a static directory that gets synced. WARNING: The Go default CopyFS won't copy files to targets that exist so I have to remove the target to do the sync. 3 weeks ago
example It will now watch the static directory as well and do the sync operation when that changes. 3 weeks ago
tests Initial setup of the project directory. 4 weeks ago
.gitignore Initial setup of the project directory. 4 weeks ago
LICENSE Create a funny parody logo. 4 weeks ago
Makefile Initial setup of the project directory. 4 weeks ago
README.md It will now watch the static directory as well and do the sync operation when that changes. 3 weeks ago
go.mod Moved over to ssgod because super-saiyan-god would produce binaries with that name. Now go get -tool should work. 3 weeks ago
go.sum Now we have basic directory watching, although it does fail on windows because of timing with the file locking Windows does. 3 weeks ago
main.go It will now watch the static directory as well and do the sync operation when that changes. 3 weeks ago

README.md

Super Saiyan God

A parody of beerus

"This isn't even my final form."

SSG is a Static Site Generator that is only a Static Site Generator. No resumes here! I'll never work at Amazon, Google, or Microsoft so SSG doesn't include every single thing they've ever made. Just a piece of code that generates static files from templates for websites, and can do it live while you develop said templates.

Planned Features Needed

Usage

Create a default ssgod.toml config:

ssgod init

The config assumes you have a public/ as a target, and a pages/ as source full of templates to render. You can change this in the config. Once you're ready run:

ssgod

It will render all pages/**/*.md and pages/**/*.html into the public/ directory using the pages/layout/main.html as the layout. You can then have it watch your pages/ templates for changes and do a sync:

ssgod watch

This will watch the directory and whenever you change something it'll rebuild. It has a 500ms delay to prevent running the render too often.

Syncing a static/ Dir

WARNING: This deletes your target public/ directory. It's assumed that you want to keep a clean public that is only built from other sources. Anything precious in public/ should be moved into static/ so ssgod can faithfully recreate your public/.

If you want to have ssgod sync a static directory then you have to uncomment a line in the ssgod.toml file to enable sync_dir as an option:

views = "pages"
layout = "pages/layouts/main.html"
target = "public"
watch_delay = "500ms"
# comment this out to sync static
sync_dir = "static"

In this example I've removed the comment. Once you do that ssgod will then remove your public/ directory on each run, but recreate it from the static/ and pages/ directory. This ensures your public/ is "clean" and doesn't contain any random junk that might mess up your build.

NOTE: This is a valid reason to do this, but the technical reason is that Go's os.CopyFS will error out when the target file exists. Not sure what kind of Nanny-State bullshit is going on over at Google but the only viable solution is to just remove the directory that's the target, or make my own os.CopyFS...but with Blackjack...and...and Hookers.

After that when you work on the templates it'll sync them over and rebuild your public for you.

In this example I've removed the comment. Once you do that ssgod will then remove your public/ directory on each run, but recreate it from the static/ and pages/ directory. This ensures your public/ is "clean" and doesn't contain any random junk that might mess up your build.

NOTE: This is a valid reason to do this, but the technical reason is that Go's os.CopyFS will error out when the target file exists. Not sure what kind of Nanny-State bullshit is going on over at Google but the only viable solution is to just remove the directory that's the target, or make my own os.CopyFS...but with Blackjack...and...and Hookers.

After that when you work on the templates it'll sync them over and rebuild your public for you.