Wednesday, July 20, 2016

The Worst Metric to Focus on First in PPC


Open any PPC analytics dashboard and you’ll start swimming in numbers. Which ones are important and which ones can be set aside? Many people focus on the click-through rate (CTR). That’s the proportion of how many people see your ad versus clicking on your ad. So, if 1000 people see your ad and 100 people click it, that’s a click-through rate of 10%.

It seems like an obvious metric for success. But speaking from over a decade of personal experience running Adficient, the click-through rate is not the first metric to examine for long-term success. Why? First, it’s a lousy way to measure how well you’re doing versus the competition. If everyone else has a high click-through rate on the same keywords, your piece of the overall clicks is smaller than you might imagine. Many new PPC marketers also seek a high PPC rate because it means lower prices from your provider, but that’s also measured in relation to your competition.

Also, just because someone clicks on your ad doesn’t mean they’re going to buy. A high click-through rate means you have an ad that people like but it doesn’t necessarily translate into purchases. If no one buys, you’ll just be paying for all those clicks with nothing to show for it.

So, if the click-through rate is misleading for success, then what’s the metric we should look at first?

by Guest Author via Digital Information World

Is going through recruiting a good option for landing an ideal UX role?

Georgie Carpenter is the founder of 10collective—a recruiting agency specialising in IT and UX roles. Matt interviewed her a while back as research for our book Get Started in UX, the complete guide to launching and growing a career in user experience design. Read on to hear Georgie’s insider tips about getting a competitive advantage in your hunt for the ideal UX job.

Can you tell us about 10collective?

Georgie Carpenter

Georgie Carpenter, director and owner of 10collective, a UX recruiting agency

10collective was a company that I started by accident in 2008. I walked out the door of my previous company, an IT recruitment agency, and received a call from a client who said, “Can you find me a developer”? I said, “Okay” and on autopilot I found one and made a placement.

At the time, it was just a bit of fun and I assumed I would spend my newfound free-time painting or writing books, but it snowballed from there. In the end, I needed to hire an additional employee, and soon after that we moved into an office in Fitzroy.

At that point I’d been recruiting user experience people for a number of years. There is some debate about whether the position should even be called “User Experience” anymore, because it’s really “experience design” to some of the more established UXers.

You’ve been recruiting UX professionals for quite a while. What changes have you seen in the industry since 10collective started?

Clients certainly want UX professionals more now than they did years ago. Employers understand that UX is important and that consumers want a better “user experience” for their public-facing website.

I’m not convinced that all employers actually understand what user experience means yet, although it’s definitely more prevalent. The first school of UXers that I worked with sought to evangelise UX as important and essential, but now it is less of a fight. There is still some education to be done around what a UXer actually does, but the term “user experience” has changed, or evolved, quite substantially. If you were to ask some job hunters or employers, the difference between “user experience” and “usability”, they can’t always tell you.

Nowadays, different types of organisations want UXers, not just organisations with immense budgets. Employers don’t necessarily want what I was looking for years ago—hardcore UXers that understand interaction design and contextual enquiry—they just want a UXer to use their common sense, which is not entirely unreasonable.

The first school of UXers were very much user and research-centric. That isn’t something that a lot of my clients can even do given their budget limitations. UXers are now being sought for their established expertise rather than what they can discover by research. Many user experience people still want to be involved with the user, though. It is frustrating that many organisations are offering user experience services and user experience expertise, but they don’t have much exposure to the actual user.

Are those who are getting into user experience coming from a visual background? Is that the general path?

Yes—if you have a visual background and a good foundation of the basic principles of user experience and usability, then that’s an effective avenue for you to get a job with the title, “User Experience Designer”. Whether you can truly be a UX Designer at that point is debatable.

Do you think that you’re on the back foot if you’re not coming from a visual design background?

I think so, yes. Many agencies, for example, don’t need just “researchers” anymore— they do require you to have visual design skills as well. You need to be able to get a piece of paper and a pen and throw together some sketches. You would need to have a basic understanding of user experience or usability in order to satisfy the job briefs that we’re getting from clients, on the whole.

What skillsets are clients looking for in UX roles? Does the client say they need a user experience person when what they really want is a visual designer who’s going to use their brain?

Commonly, a client such as a digital or advertising agency will want someone in-house who is a visual designer with agency experience, but who also understands the principles of user experience. What that means is they need someone to do wireframing and prototyping, interview stakeholders and users and be able to expertly review the application or site.

There isn’t a decent understanding of the need for the individual to lead focus groups or use eye-tracking equipment or do card sorting. In many cases, it’s unlikely that those activities are going to happen in a small to medium agency, unless their clients agree to pay a reasonable amount of money. The Account Services team also needs to be able to sell those services—which is another debate entirely!

Skills-wise, a UXer would ideally have experience with Axure and Balsamiq, have some exposure to Visio and be able to use the Adobe Creative suite. UXers need to be able to defend their designs and engage in conceptualisation and ideation. Importantly, they need to have worked on robust and meaty applications. They also need to know how to talk to people, obviously!

techniques and recruiting

Being a successful UX professional is more than just being able to use the tools. You need to know how to wear the whole belt while driving process, managing people and communicating design effectively.

Nowadays, are UXers being employed in-house or as contractors?

A lot of people are doing contract work at the moment because they get better money contracting. Freelance projects are common. If you are a career UXer, you will probably end up contracting to say, three to five extremely loyal clients that use you repeatedly and pay you excellent money. Essentially, in recruiting we have had many top UXers wiped from the market which is a tragedy for smaller businesses who really could use the expertise of those people.

I advise UXers to do contract work as much as they possibly can now, but start looking for a permanent or good long-term contract within the next six to twelve months. Recruiting is a good option to help with that.

How do you determine whether an applicant truly understands what UX is?

When recruiting, I start by asking the applicant a basic and disarming question, “What is User Experience?” Oftentimes they just tell me what usability is and I might prod them until I get a better answer. Having a robust opinion about the field you engage in is compelling in job interviews. I know that UXers have to be pragmatic and maybe educate users, but users are supposed to inform your design. It’s a fairly good sign when I hear that a UXer is not attempting to change the user. Many applicants don’t even mention the user and that’s a black mark most of the time. User experience is not just the experience the user has with your product.

Would you say having a process and being able to talk about it is important?

I think so. I love it when I ask an applicant to take me through their process and the first thing they do is grab a piece of paper and a pen and take me through their process with some decent narrative.

Storytelling is a critical component of UX on the job, so I like to see evidence of that in a recruiting interview. A candidate must also have experience with the activities and practises that fall under the user experience umbrella.

What advice would you give a candidate coming into UX from another area, such as business analysis, creative production or development?

I’d advise against calling yourself a user experience designer if you’re not comfortable doing so—simply say you’re a producer with UX skills or a project manager with UX skills, or focus on the research side of things if that is how you are inclined.

The word “designer” is misleading to many companies. If a company is hiring, an applicant’s first gateway is an HR person who usually doesn’t know what user experience designers do. They see the word “designer” and they imagine someone creative for the job. You actually don’t need to be particularly creative to be a fabulous user experience researcher, in the traditional sense, although the UX discipline firmly belongs in the creative sphere.

I would advise job seekers to get into their UX community. Start reading some old school HCI usability UX blogs—for example Jakob Nielsen—but also get into some new blogs. Attend a UX Book Club and network. Simply being around UX people will give you some context around what you do and how that’s relevant to the user experience process. Doing so also gives you an idea of the language inside the UX and Design world—using relevant terminology is always useful in an interview!

Take a Business Analyst for example. What a Business Analyst does is so relevant to UX—how they interview and observe people, create specifications and evaluate scenarios. The thought process they go through is key for a UXer, but a Business Analyst needs to know how to describe what they do in UX terms.

UX Portfolios are a great help during recruiting

The answer lies in building the right kind of UX portfolio, and being smart about it.

How should a candidate prepare for an interview if they get to that stage? Would you recommend a portfolio for someone who doesn’t have a substantial visual background?

Absolutely. A user experience folio is not a design folio—it’s a case study folio and a dissection of all the activities it took to get to whatever outcome you’ve reached. What I recommend with UX folios is that once you’ve determined that a particular activity pertains to the UX discipline, you need to dissect it.

An infographic or something visual is a good idea to illustrate what you’ve done. It doesn’t need to be a band poster; it needs to be something like a screenshot of your wireframe or an infographic to show how you got to the end result.

Opinions don’t hurt, either. For example, saying, “These are the results—they were surprising for such and such reason” is pertinent for both user experience professionals and those who want to get into user experience. Giving your opinion demonstrates that you understand that those analytical skills are transferable to the discipline.

Having a folio to kick-off the discussion can be a difficult concept for many job seekers. Some UXers I know, who are absolutely amazing, have never landed a job with a folio or a CV because everyone knows their reputation so they get jobs via word of mouth. However, I still think that they should have a beautiful folio—a dissection of their ideas, their opinions and their assumptions and then how they’ve backed those things up with actual data, research and design expertise.

The UX unicorn, truly rare in recruiting

That rare creature with the glittering horn—the one who says they can design and program and manage people, all perfectly—don’t be one of those.

Do you have some general tips on how to make the most out of an interview?

Firstly, when running through your work history, ensure that your timeline actually makes sense. If you’ve been fired a bunch of times, you just need to come clean and admit it before it comes out later in the recruiting process.

Most interviews will have a behavioural interview component. The philosophy behind behavioural interviewing is that how you have acted in certain situations in the past can predict how you would act in similar situations in the future. I think it’s a flawed philosophy as nothing can predict any of those things, but behavioural interviewing during recruiting is generally believed to give an indication.

I think job seekers need to learn how to handle behavioural interviews. Most questions in this format start with, “Describe a time when…”. You need to think of a specific example in your past where you addressed the question and answer along the STAR format.

You should then analyse what you did wrong in the example you chose and also what you learned from it. If you can apply that way of answering to every behavioural question you are asked, you’re laughing.

It’s OK to use a personal scenario if you can’t apply the question to a work one. If you are changing fields, all people need to know is that you can learn and adapt to the new position that you’re applying for.

That’s where behavioral interviewing can be very useful during the recruiting process. It assesses your aptitude, emotional intelligence, commercial maturity, self-awareness and your ability to learn. If you have the skillset that is required but cannot demonstrate the key competencies in the role via a behavioural interview, then a client is unlikely to hire you.

The other piece of advice I would give is to practice your ability to decide which questions require a long answer and which ones require a short answer. It is fairly essential not to bore the interviewer.

There is some debate about how long your CV should be. What are your thoughts on that?

It depends on the client. Some clients need to be educated around what your experience is, in which case a four or five page CV can be helpful for them. There are also clients that are savvy enough to read between the lines and can draw what they need in a one to two pager. Your CV shouldn’t go any longer than four or five pages.

Your CV needs to compel a client to read on within the first five seconds of looking at it. If it does, they’ll spend the time to read the rest. If it doesn’t, it makes no difference whether your CV was one, four or thirty pages—it won’t get read.

Some of the most talented people I know don’t have good CVs. They have one page that says, “I’ve done this”. That’s good enough for them because they know people, but it’s not good enough for all of my clients.

For UXers, when you write your CV, you need to be prepared to answer the question, “How do you use your understanding of the UX discipline in the design of your CV?” Many people in the UX field do not use their skills in designing this very important piece of paper.

Your expertise has a Melbourne bent. Do you have a sense for whether there are hotspots for UX in the rest of the country, or globally?

I have many English and American people approach me for roles in Australia. Their understanding of user experience, and how it’s used practically, is quite different to ours. Recruiting for UX looks different in different places. One of the criticisms I commonly hear, from British people especially, is that nothing gets done in UX in Australia—we spend too much time in concept, too much time in research and not enough time doing.

The other piece of positive feedback that I get is that Australians are very detail oriented and we do get UX right. When I went to London last year, a mobile director for a very large and well-known digital agency remarked that Australia’s user experience for mobile applications was second to none. I’ve also heard—and I don’t know if this is true—that there is an amazing user experience scene in South America. I’ve not done any recruitment there, but I have had some people with South American roots come to me.

Considering there is a demand for UX, is it fair to say a UXer can be choosy about which jobs they take and what they do on them?

Yes and no. There was definitely a time I was getting frustrated at the UX community for being princesses during recruiting in all kinds of areas— wage, working hours, the stage of UX and design maturity—but the community is coming out of that now. Frankly, as any kind of job seeker, you should be picky about your job choice.

I think work cultures are very institutionalised in some organisations. Even though the organisation is saying they need a UX person, in fact, there may not be a place for them there culturally.

If you have to evangelise and educate, it’s a 24/7 job. It’s a very rare person who could do the job part-time. You have to be constantly showing the client that you are not only good at your job but that you are actually adding value. The issue is that what you provide isn’t necessarily something you can hold in your hand and show someone.

When you’re not proving to the client that you’re adding value, you’re being an entrepreneur, validating tests or doing experiments. Do you think the client values that learning?

Not always—and that’s a fairly dangerous position to be in during recruiting if there’s a recession imminent. Ultimately, if you’re not providing tangible deliverables and a return on investment right here and now, you might get relegated to middle management status, and I think we can all agree that middle management people always go first in the lay off rounds.

Is there a seasonal demand for UX work?

UX work is seasonal, absolutely. UXers are always involved during production, even though they should probably by around before the idea even happens. January is not a great time to go through the recruiting process to find a UX job compared to the rest of the year, but then January is not a good time to find a job for anybody!

You can read more about UX recruiting, and how to use it to your advantage as a UXer looking for work, in our ebook Get Started in UX

The post Is going through recruiting a good option for landing an ideal UX role? appeared first on UX Mastery.


by Georgie Carpenter via UX Mastery

Python on the Web: Why Frameworks Like Django Are Hot

Created in the early 1990s by Guido van Rossom, Python has grown in popularity over the years. In 2016, Python is the 4th most popular language after Java, C and C++. Python is a general purpose programming language, and it can be used in a variety of fields. To quote Kenneth Love from Treehouse ---

When I need to build a web app, I reach for Python. When I need to automate some small task on my system, I reach for Python. When I want to find the most common colors in an image, I reach for Python.

Python is a popular choice for writing scripts for testing and monitoring. Python has also been used for game development, and its ability to be integrated with other languages makes it very valuable in the process. Such is the popularity of Python that it's also been used by George Lucas' Industrial Light and Magic (responsible for special effects in the original Star Wars trilogy) to manage its complex production process.

Unlike PHP, it wasn't built for the web in mind, and there are no core web functionalities that are integrated into Python. Hence, we must use a web framework to develop web applications in Python. Web developers have started using it for the web since the rise of popular frameworks like Django.

What makes Python the go-to language for an increasing number of developers when it comes to web development these days? We'll try to find an answer to this question in this post.

Why use Python?

Python for beginners

The primary reason for the popularity of Python is the elegance of the code --- the brevity and readability in particular. For instance, let us look at how Python and Java stack up against each other in terms of reversing a number:

Java vs Python

Programs to reverse a number in Java (left) and Python 2.7.x (right)

Python provides a short learning curve, making it ideal for beginners to learn. In addition to that, if your project is Python-based and new developers aren't familiar with it, the transition is easier.

As Quora co-founder Adam D'Angelo says on the choice of Python for Quora's development ---

So far, we've been pretty happy with the choice … all of the early employees who'd been working with other languages in the past were happy to transition to Python, especially those coming from PHP.

In fact, the webcomic xkcd came up with a cartoon on how easy it is to get things done in Python!

Python webcomic by xkcd. Source: xkcd.com

Further, Python has easy to use debugging tools. Although there are several debuggers and IDE tools, the default one is pdb, an interactive debugging tool which allows a developer to stop the execution of a program midway and assess the environment to better understand run time errors.

Python on a remote server

The management of packages (or modules as they are called) in Python is very easy too. Use a package installer like pip or easy_install and it can be used to install and remove packages.

Python is very portable too! The ease of transferring your development environment to a remote machine is commendable. You just need to export the packages, and install it in a virtual environment on the remote machine with just two commands.

One more reason why Python is a good choice for web applications is the ability of running scripts which are not embedded to the web server (unlike running a PHP script.) Scripts are run as separate processes.

Continue reading %Python on the Web: Why Frameworks Like Django Are Hot%


by Shaumik Daityari via SitePoint

iziModal – Responsive and Fexible Modal Plugin with jQuery

iziModal is an elegant, responsive, flexible and lightweight modal plugin with jQuery.


by via jQuery-Plugins.net RSS Feed

An Alternative to Regular Expressions: agp-exp

Hardly any programmer escapes the need to use regular expressions in one form or another from time to time. For many, the pattern syntax can seem cryptic and forbidding. This tutorial will introduce a new pattern-matching engine, apg-exp—a feature-rich alternative to RegExp with an ABNF pattern syntax that is a little easier on the eyes.

A Quick Comparison

Have you ever needed to verify an email address and come across something like this?

^[\w!#$%&'*+/=?^_`{|}~-]+(?:\.[\w!#$%&'*+/=?^_`{|}~-]+)*@(?:[A-Z0-9-]+\.)+[A-Z]{2,6}$

A pattern-matching engine is the right tool for the job. This is a well-designed, well-written regular expression. It works great. So what's not to like?

Well, if you are an expert with regular expressions, nothing at all. But for the rest of us, they may be

  • Hard to read
  • Even harder to write
  • Hard to maintain

The regular expression syntax has a long, time-honored history and is deeply integrated into many of the tools and languages that we, as programmers, use every day.

There is, however, an alternative syntax that has been around almost as long, is very popular with writers and users of Internet technical specifications, has all the power of regular expressions but is seldom used in the world of JavaScript programming. Namely, the Augmented Backus-Naur Form, or ABNF, formally defined by the IETF in RFC 5234 and RFC 7405.

Let's see what that same email address might look like in ABNF.

email-address   = local "@" domain
local           = local-word *("." local-word)
domain          = 1*(sub-domain ".") top-domain
local-word      = 1*local-char
sub-domain      = 1*sub-domain-char
top-domain      = 2*6top-domain-char
local-char      = alpha / num / special
sub-domain-char = alpha / num / "-"
top-domain-char = alpha
alpha           = %d65-90 / %d97-122
num             = %d48-57
special         = %d33 / %d35 / %d36-39 / %d42-43 / %d45 / %d47 
                / %d61 / %d63 / %d94-96 / %d123-126

Not as compact, for sure, but like HTML and XML it is designed to be read by humans as well as machines. I'm guessing that with nothing more than a passing knowledge of wild card search patterns, you can just about read what is going on here in "plain English".

  • the email address is defined as a local part and a domain separated by @
  • the local part is one word followed by optional dot-separated words
  • the domain is one or more dot-separated sub-domains followed by a single top domain
  • the only things you might not know here, but can probably guess, are:
    • just as the wild card character * means "zero or more", 1* means "one or more" and 2*6 means min 2 and max 6 repetitions
    • / separates alternate choices
    • %d defines decimal character codes and character code ranges
    • for example, %d35 represents #, ASCII decimal 35
    • %d65-90 represents any character in the range A-Z, ASCII decimals 65-90

RegExp and apg-exp are compared for this email address in example 1.

apg-exp is a pattern-matching engine designed to have the look and feel of RegExp but to use the ABNF syntax for pattern definitions. In the next few sections I'll walk you through:

  • How to get apg-exp into your app
  • A short guide to the ABNF syntax
  • Working with apg-exp—a few examples
  • Where to go next—more details, advanced examples

Up and Running—How to Get It

npm

If you are working in a Node.js environment, from your project directory run:

npm install apg-exp --save

You can then access it in your code with require().

For example:

var ApgExp = require("apg-exp");
var exp = new ApgExp(pattern, flags);
var result = exp.exec(stringToMatch);

GitHub

To get a copy of the code from GitHub, you can clone the repository to your project directory:

git clone http://ift.tt/2av5CgH apg-exp

or download it as a zip file.

Then in page.html:

<!-- optional stylesheet used in tutorial examples -->
<link rel="stylesheet" href="./apg-exp/apgexp.css">
<script src="./apg-exp/apgexp-min.js"></script>

<script>
  var useApgExp = function(){
      var exp = new ApgExp(pattern, flags); 
      var result = exp.exec(stringToMatch);
      /* do something with the result */
  }
</script>

CDN

You can also create a CDN version directly from the GitHub source using RawGit. However, be sure to read the no uptime or support guarantees (In fact, be sure to read the entire FAQ).

The following are used in all of the examples in this tutorial.

<link rel="stylesheet"
 href="http://ift.tt/2av6bXO">
<script
 src="http://ift.tt/29WalZT"
 charset="utf-8"></script>

These files are cached on the MaxCDN servers and you are free to use them for testing as long as they remain available. However, for production, you should place copies of apgexp-min.js and apgexp.css on your own servers for guaranteed access
and include them in your pages as best suited to your application.

A Short Guide to ABNF

ABNF is a syntax to describe phrases, a phrase being any string. As you saw in the email example above, it allows you to break down complex phrases into a collection of simpler phrases. A phrase definition has the form:

name = elements LF

where LF is a line feed (newline \n) character.

The table below is a short guide to the elements (see SABNF for the full guide).

Continue reading %An Alternative to Regular Expressions: agp-exp%


by Lowell D. Thomas via SitePoint

How to explore the physical web, implement fast infinite scrollers, code mobile-first emails

The history of URLs, CSS-powered search features, and how AMP is going to deal with ads.
Read this e-mail on the Web

FrontEnd Focus

formerly HTML5 Weekly

Uri Shaked
“The Physical Web lets you anchor URLs to physical places by way of a BLE beacon.” And it’s possible to use your normal computer to do this, instead of hardware beacons.


Google Developers
“Infinite scrollers are a common UI pattern. Here we explore how to implement this pattern in a memory conservative way that performs at 60fps.”


Stig Morten Myre
A thorough, practical step-by-step guide to creating consistent looking emails across mobile, desktop and everything in between.


Linode  Sponsored
Linode's SSD hosts are the perfect environment for any HTML5, CSS, and JavaScript media. Meet your website's demands with a lightening-quick cloud host offered at competitive pricing. 99.9% uptime and 24/7 support.

Linode

Zack Bloom
Hyperlinks form the basis for the web. Here’s an in-depth history lesson on the humble URL and what each part of a URL means.


Denis Lukov
Leans on the idea of using CSS selectors to show/hide certain items within lists, creating a CSS-powered ‘search engine’ of sorts.


Dominique Hazaël-Massieux
Most of the APIs exposed on the Web platform rely on a formalization language called WebIDL (Web Interface Definition Language).


Mozilla
An experimental framework for extracting meaning from web pages, identifying parts like buttons, address forms, and the main textual content. Essentially, it scores DOM nodes and extracts them based on conditions you specify.


Accelerated Mobile Pages Project
A look at how the AMP project is building a user-experience-first ecosystem for advertising on the web.


Jobs

  • Find Your Perfect Company MatchYou're smart, you're efficient. Why job hunt the old way? Try Hired and get your profile in front of thousands of top tech companies. Hired.com

In brief

Curated by Peter Cooper and published by Cooper Press.

Unsubscribe : Change email address : Read this issue on the Web

Published by Cooper Press Ltd. Fairfield Enterprise Centre, Louth, LN11 0LS, UK


by via HTML5 Weekly

20+ Docs and Guides for Front-end Developers (No. 9)

It’s that time again to get learning! As before, I’ve collected a number of different learning resources, including guides, docs, and other useful websites to help you get up to speed in different areas of front-end development.

So please enjoy the ninth installment of our Docs and Guides series and don’t forget to let me know in the comments of any others that I haven’t yet included.

1. JavaScript Standard Style

This is not primarily a learning guide, but a module that you can install and run via the command line to test your code against a set of rules for JavaScript syntax. It’s also available as a text editor plugin. As a guide, however, you can read the rules breakdown, which should be a good way for beginners and others to get a sense of some general JavaScript best practices.

JavaScript Standard Style

2. Webpack: An Introduction

“Webpack is a popular module bundler, a tool for bundling application source code in convenient chunks and for loading that code from a server into a browser.” This guide is on the official Angular website, so the guide is geared towards using Webpack with Angular 2 apps.

Webpack: An Introduction

3. Aural UI of the Elements of HTML

“How HTML elements are supported by screen readers.” Consists of four tables of data covering JAWS on Firefox on Windows 10, VoiceOver and Safari 9 on OSX, and NVDA and Firefox on Windows 8.1, with more tests to come.

Aural UI of the Elements of HTML

4. Type Terms

This is more for designers than developers, but it’s a really nicely designed and useful interactive tool for those who want to become more familiar with typography terminology. Made by the folks at Supremo, a Manchester-based design agency.

Type Terms

5. Email Toolbox

This is an extensive resource of links focused primarily on designing and coding HTML email. Lots of stuff under various categories including people to follow, courses, blogs to read, tools, and email service providers.

Email Toolbox

6. Almost complete guide to flexbox (without flexbox)

There are so many different flexbox guides and tools floating around, but here’s something a little different. This guide shows you how to achieve flexbox-like effects in your layouts using the traditional methods. Nice to see them all in one post like this, with code examples.

Almost complete guide to flexbox (without flexbox)

7. Angular 1.x styleguide (ES2015)

This is an “Angular styleguide for teams” by Todd Motto, a Developer Advocate with Telerik. Todd also offers courses on AngularJS development. This styleguide “has been rewritten from the ground up for ES2015, the changes in Angular 1.5+ for future-upgrading your application to Angular 2.”

Angular 1.x styleguide (ES2015)

Continue reading %20+ Docs and Guides for Front-end Developers (No. 9)%


by Louis Lazaris via SitePoint