[ This is a content summary only. Visit our website http://ift.tt/1b4YgHQ for full links, other content, and more! ]
by Web Desk via Digital Information World
"Mr Branding" is a blog based on RSS for everything related to website branding and website design, it collects its posts from many sites in order to facilitate the updating to the latest technology.
To suggest any source, please contact me: Taha.baba@consultant.com
Underscore.string is a string manipulation helpers for javascript. Originally started as an Underscore.js extension but is a full standalone library nowadays.
This article was sponsored by JetBrains. Thank you for supporting the partners who make SitePoint possible.
In this 2-part series, Google Developer Experts Jurgen Van de Moere and Todd Motto share their favorite productivity tips for developing Angular applications using WebStorm.
In this first part, Jurgen shares his personal top 5 WebStorm features that allow him to increase his productivity on a daily basis:
Each tip can tremendously increase your development productivity, so let's dig into them a little deeper one by one.
Angular CLI is a Command Line Interface (CLI), written and maintained by the Angular team, to help automate your development workflow. You can use it to quickly create new Angular projects and add new features such as components, services and directives to existing Angular projects.
WebStorm's integration with Angular CLI provides you with all its power right from within WebStorm, without using the terminal.
To create a new Angular Project, choose File | New | Project and select Angular CLI.
Enter a project location and hit the Create button. WebStorm uses Angular CLI to create a new Angular project and install dependencies.
When your new Angular application is in place, you can easily add new Angular features. Right click on src/app and choose New | Angular CLI to pick the type of feature you wish to add.
Once you’ve selected a feature, you can specify the name and optional parameters, just as you would with Angular CLI on the command line:
To learn more about Angular CLI options and parameters, make sure to check out The Ultimate Angular CLI Reference.
What's really awesome is that WebStorm automatically adds the component to the right Angular module for you, in this case AppModule.
If your application has multiple Angular modules, right click on the module you wish to add the feature to and choose New | Angular CLI. WebStorm will make sure the new files are created in the right location and that the new feature is added to the correct Angular module.
How sweet is that!
Use cmd-click or cmd-B to easily jump to any definition within your project.
If you are a keyboard user, just put your cursor on a term and hit cmd-B. If you are a mouse user, hold down the cmd button and all terms you hover will turn into links to their definition.
WebStorm automatically recognizes Angular components and directives in your HTML, links to stylesheets, links to templates, classes, interfaces and much more.
No need to open file(s) manually, just jump to any definition you need:
When looking for a file that you don't have an immediate reference to, hit shift twice to open the Search everywhere dialog. You don't have to type the entire search string. If you want to open AppComponent, just type the first letter of each part — i.e. ac — and WebStorm will immediately narrow down the result list for you, so you can quickly pick the suggestion you wish to open:
Another super useful navigation shortcut is cmd-E, which presents you with a list of recently edited files so you can easily navigate back and forth between them.
Knowing how to quickly navigate to the code you need will save you a tremendous amount of time every single day.
Angular Language Service is a service, designed by the Angular Team, to provide IDEs with error checking and type completion within Angular templates.
WebStorm integrates with Angular Language Service to better understand your code. To enable Angular Language Service, first make sure it is installed:
npm install @angular/language-service --save-dev
If you use Angular CLI to generate an Angular application, Angular Language Service is automatically installed.
Next, go to Preferences | Languages & Frameworks | TypeScript, make sure Use TypeScript Service is checked and click Configure...:
The Service Options modal will pop up. Enable Use Angular service and apply the changes:
By default, WebStorm already provides great assistance for writing Angular code.
When editing a script, WebStorm automatically imports the required JavaScript modules so you don't have to import them manually.
If you open up the TypeScript panel, WebStorm provides you with immediate feedback on the validity of your code, so you can quickly resolve issues before having to compile your project.
Watch how the OnInit interface is automatically imported and how the live TypeScript feedback immediately tells you whether or not your TypeScript code is valid:
When you edit a template, WebStorm provides you with smart code completion that recognizes components, directives and even input and output properties:
With Angular Language Service enabled, WebStorm is able to improve code completion in template expressions:
… and report template errors more precisely right inside your editor:
Catching errors without having to compile your project saves you incredible amounts of time.
Don't worry about formatting your code manually. WebStorm has you covered.
Whether your are in a template, a script, a stylesheet or even a JSON file, just hit cmd-option-L and WebStorm will automatically format all code for you:
Continue reading %Top 12 Productivity Tips for WebStorm and Angular – Part 1%
The following is a short extract from our new book, Researching UX: User Research, written by James Lang and Emma Howell. It's the ultimate guide to user research, a key part of effective UX design. SitePoint Premium members get access with their membership, or you can buy a copy in stores worldwide.
Once you’ve decided who you want to include in the research, and defined it in a recruitment brief, you’ll need a way to ensure that you’re actually getting those people. There are two ways to do this.
There are pros and cons to both approaches. Evaluating against the recruitment brief can be inaccurate, risking misleading results and undermining the credibility of your project. On the other hand, a screener takes additional time to create and apply.
There are some workarounds. If you hire a recruitment agency, they will often write the screener on your behalf. If you’re conducting guerrilla research, the screener will be very short. We’ll say more about both of these scenarios later in the chapter.
A screener is a set of questions that are asked to potential participants, based on the sample criteria you defined in your recruitment brief. These questions are designed to figure out how suitable participants are for your project.
You can see an example screener here, showing the key questions you would want to ask to recruit for a project about outdoor gear. It establishes what activities the potential participants do without leading them to give certain answers. The other questions are written to probe more into their experiences and habits when buying outdoor equipment, without being leading. The final question is written to catch out anyone that is trying to trick their way onto the research.
Screener questions contain several elements:
Continue reading %How to Conduct User Research: Getting the Right People%
My Introduction to Component IO article described how you could use pre-built components on any site regardless of the Content Management System, languages, or technologies used. The benefits include:
Despite the huge range available, Component IO permits developers to create and edit their own components. In this tutorial, I will illustrate how to create a simple custom bar chart component which can be displayed and configured on any site:
Component IO uses the Vue.js component model. Those with experience with the framework will immediately recognize the concepts and syntax. That said, I'm no Vue.js expert — but a little HTML, CSS and JavaScript knowledge is enough to build a complex component.
All components are encapsulated; their styles and code cannot 'leak' to other parts of the page. For example, the bar chart component's title is an H2 element and we can apply any styles, e.g.
h2 {
font-family: comic-sans;
font-size: 8em;
color: #f00;
}
Vue.js will ensure those (awful!) styles are only applied to our component and not H2 headings elsewhere on the page. However, a style applied to all H2 titles on the page can cascade to our component title. This can be useful since our component can inherit default fonts, colors and dimensions.
Log in to component.io, and then click Blank component on the Project page:
From the Edit menu, choose Edit component name and enter "barchart" or another suitable name.
Fields are used to configure a component. They allow:
From the Edit menu, choose Add / remove fields and enter the fields you require:
For this control, I defined:
These last three items had the repeat checkbox checked. We can therefore define any number of data items in our bar chart.
Hit the Edit menu to open the Content and Code control. Remaining in the Content section, I entered values for the title and three data items:
Hit the Code toggle to open the code editor. This is where the component's HTML, CSS and JavaScript is defined:
The component HTML documentation describes how templates are created. There is no need for an outer DIV or other element because the component will be automatically given one.
The title field is added first:
<h2 v-text="title"></h2>
Alternatively, we could use:
<h2></h2>
The chart bars will be contained in a <ul> list element where each <li> displays a single value. The HTML code:
Continue reading %How to Create Custom Components Using Component IO%