Aucune remarque pour cette diapositive
Bonjour nous sommes heureux d ’être ici avec vous pour officialiser le lancement d’Acquia en France! En effet, Tout le monde attendait ce moment, Les clients nous attendaient Les partenaires nous attendaient La communauté nous attendaient Afin que nous puissions les supporter et les accompagner pour assurer le Succès des projets Drupal, ..
CMO : Mobile optimized experiences Harness social media Mass personalization / testing Translation Managing digital assets Marketing dashboards / reporting CTO : Mobile app development Big data / web scale Increase return from analytics Localization costs / quality Content distribution services Platform integration / ecosystem
Interwoven now HP
Interwoven now HP
The problem every business and marketer is trying to accomplish in their communications is simple, but the explosion of content, tools, and channels makes that goal harder and harder. CMO Mobile optimized experiences Harness social media Mass personalization / testing Translation Managing digital assets Marketing dashboards / reporting CTO Mobile app development Big data / web scale Increase return from analytics Localization costs / quality Content distribution services Platform integration / ecosystem
The drupal world has 1.5M.
However, we ’ re only a small planet in this universe! Drupal sites make up only 6.7% of all CMS sites Drupal as a platform vision Data from here: http://w3techs.com/technologies/overview/content_management/all
Did you know that only 30% of all websites are built on CMS platform?
5th technology cycle
Drupal is leading the change for management of dynamic content in the enterprise. Today it powers circa 2% of the web. The most recent release of Drupal, Drupal 7, had almost 1000 contributors to Drupal core. There were thousands more who submitted patches that were not incorporated. Arguably, Drupal shares with Linux the title of “most active open source projects”. In fact, Drupal has twice the number of developers who’ve contributed code as the Linux project (linux had 8,000 contributors since 2005, according to the Linux foundation in 2011) Drupal wins because it offers: Shorter innovation cycles Faster time to market via assembly of modules More flexibility .. Want a slightly different behavior … you can ameliorate a module yourself or with a partner No vendor lock in Better total cost of ownership Acquia is the leading player commercializing Drupal, much in the same way that Red Hat commercialized Linux. Dries Buytaert, the founder and project lead of Drupal, is also Acquia ’s founder and CTO. Dries’ co-maintainers for the last two Drupal versions are also members of our team. We lead the community in many ways, from design to thought leadership to writing the code, yet we’re able to leverage the community broadly, where roughly 90% of the code is written.
Drupal is composed of functional components known as modules, and was designed from the get-go to support great extensibility. In fact, the Drupal community regularly “absorbs” contributed modules (created on top of CORE Drupal), making them part of Drupal’s next major platform release. Innovation in the Drupal community works like this: Individual community members identify new functional requirements for their Drupal sites, typically based on their own needs. He or she develop and contribute a new module to the project based on those needs. If others share this requirement, they will investigate and use the module, often contributing patches and bug fixes, along with new capabilities, to improve the module. The more popular a module becomes, the faster it improves in quality - to the benefit of everyone who uses it. If a module becomes popular, or valuable enough, it may be considered for inclusion in a future release of Drupal core. This virtuous cycle of informal, networked collaboration is what drives innovation in the Drupal community, and on the web. Drupal core consists of approx. 30 such modules, which have been created, managed, and maintained by approx 800 community contributors. On top of Drupal core, there are at this time over 7,000 contributed modules -- from approx. 5000 contributors. Drupal.org hosts a testing environment with over 30,000 test to ensure the stability of core and contributed modules And Drupal is designed around a hook system which makes it possible for your developers to “override” module behavior to meet your organizations custom needs.
With that, Drupal is emerging as a new standard for managing integrated customer experiences. Drupal was born 10 years ago as a social publishing tool, and quickly evolved to become a robust web development platform that covers the full gamut of content, community, and commerce experiences. It has an architecture that allows it to treat content as individual objects that can be delivered in whatever context you choose, and has a flexible front end that lets it output to one or many distinct web experiences. You see drupal used as often for headless experiences where it is simply feeding applications and rich media as you see it being used for traditional web experiences.
[This slide builds] Core to Drupal ’s success since the project’s first release in 2001 has been an extremely elegant information architecture. Drupal manages information of all kinds in the form of “nodes.” Content on Drupal sites are almost always composed of multiple “nodes,” e.g.: a product description - text a product image - jpeg file related product catalog information Because these atomic elements are managed separately by Drupal, site developers can assemble them in many ways and generate new user experiences easily. Administrators can also create custom content types -- to supplement a raw node with information which makes the content useful and meaningful to people. --- Raw nodes including text content can become “blog posts,” for example, by including information identifying the author, and a date for publication. A node including a reference to an MP3 file can be converted into an “album tracks” with the inclusion of information identifying the artist, the title, the producer, and the date of publication. --- Content in Drupal can be “referenced.” Examples: Users can create a comment, which is associated with a specific blog post; or they can add a vote or a tag to a product description page. As we will see in a moment, this type of content is used in conjunction with roles and permissions to enable a broad range of social publishing capabilities. --- Finally, Drupal gives site designers and administrators great flexibility over how site content is presented to users through “views.” Views provide a powerful capability to query content stored in Drupal nodes, and to present that content to users in meaningful ways. Views can be used to do everything from creating simple, reverse-chronological lists of blog post titles, to creating a rich display of music track thumbnails ordered by average “star rating” based on user voting, to RSS feeds, navigational blocks and much more.
[this slide builds] Drupal provides an elegant user management framework which makes new, interesting types of social engagement on the web possible. --- Users can be “anonymous,” or they can have a profile on a Drupal site and become authenticated users. Authenticated users can be organized into groups, known as roles. As a simple example, anonymous users might be plain readers of public content on a Drupal site, while users in the “authors” role might be able to create new pages or blog posts on the site. Another group of users might be “editors.” --- Author permissions might only grant users with that role access to public content, plus the pages or posts they have themselves created. --- Editors, on the other hand, might have permissions giving them access to see all contributed pages and posts, and to update the content of those pages and posts. Furthermore, perhaps only editors have the right to set a custom field like “publication time,” which would specify when the content would go live on the web site. --- All of these are configurable by the site administrator, and completely customizable. The ability to create custom roles, and to define very specific access control permissions based on those roles, makes great social sites possible. It is simple to define a role such as “Visitor.” Visitors would like to comment on blog posts -- so they create a Drupal log-in, but that role’s permissions may give them only the right to add comments to blog posts. “Customers” might be granted a different custom role, which would entitle them to add content ratings to product pages. These ratings might be visible to “Product Managers,” but invisible to “Visitors.” Suddenly very rich interactive experiences can be offered to visitors, all in accordance with the access appropriate to them individually.
But it ’s not enough to have a solid architecture. The experience for marketers and site owners to be able to craft those experiences must be simple and elegant. Early versions of Drupal were primarily developer tools, and had the UI to prove it. That changed dramatically in Drupal 7, and Acquia has taken it even further by taking cues from some of the best web experience design tools in the commercial space and bringing them into the Drupal UI. Now, users can select and design content components, mash them up and arrange them into the experiences they desire, and deploy them to a plethora of devices – all without the help of a Developer.
9 h 30 à 9 h 45 Introduction , Cyril Reinhard, Directeur Acquia France Acueil: remerciement public et partenaires Agenda Acquia Key Figure La france Intro avec Dries 9 h 45 à 10 h 30 Vision et le Futur de Drupal . Dries Buytaert, créateur de Drupal et directeur technique d ’Acquia, partagera sa vision et vous parlera de l’évolution de Drupal, ainsi que de son orientation pour 2012 et dans les années à venir. 10 h 30 à 11 h Étude de cas client - Radio France 11 h à 11 h 30 Pause café et exposition des partenaires 11 h 30 à 12 h 10 Bonnes pratiques. Comment gérer une expérience utilisateur Multi-canal et personnalisée, Comment industrialiser la création et gestion de sites. 12 h 10 à 12 h 30 Acquia France. Une équipe, des Partenaires, une communauté pour vous accompagner sur vos projets. Cyril Reinhard, Directeur Acquia France 12 h 30 à 13 h Débat et session de questions-réponses 13 h à 14 h 30 Buffet et échanges
Based in Orlando with 7 hospitals and more than 30 care centers, Florida Hospital is America ’s #1 hospital for inpatient admissions. The #1 reason visitors come to floridahospital.com is to locate the nearest emergency room facility. Using open source Drupal, every visitor can prominently see, in the Red Bar, both a list of nearby emergency rooms, in order of location proximity to the site visitor, but also the current wait time at that facility. This valuable information, delivered anywhere their customers are located, helps FH improve their overall patient experience.
Acquia a été créée dans un objectif «Etre le guide Drupal des Entreprises» LA communauté est l ’une des plus importante et plus productives, et il manquait un Editeur pour la soutenir et supporter des projets toujours plus ambitieux. Les entreprises et administrations avaient et ont besoin d ’être rassurées sur la pérennité et l’avenir de Drupal et sa communauté, de pouvoir intégrer dans leur stratégie Digital sur le moyen et le long terme la Plateforme Drupal (Services Acquia, Partenaires) et c’est la raison pour laquelle le rôle d’Acquia pour soutenir les partenaires et la communauté est primordiale. Pourquoi la France, La France est très active dans l ’Open Sorce et très consommatrice de Drupal, et ont y trouve des projets de plus en plus importats, et notre rôle à tous et d’en assurer le succès, car le succès des projets d’aujourd’hui fera le le succès des projets de demain