FE developer meeting

18.11.2013.

Building a demo product/best practices repository


EEDemo app

We should start with the manager apps since they are simpler and use the experience on WCI/IBE



What we can do "RIGHt now"


1) Full switch to eefetools (consistency)

2) Implement all modules we use (if not all module use cases)

3) Increase comment frequency and their usefuleness

What we need to discuss first


1) How to share (bug) fixes?

2) What functions can we abstract?

3) How to include and validate JS in the future( not inline) ?

4) Who's in charge?

Using a framework/workflow (Backbone.js / Ember.js, Yeoman...)


What's the current situation?

Depends on the project


1) MLD and HHN have "more" Backbone.js implementation

2) JBU and DLH have "some" Backbone.js

3) Do other projects use it?

In addition to Backbone.js, HHN is being built with Grunt.js (and LESS is also required)

WHAT WE CAN DO "RIGHT NOW"


1) Decide what to do with Backbone.js/Grunt.js/Bootstrap/Less (keep in certain projects, replace with something else, move current projects to these technologies)?

2) Decide if we're going to switch to RESTful API (in 2013, a kitten dies every time the page reloads instead of making an XHR request)

WHAT WE NEED TO DISCUSS FIRST


1) Decide if we're interested in going more JS and less PHP ( either by utilising a framework, XHR or even going one page app)

2) Discuss our Mercurial workflows

Test driven development


Currently not used on FE

Open for suggestions
Made with Slides.com