Stop Using Native HTML5

Kyle Simpson advises on accessing HTML5 or JavaScript native APIs though a façade built with h5ive that would protect the application code from evolving API changes over the following years. 
Stop Using Native HTML5

Ruby On Rails State of Practice: Deployment and Management

Rails developers can draw from a huge pool of libraries to build their applications. Dozens of options are available just for templating: do you use ERB, HAML, SASS, or do you prefer a JavaScript approach with Backbone.js or Knockout.js? The possibilities are endless, so we want to find out what our readers are using, or planning to use in the future.
Ruby On Rails State of Practice: Deployment and Management

Top JavaScript MVC Frameworks

As more and more logic ends up being executed in the browser, JavaScript front-end codebases grow larger and more difficult to maintain. As a way to solve this issue developers have been turning to MVC frameworks which promise increased productivity and maintainable code. As part of the new community-driven research initiative, InfoQ is examining the adoption of such frameworks and libraries by developer
Top JavaScript MVC Frameworks

Introduction to Entando Architectural Model

Hi guys,

today I present to you the last post published on the blog Entando:

Entando architectural model is composed by three layers:

• Data Access Layer: It is composed by all the elements which superintend the Persistence Layer. The main component are the DAO classes (Data Access Object) which are the only linking element between the framework and the data sources (Database, Filesystem, LDAP service directory etc.)

• Business Layer: This is the core of the system. Here the concept of Entando service as manager of every macro functionality, takes place. This layer is built upon the Spring Framework, whose listener, during the system start-up, initializes all the services and injects them in the web application context as beans. The Business Layer utilizes the Data Access layer to get the data needed, gives to the higher layer (the Presentation layer) the elements to display and supports it in the execution of actions.

• Presentation Layer: the aim of this layer is to build the graphic interfaces which represent the mean through which the users interact with the system. This layer gives a pure View layer (that is, a JSP without any business logic) and a "slim" controller (which checks the consistency of the data submitted and serves the data produced); both of them provide support to the layer below, the Business Layer. In the Entando framework this layer is divided in two parts:

             - the Portal View, referred to as Front-end
             - the Administration View referred to as Back-end

read more. 

How To Test Your Landing Pages

Infographic by- Invesp