Skip to content
Svelte Site Generator. why try this? because sapper has a lot of setup, and isn't great at pipelining data:
TypeScript JavaScript HTML
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
examples add examples and source-yaml Sep 12, 2019
packages bump sapper dep to fix export queue issue Nov 7, 2019
.gitignore swap implementation to fork sapper cli Sep 12, 2019
LICENSE Create LICENSE Sep 12, 2019
README.md deactive source remark Nov 4, 2019
package.json add examples and source-yaml Sep 12, 2019
yarn.lock deactive source remark Nov 4, 2019

README.md

SSG

this is a monorepo for a Sapper Site Generator and related packages. Check README's inside /packages for more info on each. In particular:

We also have an examples folder but its kinda inactive right now.

Project Roadmap

I have been dragging my feet on SSG mostly because I wish someone else was working on it rather than me (it will never make money and I don't have time for it).

However the conversations I have daily at work always bother me and make me wish there was a better solution out there. Because nobody is working on exactly what I want, I'm forced to be the one to do it :( despite not having a better usecase for it than my own blog.

I am not at all optimistic this will ever be a wise venture so this is literally for shits n giggles until someone more serious than me picks this up. Because I'm not serious about it, it has an even higher chance of failure than the abysmal chance it had :(. at least i hope somebody else comes along and picks this up.

SSG v0

whatever i have now, the Sapper-based slow monstrosity. I can add:

  • an incremental build api
  • zero config filestructure based markdown
    • default ejectable theme
  • preprocessed typescript and postcss
  • DEBUG=*

SSG v1

What I want SSG to launch with is:

  • 0kb of JS for a page that doesnt use it
  • visual editor? use netlifycms? fork sapper studio?
  • incremental builds
  • ludicrous speed. this probably means not using Sapper, and possibly using Rust/WASM.
  • ejectable themes
  • preprocessed typescript and postcss
  • Zero config:
    • RSS
    • filestructure based markdown
  • ship your own docs in CLI
  • proper docsite
  • DEBUG=*

open questions:

  • dev mode?
  • no clientside routing?
  • graphql?
  • 404 search
  • react import path?
  • tailwind?
  • graphql support?
  • support 11ty's templating (mustache etc) and exact api?

SSG v2

I actually wish i could work on this earlier, but Netlify doesn't support datastores now so there's no point:

  • serverless serving if updates are found (so you get instant refresh)
  • smart clientside routing? need to learn a lot more about this
  • service worker layer?

TODO: check if there's a way to see if there's a new version of a page updated

  • nested ssgconfigs so you can section up sites?

What else?

You can’t perform that action at this time.