As designers, we are often burdened by the responsibility of producing and managing website content. It's not our job to write it, but it's not the client's either. We can avert disaster by including content production in the design process.

One of the stand-out headline features of HTML5 for many designers and developers was the addition of a number of new types of form input that could be used. For years, we'd been confined to using single-line text inputs (type="text") and laying on JavaScript and user instructions to try an accurately capture valid data of different types through that one unsophisticated field. HTML5 brought with it new values of the type attribute that enabled us to be much more specific about the types of data we needed to capture through the field, with the promise being that the browser would then provide the interface and validation required to coerce the user into completing the field accurately.

On his blog Marc Baker about static calls and the trouble they bring in your applications. It's a continuation of ideas that Kore Nordmann shared previously on his site. It's been seven years since Kore Nordmann first published "static considered harmful" on his blog, explaining the problems with using static method calls in classes, and the difficulties that they cause when trying to test that class. Seven years on, and those difficulties are still the same, and there is still new code being written using static calls despite that knowledge; but it's often a more severe problem in legacy code with little or no unit tests.a So why exactly are static calls so bad? If you've read Kore's article, then you probably have a good idea already; but what that article doesn't cover is approaches that we can use to make the code testable. He covers the main issue static methods have when it comes to testing: they introduce coupling by hard-coding a dependency into your code. He talks about the static testing functionality that various PHP testing tools provided: PHPUnit, Phake and Mockery. He then focuses on a newer tool that he's discovered to help make the testing simpler: AspectMock. He gives an example of it in use and some examples of tests using anonymous classes to make it easier to create tests on the fly.

php[architect] magazine has announced the publication of their latest issue, the March 2018 edition: Long Running PHP. Some of the articles featured in this issue include: "PHP Daemons and Long-Running Processes" by Tim Lytle "Evolving PHP" by Chris Pitt "Containers Are a Pile of Lies! Part Two" by Larry Garfield "Hands on With Accessibility" by Derek Binkley Other topics mentions in the usual columns cover the Lumen framework, code reviews, signed Git commits, running a user group and the use of Twitter for PHP development. You can check out the full list of articles in this latest issue and get a copy of your own on the php[architect] site. If you're interested in the content of the issue, be sure to check out this month's free article.

Although email marketing may seem a rather still industry, it constantly undergoes changes. They may not be obvious to regular users, but email marketers today have way more tools than they would have even 2 years ago. Gamification is one of such tools. Primarily, before live stories and streaming, game-like content was heavily used on...

This week's Designer News (N.360) includes Flexbox Grid System, Learn Angular 2, Free Web Tools, Sketch Tricks, PWA, Design Style Guides, Pencil Beta, and more. The post Weekly News for Designers (N.360) appeared first on Speckyboy Design Magazine.

On the Sticher.io site there's a new tutorial posted where Brendt shares some thoughts about domain driven design and splitting codebases to make them more maintainable and logically separated. In this post we'll look at a different approach of structuring large code bases into separate domains. The name "domain" is derived from the popular paradigm DDD, or also: domain driven design. While many concepts in this post are inspired by DDD principles, they will not follow every rule set by the paradigm. In our context, "domain" can also be named "module". A "domain" simply refers to a category of related stuff, that's it. The post then starts with a definition of what a "domain" is and how it relates to functionality in an application (a Laravel app in this case). He gives an example of restructuring the code into "domains" of functionality rather than thinking about their types (enums, rules, etc). He provides a new proposed directory structure for these domains including folders for Actions, Exceptions, Rules, Status and ValueObjects. He then walks through several of these categories and gives a bit more detail about what's inside and some of the functionality those files might contain.

The trends are always changing and keeping your website up to date with the latest features is a never ending task. CSS formatting helps you rapidly customize your website, allowing you to instantly add certain features to multiple code lines. This is a real time-saver and it will improve your site’s performance. Even though, CSS may […] The post 20 Image Hover CSS Snippets: Designer Cheat List appeared first on Line25.

Everywhere you look, there's video. From social media sites to full-scale web projects, a video can be an integral part of today's online user experience. We have five tips to help you make any web video better, and improve the quality of what you publish. While some projects require the time commitment of a professional […]

I have been an iOS developer for over a decade now and have rarely seen articles that consolidate all possible ways to perform animations in iOS. This article aims to be a primer on iOS animations with the intent of exhaustively covering the different ways of doing the same. Given the extensiveness of the topic, we would cover each part succinctly at a fairly high level. The goal is to educate the reader with a set of choices to add animations to his/ her iOS app.