geoff
/
riot-starter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
13 Commits 2 Branches 0 Tags 513 KiB
Go to file
Geoff Doty 76259b485d added LICENSE content;) 2018-11-30 05:16:21 -05:00
docs initial commit 2018-03-22 16:37:34 -04:00
src/public increased landing page font size 2018-11-30 04:37:35 -05:00
.editorconfig initial commit 2018-03-22 16:37:34 -04:00
.eslintrc.json replace jscs with eslint 2018-11-09 19:57:18 -05:00
.gitignore ignore dist 2018-11-09 17:29:27 -05:00
LICENSE added LICENSE content;) 2018-11-30 05:16:21 -05:00
README.md tweaks 2018-04-01 03:19:55 -04:00
gulpfile.js FIX: npm build WORKS now w/ gulp@4. Added more tasks, and task groups 2018-11-30 04:39:58 -05:00
package-lock.json changed how vendor assets are managed. using npm `frontend-dependencies` 2018-11-30 04:35:13 -05:00
package.json changed how vendor assets are managed. using npm `frontend-dependencies` 2018-11-30 04:35:13 -05:00

README.md

Rapid RiotJS

A Starter kit

Rapidly prototype your next single-page application, with a zero-build out-of-the-box web-component solution. Need to go beyond the prototype stage, fret not, the tools are in-place to take you to production.

Features

  • RiotJS 3.x
    • Web Components for reuseable UI
    • Events for communication
    • Route for url navigation
  • Based on HTML5Boilerplate 6.x
  • JSCS for coding style
  • Jasmine for testing
  • Gulp for production builds
    • Rollup to only export the code your using

Getting Started

Why Zero-Build?

SPEED!

A production pipe-line should NOT be in your way while developing...

...however, npm build adds it when you need it

How

Project Structure

Polyfills

Todays "Evergreens" browsers support 99% of ES6, providing a pethra of capabilities, such as import, class, fetch, and promise. Depending on your desired browser support, you may find a polyfill to suit your needs...

...but such is beyond the scope of this starter kit.