Repository files navigation

transforms a src directory into a github hosted gh-pages branch.

npm i --save mspg/core

mspg comes as a single executable file.

mspg [TASKS]...available tasks:clean   - deletes the public directorybuild   - builds the src dir to publicserve   - serves the public dirzip     - gzips the public dir using zopfliconnect - connects the git repository to it's gh-pages branchpublish - publishes the current HEAD to github/gitlab pageshelp    - this help text

# production buildNODE_ENV=production mspg clean build zip# development (build files, watch for changes, and serve them on localhost:3000)mspg build serve watch

a minimal example app is in theexample directory of this repository,usingconfig.js from the root directory

the example app is published to thegh-pages branch.it is hosted @https://mspg.github.io/core

writing transpilers for any kind of toolchain is pretty easy,just have a look at the examples below to get started if you want to use another toolchain.every transpiler also includes a minimal example project in the example directory.

both html toolchains below follow the same rules:

• every *.html file in the src/ directory is a page and gets transpiled to public/

• every includes/html/*.extension file is an include file and can be included using /filename.extension

• every includes/html/*.extension file can also be a template file. using extend you can reuse a html template in both pug and posthtml.

• pug

• posthtml

• stylus
• postcss - soon

• babel
• rollup - soon