Working group

A sub community within Drupal for the users of Janrain to discuss the module space, and the way that we can grow and empower other community members within this space.

The purpose of this group is to collectively gather, analyse and discuss the findings that have been done in Academia about the Drupal community, and what can we learn as a community from them. It will also act as a meeting point for those who are interested in the study of the Drupal community, so we can put a face to the names and explore how to collaborate and coordinate.

This initiative was born as part of the the BoF session at DrupalCon Amsterdam (https://amsterdam2014.drupal.org/bof/study-drupal-community-academia-wha...).

Extend the functionality of the async Drupal distribution https://www.drupal.org/project/async_drupal and the nodejs integration module to https://www.drupal.org/project/nodejs to enable proliferation of events and actions to multiple subscribers. At the time of writing the interaction between node.js and rules is limited to updating views and showing rules notifications on multiple subscribers.

Necessito de gravar as informações de um formulário em um serviço Rest externo. No drupal ficaria apenas o HTML (tela) , mas as informações de conteudo em servidor externo.

Realizei alguns testes mas todos com algumas limitações:

1) Criação no formulário no CCK e utilizando RULES para pegar as informações da tela e realizar a chamada do serviço REST Post externo.
Problema: As informações da tela ficam duplicadas no drupal e no servidor externo.

2) Criação de módulo personizado e a chamada submit do serviço Rest.
Problema: Teria que criar um módulo específico para cada formulário.

This group is for Drupal Mumbai leadership board and also for those who are directly involved in organizing and conducting the events in Drupal Mumbai.

A graph database is a kind of NoSQL database that uses graph structures with nodes, edges, and properties to represent and store information.

We will talk in this group about the different approaches on how to store information from Drupal entities in such a database.

On of the topics will be Neo4j. Neo4j is a graph database, reliable and fast for managing and querying highly connected data. http://www.neo4j.org

This group was started to aggregat all the discussion into one place and invite as many people to join and together to find the best approach:

Related module:

<

ul>

Drupal için seo çalışmaları grubu türkçe bilgi kaynağı.

We want Drupal to be the CMS of choice for client-side MVC frameworks.

We want an API for renderable structure and context-aware template-driven JSON representations of pages.

The intention of this working group is to discuss how Drupal core should change for the ability for many different presentation layers to interact with Drupal, especially client-side frameworks, not just Drupal's own theme system.

We are working on drafting a manifesto on GitHub.

Drupal's complexity often creates a major barrier to entry, and contributes to widespread misinformation about the platform. To add to this, finding usable information can be daunting. To solve this, we should be reaching out to new users who come to Drupal.org with use cases, quick starts, and gamification of achievements in order to make the community more approachable and to encourage more participation.