ERPAL is the Drupal distribution to manage your company's projects and business processes. With the ERPAL distribution you build ONE plattform for MANY tools to manage your data, workflows, teams and projects of your company. Find more information about the features of ERPAL at http://drupal.org/project/erpal
After a quick recap of the changes you need to make to port your JS to Drupal 8, we'll dig into the changes you should embrace as a module maintainer or site developer to make your life, and the web, better.
You hand over a site that you have just built to your client and then… the phone is ringing…
You: Hello, how can I help you?
Customer: I can't login to my site.
You: Are you sure you used the right password?
Customer: Yes, I'm sure. I saw my colleague do it.
You: Can you tell me what the password was?
Customer: Five stars.
If this is the most polite thought that crossed your mind while dealing with the Drupal 7 Field API, you want to attend this session. You will learn how much we improved the Entity and Field systems in Drupal 8 with respect to language and multilingual support. By covering everything from the design concepts behind the new functionalities and APIs to the new storage layer and the related query system, this session will help you transition smoothly to the shiny D8 multilingual world.
Security is paramount, for almost any web application. We will take a look at security best practices to keep your site safe and take the perspective of an attacker to understand how they exploit things. I will show you common mistakes that Drupal Developers make when they write code and how they can be avoided. As a member of the security team and code review administrator on drupal.org I have seen a lot of code and what can go wrong with it.
Sharing my experience about:
With Drupal you can have several languages on one site. Everything can be translated: Content, Strings, Menus, Taxonomy terms, you name it! That's fantastic.
But when you go beyond a few dozen nodes, the overview is lost pretty fast. The state of translation of a Drupal installation is not really transparent. And there is no administrative interface for guiding the translation process.
A project manager talks to the development team...
'Sorry guys, the design is not yet approved, but we need to start implementing. Can we just start with what we have and hope it will not change too much?'
'Hi guys, can we still implement this one change request? I promise it is the last one…'
'Sorry, the client didn't test well, so that is why we have all these bugs online that we need to fix asap…'
Does that sound familiar to you?
Content editors are amongst the most important but the most forgotten stakeholders in a CMS project.
They are the ones producing all the content years over years. You can help them creating high-quality content, to be efficient and to make them raise improvements for further developments.
What is Bassets?
Bassets (Better Assets) is a client-server solution for storing and managing of digital assets (pictures, videos etc.).
So Bassets consists of 2 Drupal distributions:
At Aral Balkan's DrupalCon keynote he spoke about Experience Driven Open Source and the need to be able to choose who stores are data for us.
Online friending / following basically boils down to categorizing email addresses (the primary key of identity). We want to be able to categorize identities anywhere and take them with us.
Currently Facebook will not let you bring your data to a startup it doesn't like. The only organisation that implements Facebook's APIs is Facebook. You can't decide who you want to store this data for you.