Source code for the official 'Monica Macovei Presedinte' website.
Setting up the project
This is a single page, static webapp. Dependencies are handled through
bower, and the build process is managed by
To set up the project, install
gulp and the project dependencies:
$ npm install -g bower gulp $ bower install $ npm install
Available build workflow commands
$ gulp $ # or $ gulp build
This will compile a minimal working version (not production-ready) of the project into the
./.tmp folder. No minification or optimization, this task should always do the least possible amount of work to get to something that works.
$ gulp build:dist
This will run
gulp build as a prerequisite and then proceed to perform a number of additional transformations (
html-minify, etc), outputting into the
$ gulp clean $ # or $ gulp clean:dist
This will delete the
./dist folders respectively.
Serving the results
$ gulp serve $ # or $ gulp serve:dist
This will start a
browserSync server with either the
./dist directory as the source.
browserSync will synchronize scroll events, form actions, and more.
Developing for the web
$ gulp watch
This will run the build task, then a
gulp serve server on top of it that will automatically refresh when you change anything relevant in
$ gulp test
This will run the tests on the files in the
./.tmp directory by using a
phantomjs headless browser, and re-run them upon detecting file changes. It will output the results to the console and optionally as system notifications if you're on OSX.
A typical development workflow will involve running:
It will start a testing server on
http://localhost:9876. You can connect to this server with as many test browsers on your network as you want. Leave them running with the tab open to have Karma use them for all future tests.
$ gulp test:once
This will run the build task, and then the tests just one time. Used by
travis. Additionally, it will also generate accurate coverage reports for
$ foreman start $ # or $ ./node_modules/gulp/bin/gulp.js build:dist && node index.js
This will start the production
express server (using the
./dist folder) that doesn't do any fancy live-reloading or scroll synchronization, but does
gzip your assets.
$ # if you're using `foreman start`, it'll start the server on `localhost:5000` $ PORT=5000 gulp pagespeed
Use this in combination with the production server to alias it to a secure external tunnel URL, which will then get passed to Google Pagespeed Insights. You'll receive a report in your terminal about how to further improve the performance of the application.
Tools, libraries and languages used
gulp- build workflow
karma- test runner
mocha- test framework
should- assertion library
istanbul- coverage reports
browserSync- development server
jade- HTML preprocessor
stylus- CSS preprocessor
travis- continuous integration
coveralls- online coverage reports
. ├── app # raw application logic and assets ├── gulp # build tasks └── test # frontend tests
. ├── .tmp # minimal build ├── dist # production build ├── coverage # coverage information └── node_modules # node dependencies
- All commits and pull requests get processed by
travis, which runs the test suite. Every build will also report to
- Fork the project and send in pull requests.
jshint, which will automatically pick up the included