gulp for its build system. To use the build system and run both Demo and Documentation locally, make sure your system has the following:
Assuming that your system have the above requirements. Then open your command line and navigate to Looper directory, now you need to run:
Finally, once everything is done, you’ll be able to run the various tasks provided from the command line.
gulp task. simple and effective!
If you are not familiar with Gulp, please take a look at this beginners guide.
gulpfile.js includes all of the tasks and subtasks that named after what they do. You can edit or look at any of them to see how they actually work. They're all commented. Below are some of the tasks you will use often:
|| Creates HTML files, builds assets, copied dependencies into
||Open up Looper demo pages in your browser and watch for changes.|
||This is the default command, and probably the one you'll use the most. This command will build all assets and pages then serves it. As you are changing your pages and assets they will automatically update and inject into your browser via BrowserSync.|
||Build the documentation and open up in your browser.|
|| When you are done customizing you can have your assets optimized and injected correctly into your HTML. Your assets will be prettified, minified, compressed with gzip, cache busted and otherwise optimized. All of pages, assets, and documentation will stored in
|| Deletes your assets and all of build files from their
Heads up! We used Liquid Markup to generate html templates with simple logic and load dynamic content in build process. So we can separate our templates into small parts, making it easier to maintenance. Please see the Liquid Markup site to see what you can do with it.
We also used FrontMatter in build process to handle our meta-data from html document and our dummy data from
This work like a static site generator. If you've heard about Jekyll, then you will know that we adopt a similar technology.