stan-fixate

Hi, We are an agency based in Johannesburg, South Africa (GMT+2), we're happy to work with anyone remotely. We are looking for a PHP and front-end developer to work with us now and possibly in the future on a few sites using ProcessWire. Our basic requirements for each site are: All sites are mobile responsive For ease of development and maintainability you should use our SASS framework (inspired by BEM, innuit CSS) - See https://github.com/larrybotha/styleguide/tree/inuit We create a style guide of styles/components (colours, buttons, layout etc) for all sites before building the site. Preferably you would complete the styleguide - If necessary we can create one for each site as a base to build from. Make use of our yeoman project generator which should get you set up really quickly (https://github.com/fixate/generator-fixate-pw) The generator adds our boilerplate with views and controllers (see https://github.com/fixate/pw-mvc-boilerplate) Strong use of coding conventions, structure and modularity Support IE 10 and above We'll provide the design to work from in Illustrator or PDF format. We are happy to provide some help and advice for using these libraries/projects. We've found they work well and the learning curve isn't that steep. Always open to new/better ways of doing things On the front-end side, we build our assets with gulp, we use ES6 and can include React if it makes sense for the project. All of the boilerplate is done for you. Get in touch if you are interested at stan@fixate.it or larry@fixate.it along with the your pricing and some examples of your work. Looking forward to hearing from you! Many thanks, Stan

@SiNNuT Will update the docs - 5.4 is the minimum version because of traits. Traits are only used in the ApplicationController and can easily be placed inline if that suites better. For us it generally doesn't matter as we use 5.4.

@xweb - Hi, I mainly wrote the PW MVC framework. Thanks for pointing that out - this is why we need to get some tests up! The project which I built this for didn't need to change the layout, so it didn't get manually tested - I'll improve/fix the layout API today and write some tests in the coming weeks. (I'm aware that is the wrong order to do things ) As for the the methods used as an example - override_view_name and page_specific, those should work if you have a page called 'override-view-name' that uses the 'Home' template (i.e. HomeController). To be clear, the override_view_name and page_specific are NOT special functions, but just examples (quite confusing examples I'm just realising). If you have a page called 'foo-bar' or 'foo_bar' using the 'Baz' template then you can optionally put a function called foo_bar in your BazController which will be called for that page.