DRY (Don't repeat yourself) is a principle of software development, have you hear about that? Sometimes on Drupal while we are developing a custom module, there are some common tasks, features that we probably need to implement, instead of create our custom solutions, what if I told you that Drupal provides, let's say, a toolbox with common functions and useful classes to make our lives easier.
I would like to share my experience on the last time I implemented the Migration API on Drupal 8, a heads-up before jumping to write code: keep calm. This topic might looks overwhelming on first sight, what I hightlight recommend you to take one step back, relax and prepare yourself to read in order to understand how it works.
Migration API is described as a process which extracts data from a source, then transforms the given data to load it into a destination:
Angular 2 Entity is a module that provides the ability to expose Drupal entities as Angular 2 components through Entity Display Modes and Progressive Decouple Blocks (PDB) contributed module, cool, isn't it? But how could we see an implementation of that? In this case, we now go through an example by using this module and creating a view to expose all our articles as Angular 2 components. Let's get start it!
On web security we need to be two steps ahead, then if we expose any resource or path we should not trust that any request is coming from our page. Drupal implements token validation to achieve that, on this page we walk through on a simple example about how do that.
Basically we should use two functions that Drupal provides us,
Drupal give us an excellent documentation about how to setup our settings file, but what about if we are developing our site using a local environment, what shall we know? which are the best practice that we must keep in mind.