�ݺ�ߣshows by User: hernanibf

�ݺ�ߣshows by User: hernanibf / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: hernanibf / Thu, 13 Sep 2018 06:26:07 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: hernanibf Drupal Europe 2018: Hackers automate but the drupal community still downloads modules from drupal.org /slideshow/drupal-europe-2018-hackers-automate-but-the-drupal-community-still-downloads-modules-from-drupalorg/114208018 presentationtalk-hackersautomatebutthedrupalcommunity-180913062607
“Automatic Updates for Drupal” was, is and will be a matter of debate. In this open discussion, we want to welcome everyone who wants to learn more about the current state of update processes within the Drupal Community, and especially about possible future scenarios in Drupal. We welcome everyone who’s interested in joining the discussion about auto update possibilities and bringing in critical reflections.]]>
“Automatic Updates for Drupal” was, is and will be a matter of debate. In this open discussion, we want to welcome everyone who wants to learn more about the current state of update processes within the Drupal Community, and especially about possible future scenarios in Drupal. We welcome everyone who’s interested in joining the discussion about auto update possibilities and bringing in critical reflections.]]> Thu, 13 Sep 2018 06:26:07 GMT /slideshow/drupal-europe-2018-hackers-automate-but-the-drupal-community-still-downloads-modules-from-drupalorg/114208018 hernanibf@slideshare.net(hernanibf) Drupal Europe 2018: Hackers automate but the drupal community still downloads modules from drupal.org hernanibf “Automatic Updates for Drupal” was, is and will be a matter of debate. In this open discussion, we want to welcome everyone who wants to learn more about the current state of update processes within the Drupal Community, and especially about possible future scenarios in Drupal. We welcome everyone who’s interested in joining the discussion about auto update possibilities and bringing in critical reflections. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/presentationtalk-hackersautomatebutthedrupalcommunity-180913062607-thumbnail.jpg?width=120&height=120&fit=bounds" /> “Automatic Updates for Drupal” was, is and will be a matter of debate. In this open discussion, we want to welcome everyone who wants to learn more about the current state of update processes within the Drupal Community, and especially about possible future scenarios in Drupal. We welcome everyone who’s interested in joining the discussion about auto update possibilities and bringing in critical reflections.

Drupal Europe 2018: Hackers automate but the drupal community still downloads modules from drupal.org from hernanibf

]]> 838 4 https://cdn.slidesharecdn.com/ss_thumbnails/presentationtalk-hackersautomatebutthedrupalcommunity-180913062607-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Aiming for automatic updates - Drupal Dev Days Lisbon 2018 /slideshow/aiming-for-automatic-updates-drupal-dev-days-lisbon-2018/104399306 aimingddd-180705173810
Drupal recents security updates resulted in many hours of work for different professionals involved in maintenance of Drupal websites from developers to operations teams. New Drupal 8 release cycle is also requiring organisations to spend more time guaranteeing that their websites are following last minor core release so their sites are updated and ready to receive new features and security updates. Nevertheless, even with the increasing required effort, we still don’t have an easy way to support automatic updates in Drupal core but options start to appear. In this session I will talk about different possible alternatives that can minimize the effort to automatically update Drupal while still maintaining best practices in all the required phases.]]>
Drupal recents security updates resulted in many hours of work for different professionals involved in maintenance of Drupal websites from developers to operations teams. New Drupal 8 release cycle is also requiring organisations to spend more time guaranteeing that their websites are following last minor core release so their sites are updated and ready to receive new features and security updates. Nevertheless, even with the increasing required effort, we still don’t have an easy way to support automatic updates in Drupal core but options start to appear. In this session I will talk about different possible alternatives that can minimize the effort to automatically update Drupal while still maintaining best practices in all the required phases.]]> Thu, 05 Jul 2018 17:38:10 GMT /slideshow/aiming-for-automatic-updates-drupal-dev-days-lisbon-2018/104399306 hernanibf@slideshare.net(hernanibf) Aiming for automatic updates - Drupal Dev Days Lisbon 2018 hernanibf Drupal recents security updates resulted in many hours of work for different professionals involved in maintenance of Drupal websites from developers to operations teams. New Drupal 8 release cycle is also requiring organisations to spend more time guaranteeing that their websites are following last minor core release so their sites are updated and ready to receive new features and security updates. Nevertheless, even with the increasing required effort, we still don’t have an easy way to support automatic updates in Drupal core but options start to appear. In this session I will talk about different possible alternatives that can minimize the effort to automatically update Drupal while still maintaining best practices in all the required phases. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/aimingddd-180705173810-thumbnail.jpg?width=120&height=120&fit=bounds" /> Drupal recents security updates resulted in many hours of work for different professionals involved in maintenance of Drupal websites from developers to operations teams. New Drupal 8 release cycle is also requiring organisations to spend more time guaranteeing that their websites are following last minor core release so their sites are updated and ready to receive new features and security updates. Nevertheless, even with the increasing required effort, we still don’t have an easy way to support automatic updates in Drupal core but options start to appear. In this session I will talk about different possible alternatives that can minimize the effort to automatically update Drupal while still maintaining best practices in all the required phases.

Aiming for automatic updates - Drupal Dev Days Lisbon 2018 from hernanibf

]]> 453 3 https://cdn.slidesharecdn.com/ss_thumbnails/aimingddd-180705173810-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Deployer - Deployment tool for PHP /slideshow/deployer-deployment-tool-for-php-82108557/82108557 deployer-171115144608
Deployer is a php tool that can be used to deploy Php applications. Presentation provided at phplx november in Lisbon.]]>
Deployer is a php tool that can be used to deploy Php applications. Presentation provided at phplx november in Lisbon.]]> Wed, 15 Nov 2017 14:46:08 GMT /slideshow/deployer-deployment-tool-for-php-82108557/82108557 hernanibf@slideshare.net(hernanibf) Deployer - Deployment tool for PHP hernanibf Deployer is a php tool that can be used to deploy Php applications. Presentation provided at phplx november in Lisbon. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/deployer-171115144608-thumbnail.jpg?width=120&height=120&fit=bounds" /> Deployer is a php tool that can be used to deploy Php applications. Presentation provided at phplx november in Lisbon.

Deployer - Deployment tool for PHP from hernanibf

]]> 1131 1 https://cdn.slidesharecdn.com/ss_thumbnails/deployer-171115144608-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Intro to drupal /slideshow/intro-to-drupal-65695476/65695476 introtodrupal-160905101543
Intro to Drupal talk presented in phplx meetup, August 3rd in Lisbon]]>
Intro to Drupal talk presented in phplx meetup, August 3rd in Lisbon]]> Mon, 05 Sep 2016 10:15:43 GMT /slideshow/intro-to-drupal-65695476/65695476 hernanibf@slideshare.net(hernanibf) Intro to drupal hernanibf Intro to Drupal talk presented in phplx meetup, August 3rd in Lisbon <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/introtodrupal-160905101543-thumbnail.jpg?width=120&height=120&fit=bounds" /> Intro to Drupal talk presented in phplx meetup, August 3rd in Lisbon

Intro to drupal from hernanibf

]]> 959 2 https://cdn.slidesharecdn.com/ss_thumbnails/introtodrupal-160905101543-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Drupal architectures for flexible content - Drupalcon Barcelona /slideshow/drupal-architectures-for-flexible-content-drupalcon-barcelona/53113727 dcon-barcelona-150923144859-lva1-app6891
We got to the point where the old Drupal mantra of creating content first to see it later is not enough to suceed with content editors. Drupal is competing and replacing other CMS and platforms where the lack of flexibility is the problem #1 for content editors. They are expecting full flexibity on how content is created, displayed, approved and published. However this introduce a common problem for web developers and site builders: how can you provide this full flexibility without having to be constantly on the hook for further development or configuration. Modules like panels and panelizer, projects like Spark and distributions like panopoly and demo framework helped change the panorama in Drupal and the expectations that are set when sites are built. In this session we will look to a set of common problems and real examples when creating content and layout for pages with demanding editorial teams. We will look and evaluate common options and recipes. How can complex content and rich pages be structured ? Free HTML format in different fields? Structured data in complex fields? Use paragraphs or field collection? Different content items in different items/entities? How to glue it all together? How can indivual page layout be managed providing flexibility but also control? Rely on templating system and view modes? Use contrib modules like panels and panelizer or display suite? Mix several approaches and modules? How can I add any content to any page and choose its display ? How can I have a list of curated widgets ready to use by the content team to deploy anywhere or in any section? How can pages and sections be managed before approved and published? Use preview systems and inline editors? Use workbench or workflow for layout? Rely on more complex content staging systems? Use separated environments? These are daily problems that architects and developers face in every project. As a technical architect in Acquia it is uncommon a project where I am involved that does not need to solve one or more of these problems. In this session I will give some real examples and resume options and recipes that can be used to solve those problems today in Drupal 7 and look to Drupal 8 to explain how it can improve some of our possibilities and options and easy the life of one of our most important personas: the content editor.]]>
We got to the point where the old Drupal mantra of creating content first to see it later is not enough to suceed with content editors. Drupal is competing and replacing other CMS and platforms where the lack of flexibility is the problem #1 for content editors. They are expecting full flexibity on how content is created, displayed, approved and published. However this introduce a common problem for web developers and site builders: how can you provide this full flexibility without having to be constantly on the hook for further development or configuration. Modules like panels and panelizer, projects like Spark and distributions like panopoly and demo framework helped change the panorama in Drupal and the expectations that are set when sites are built. In this session we will look to a set of common problems and real examples when creating content and layout for pages with demanding editorial teams. We will look and evaluate common options and recipes. How can complex content and rich pages be structured ? Free HTML format in different fields? Structured data in complex fields? Use paragraphs or field collection? Different content items in different items/entities? How to glue it all together? How can indivual page layout be managed providing flexibility but also control? Rely on templating system and view modes? Use contrib modules like panels and panelizer or display suite? Mix several approaches and modules? How can I add any content to any page and choose its display ? How can I have a list of curated widgets ready to use by the content team to deploy anywhere or in any section? How can pages and sections be managed before approved and published? Use preview systems and inline editors? Use workbench or workflow for layout? Rely on more complex content staging systems? Use separated environments? These are daily problems that architects and developers face in every project. As a technical architect in Acquia it is uncommon a project where I am involved that does not need to solve one or more of these problems. In this session I will give some real examples and resume options and recipes that can be used to solve those problems today in Drupal 7 and look to Drupal 8 to explain how it can improve some of our possibilities and options and easy the life of one of our most important personas: the content editor.]]> Wed, 23 Sep 2015 14:48:59 GMT /slideshow/drupal-architectures-for-flexible-content-drupalcon-barcelona/53113727 hernanibf@slideshare.net(hernanibf) Drupal architectures for flexible content - Drupalcon Barcelona hernanibf We got to the point where the old Drupal mantra of creating content first to see it later is not enough to suceed with content editors. Drupal is competing and replacing other CMS and platforms where the lack of flexibility is the problem #1 for content editors. They are expecting full flexibity on how content is created, displayed, approved and published. However this introduce a common problem for web developers and site builders: how can you provide this full flexibility without having to be constantly on the hook for further development or configuration. Modules like panels and panelizer, projects like Spark and distributions like panopoly and demo framework helped change the panorama in Drupal and the expectations that are set when sites are built. In this session we will look to a set of common problems and real examples when creating content and layout for pages with demanding editorial teams. We will look and evaluate common options and recipes. How can complex content and rich pages be structured ? Free HTML format in different fields? Structured data in complex fields? Use paragraphs or field collection? Different content items in different items/entities? How to glue it all together? How can indivual page layout be managed providing flexibility but also control? Rely on templating system and view modes? Use contrib modules like panels and panelizer or display suite? Mix several approaches and modules? How can I add any content to any page and choose its display ? How can I have a list of curated widgets ready to use by the content team to deploy anywhere or in any section? How can pages and sections be managed before approved and published? Use preview systems and inline editors? Use workbench or workflow for layout? Rely on more complex content staging systems? Use separated environments? These are daily problems that architects and developers face in every project. As a technical architect in Acquia it is uncommon a project where I am involved that does not need to solve one or more of these problems. In this session I will give some real examples and resume options and recipes that can be used to solve those problems today in Drupal 7 and look to Drupal 8 to explain how it can improve some of our possibilities and options and easy the life of one of our most important personas: the content editor. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/dcon-barcelona-150923144859-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds" /> We got to the point where the old Drupal mantra of creating content first to see it later is not enough to suceed with content editors. Drupal is competing and replacing other CMS and platforms where the lack of flexibility is the problem #1 for content editors. They are expecting full flexibity on how content is created, displayed, approved and published. However this introduce a common problem for web developers and site builders: how can you provide this full flexibility without having to be constantly on the hook for further development or configuration. Modules like panels and panelizer, projects like Spark and distributions like panopoly and demo framework helped change the panorama in Drupal and the expectations that are set when sites are built. In this session we will look to a set of common problems and real examples when creating content and layout for pages with demanding editorial teams. We will look and evaluate common options and recipes. How can complex content and rich pages be structured ? Free HTML format in different fields? Structured data in complex fields? Use paragraphs or field collection? Different content items in different items/entities? How to glue it all together? How can indivual page layout be managed providing flexibility but also control? Rely on templating system and view modes? Use contrib modules like panels and panelizer or display suite? Mix several approaches and modules? How can I add any content to any page and choose its display ? How can I have a list of curated widgets ready to use by the content team to deploy anywhere or in any section? How can pages and sections be managed before approved and published? Use preview systems and inline editors? Use workbench or workflow for layout? Rely on more complex content staging systems? Use separated environments? These are daily problems that architects and developers face in every project. As a technical architect in Acquia it is uncommon a project where I am involved that does not need to solve one or more of these problems. In this session I will give some real examples and resume options and recipes that can be used to solve those problems today in Drupal 7 and look to Drupal 8 to explain how it can improve some of our possibilities and options and easy the life of one of our most important personas: the content editor.

Drupal architectures for flexible content - Drupalcon Barcelona from hernanibf

]]> 1339 6 https://cdn.slidesharecdn.com/ss_thumbnails/dcon-barcelona-150923144859-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Drupal content editor flexibility /slideshow/drupal-content-editor-flexibility/48534913 drupalcamp-spain-2015-150524103901-lva1-app6892
We got to the point where the old Drupal mantra of creating content first to see it later is not enough to suceed with content editors. Drupal is competing and replacing other CMS and platforms where the lack of flexibility is the problem #1 for content editors. They are expecting full flexibity on how content is created, displayed, approved and published. However this introduce a common problem for web developers and site builders: how can you provide this full flexibility without having to be constantly on the hook for further development or configuration. Modules like panels and panelizer, projects like Spark and distributions like panopoly and demo framework helped change the panorama in Drupal and the expectations that are set when sites are built. In this session we will look to a set of common problems and real examples when creating content and layout for pages with demanding editorial teams. We will look and evaluate common options and recipes. - How can complex content and rich pages be structured ? Free HTML format in different fields? Structured data in complex fields? Use paragraphs or field collection? Different content items in different items/entities? How to glue it all together? - How can indivual page layout be managed providing flexibility but also control? Rely on templating system and view modes? Use contrib modules like panels and panelizer or display suite? Mix several approaches and modules? - How can I add any content to any page and choose its display ? How can I have a list of curated widgets ready to use by the content team to deploy anywhere or in any section? - How can pages and sections be managed before approved and published? Use prewiew systems and inline editors? Use workbench or workflow for layout? Rely on more complex content staging systems? Use separated environments? These are daily problems that architects and developers face in every project. As a technical architect in Acquia it is uncommon a project where I am involved that does not need to solve one or more of these problems. In this session I will give some real examples and resume options and recipes that can be used to solve those problems today in Drupal 7 and look to Drupal 8 to explain how it can improve some of our possibilities and options and easy the life of one of our most important personas: the content editor.]]>
We got to the point where the old Drupal mantra of creating content first to see it later is not enough to suceed with content editors. Drupal is competing and replacing other CMS and platforms where the lack of flexibility is the problem #1 for content editors. They are expecting full flexibity on how content is created, displayed, approved and published. However this introduce a common problem for web developers and site builders: how can you provide this full flexibility without having to be constantly on the hook for further development or configuration. Modules like panels and panelizer, projects like Spark and distributions like panopoly and demo framework helped change the panorama in Drupal and the expectations that are set when sites are built. In this session we will look to a set of common problems and real examples when creating content and layout for pages with demanding editorial teams. We will look and evaluate common options and recipes. - How can complex content and rich pages be structured ? Free HTML format in different fields? Structured data in complex fields? Use paragraphs or field collection? Different content items in different items/entities? How to glue it all together? - How can indivual page layout be managed providing flexibility but also control? Rely on templating system and view modes? Use contrib modules like panels and panelizer or display suite? Mix several approaches and modules? - How can I add any content to any page and choose its display ? How can I have a list of curated widgets ready to use by the content team to deploy anywhere or in any section? - How can pages and sections be managed before approved and published? Use prewiew systems and inline editors? Use workbench or workflow for layout? Rely on more complex content staging systems? Use separated environments? These are daily problems that architects and developers face in every project. As a technical architect in Acquia it is uncommon a project where I am involved that does not need to solve one or more of these problems. In this session I will give some real examples and resume options and recipes that can be used to solve those problems today in Drupal 7 and look to Drupal 8 to explain how it can improve some of our possibilities and options and easy the life of one of our most important personas: the content editor.]]> Sun, 24 May 2015 10:39:01 GMT /slideshow/drupal-content-editor-flexibility/48534913 hernanibf@slideshare.net(hernanibf) Drupal content editor flexibility hernanibf We got to the point where the old Drupal mantra of creating content first to see it later is not enough to suceed with content editors. Drupal is competing and replacing other CMS and platforms where the lack of flexibility is the problem #1 for content editors. They are expecting full flexibity on how content is created, displayed, approved and published. However this introduce a common problem for web developers and site builders: how can you provide this full flexibility without having to be constantly on the hook for further development or configuration. Modules like panels and panelizer, projects like Spark and distributions like panopoly and demo framework helped change the panorama in Drupal and the expectations that are set when sites are built. In this session we will look to a set of common problems and real examples when creating content and layout for pages with demanding editorial teams. We will look and evaluate common options and recipes. - How can complex content and rich pages be structured ? Free HTML format in different fields? Structured data in complex fields? Use paragraphs or field collection? Different content items in different items/entities? How to glue it all together? - How can indivual page layout be managed providing flexibility but also control? Rely on templating system and view modes? Use contrib modules like panels and panelizer or display suite? Mix several approaches and modules? - How can I add any content to any page and choose its display ? How can I have a list of curated widgets ready to use by the content team to deploy anywhere or in any section? - How can pages and sections be managed before approved and published? Use prewiew systems and inline editors? Use workbench or workflow for layout? Rely on more complex content staging systems? Use separated environments? These are daily problems that architects and developers face in every project. As a technical architect in Acquia it is uncommon a project where I am involved that does not need to solve one or more of these problems. In this session I will give some real examples and resume options and recipes that can be used to solve those problems today in Drupal 7 and look to Drupal 8 to explain how it can improve some of our possibilities and options and easy the life of one of our most important personas: the content editor. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/drupalcamp-spain-2015-150524103901-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds" /> We got to the point where the old Drupal mantra of creating content first to see it later is not enough to suceed with content editors. Drupal is competing and replacing other CMS and platforms where the lack of flexibility is the problem #1 for content editors. They are expecting full flexibity on how content is created, displayed, approved and published. However this introduce a common problem for web developers and site builders: how can you provide this full flexibility without having to be constantly on the hook for further development or configuration. Modules like panels and panelizer, projects like Spark and distributions like panopoly and demo framework helped change the panorama in Drupal and the expectations that are set when sites are built. In this session we will look to a set of common problems and real examples when creating content and layout for pages with demanding editorial teams. We will look and evaluate common options and recipes. - How can complex content and rich pages be structured ? Free HTML format in different fields? Structured data in complex fields? Use paragraphs or field collection? Different content items in different items/entities? How to glue it all together? - How can indivual page layout be managed providing flexibility but also control? Rely on templating system and view modes? Use contrib modules like panels and panelizer or display suite? Mix several approaches and modules? - How can I add any content to any page and choose its display ? How can I have a list of curated widgets ready to use by the content team to deploy anywhere or in any section? - How can pages and sections be managed before approved and published? Use prewiew systems and inline editors? Use workbench or workflow for layout? Rely on more complex content staging systems? Use separated environments? These are daily problems that architects and developers face in every project. As a technical architect in Acquia it is uncommon a project where I am involved that does not need to solve one or more of these problems. In this session I will give some real examples and resume options and recipes that can be used to solve those problems today in Drupal 7 and look to Drupal 8 to explain how it can improve some of our possibilities and options and easy the life of one of our most important personas: the content editor.

Drupal content editor flexibility from hernanibf

]]> 1324 2 https://cdn.slidesharecdn.com/ss_thumbnails/drupalcamp-spain-2015-150524103901-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 One Drupal to rule them all - Drupalcamp London /slideshow/one-drupal-to-rule-them-all-drupalcamp-london/31845662 onedrupal-140303084647-phpapp01
Dries famous sentence (http://buytaert.net/one-drupal-to-rule-them-all) is becoming a reality for many organisations from small shops to the enterprise space. More and more stakeholders are following the idea of standardising their online presence in Drupal and leverage the same code and infrastructure amongst their different sites. What they are seeking is a drastic reduction in the time needed to create, launch and configure a Drupal site at the same time that they reduce the maintenance effort of the whole sites' network. To achieve it, a drastic change needs to happen on the standardisation of development processes, more strict control of the overall architecture while supporting new changes and requirements, and repeatable and trustable deployment process to avoid the opposite pitfall of "one site to break them all". In this session we will look to what needs to be thought when creating such an architecture from the development process to the infrastructure to host the different environments needed. We will look at different solutions that allow maintain these sites factories and walk you through several architectures explaining their advantages and differences. Finally, we will look in detail to Acquia's Cloud Site Factory, a fully-hosted SaaS solution that allows organisations to quickly deploy and manage websites by the hundreds. Pre-define site templates, create new sites in a single click, manage roles and permissions across sites and connect to existing analytics and data systems.]]>
Dries famous sentence (http://buytaert.net/one-drupal-to-rule-them-all) is becoming a reality for many organisations from small shops to the enterprise space. More and more stakeholders are following the idea of standardising their online presence in Drupal and leverage the same code and infrastructure amongst their different sites. What they are seeking is a drastic reduction in the time needed to create, launch and configure a Drupal site at the same time that they reduce the maintenance effort of the whole sites' network. To achieve it, a drastic change needs to happen on the standardisation of development processes, more strict control of the overall architecture while supporting new changes and requirements, and repeatable and trustable deployment process to avoid the opposite pitfall of "one site to break them all". In this session we will look to what needs to be thought when creating such an architecture from the development process to the infrastructure to host the different environments needed. We will look at different solutions that allow maintain these sites factories and walk you through several architectures explaining their advantages and differences. Finally, we will look in detail to Acquia's Cloud Site Factory, a fully-hosted SaaS solution that allows organisations to quickly deploy and manage websites by the hundreds. Pre-define site templates, create new sites in a single click, manage roles and permissions across sites and connect to existing analytics and data systems.]]> Mon, 03 Mar 2014 08:46:47 GMT /slideshow/one-drupal-to-rule-them-all-drupalcamp-london/31845662 hernanibf@slideshare.net(hernanibf) One Drupal to rule them all - Drupalcamp London hernanibf Dries famous sentence (http://buytaert.net/one-drupal-to-rule-them-all) is becoming a reality for many organisations from small shops to the enterprise space. More and more stakeholders are following the idea of standardising their online presence in Drupal and leverage the same code and infrastructure amongst their different sites. What they are seeking is a drastic reduction in the time needed to create, launch and configure a Drupal site at the same time that they reduce the maintenance effort of the whole sites' network. To achieve it, a drastic change needs to happen on the standardisation of development processes, more strict control of the overall architecture while supporting new changes and requirements, and repeatable and trustable deployment process to avoid the opposite pitfall of "one site to break them all". In this session we will look to what needs to be thought when creating such an architecture from the development process to the infrastructure to host the different environments needed. We will look at different solutions that allow maintain these sites factories and walk you through several architectures explaining their advantages and differences. Finally, we will look in detail to Acquia's Cloud Site Factory, a fully-hosted SaaS solution that allows organisations to quickly deploy and manage websites by the hundreds. Pre-define site templates, create new sites in a single click, manage roles and permissions across sites and connect to existing analytics and data systems. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/onedrupal-140303084647-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> Dries famous sentence (http://buytaert.net/one-drupal-to-rule-them-all) is becoming a reality for many organisations from small shops to the enterprise space. More and more stakeholders are following the idea of standardising their online presence in Drupal and leverage the same code and infrastructure amongst their different sites. What they are seeking is a drastic reduction in the time needed to create, launch and configure a Drupal site at the same time that they reduce the maintenance effort of the whole sites' network. To achieve it, a drastic change needs to happen on the standardisation of development processes, more strict control of the overall architecture while supporting new changes and requirements, and repeatable and trustable deployment process to avoid the opposite pitfall of "one site to break them all". In this session we will look to what needs to be thought when creating such an architecture from the development process to the infrastructure to host the different environments needed. We will look at different solutions that allow maintain these sites factories and walk you through several architectures explaining their advantages and differences. Finally, we will look in detail to Acquia's Cloud Site Factory, a fully-hosted SaaS solution that allows organisations to quickly deploy and manage websites by the hundreds. Pre-define site templates, create new sites in a single click, manage roles and permissions across sites and connect to existing analytics and data systems.

One Drupal to rule them all - Drupalcamp London from hernanibf

]]> 2774 2 https://cdn.slidesharecdn.com/ss_thumbnails/onedrupal-140303084647-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 One drupal to rule them all - Drupalcamp Caceres /hernanibf/one-drupal-to-rule-them-all-drupalcamp-caceres onedrupal-131027023826-phpapp01
]]>
]]> Sun, 27 Oct 2013 02:38:26 GMT /hernanibf/one-drupal-to-rule-them-all-drupalcamp-caceres hernanibf@slideshare.net(hernanibf) One drupal to rule them all - Drupalcamp Caceres hernanibf <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/onedrupal-131027023826-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" />

One drupal to rule them all - Drupalcamp Caceres from hernanibf

]]> 3209 2 https://cdn.slidesharecdn.com/ss_thumbnails/onedrupal-131027023826-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Fix me if you can - DrupalCon prague /slideshow/drupalcon-prague-fix-me-if-you-can-26540354/26540354 drupalconprague-fixmeifyoucan-130925093526-phpapp01
]]>
]]> Wed, 25 Sep 2013 09:35:26 GMT /slideshow/drupalcon-prague-fix-me-if-you-can-26540354/26540354 hernanibf@slideshare.net(hernanibf) Fix me if you can - DrupalCon prague hernanibf <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/drupalconprague-fixmeifyoucan-130925093526-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" />

Fix me if you can - DrupalCon prague from hernanibf

]]> 2840 3 https://cdn.slidesharecdn.com/ss_thumbnails/drupalconprague-fixmeifyoucan-130925093526-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 My Site is slow - Drupal Camp London 2013 /slideshow/london2013/16920366 london2013-130304082500-phpapp02
Drupal is a powerful and flexible tool to create web applications without building everything from scratch. This ability can drive developers to build complex websites without understanding what is Drupal doing behind the scenes. The majority of Drupal performance talks mostly focus in aspects like infrastructure changes, caching strategies or comparisons between modules and architectures. Unfortunately when performance problems occur, development teams also follow strategies to replace different aspects of the platform looking only to standard aspects like slow queries without understanding and profiling the real problem. The majority of times it is fundamental to measure and analyze what is the application is actually doing to understand te real problems. Drupal is a platform used by million of websites worlwide and its performance can in most cases be compared after measured. In Acquia we do dozens of performance assessments per year, and even in most clients we find the same problems, often we find situations that only can be detected when measured and analized when looking to a profiler report. In this session, I will explain how to detect performance problems looking to simple data, from logs to profiler data and providing some nice targets that can be analyzed to understand what is causing the uncommon bad performance of a site. ]]>
Drupal is a powerful and flexible tool to create web applications without building everything from scratch. This ability can drive developers to build complex websites without understanding what is Drupal doing behind the scenes. The majority of Drupal performance talks mostly focus in aspects like infrastructure changes, caching strategies or comparisons between modules and architectures. Unfortunately when performance problems occur, development teams also follow strategies to replace different aspects of the platform looking only to standard aspects like slow queries without understanding and profiling the real problem. The majority of times it is fundamental to measure and analyze what is the application is actually doing to understand te real problems. Drupal is a platform used by million of websites worlwide and its performance can in most cases be compared after measured. In Acquia we do dozens of performance assessments per year, and even in most clients we find the same problems, often we find situations that only can be detected when measured and analized when looking to a profiler report. In this session, I will explain how to detect performance problems looking to simple data, from logs to profiler data and providing some nice targets that can be analyzed to understand what is causing the uncommon bad performance of a site. ]]> Mon, 04 Mar 2013 08:25:00 GMT /slideshow/london2013/16920366 hernanibf@slideshare.net(hernanibf) My Site is slow - Drupal Camp London 2013 hernanibf Drupal is a powerful and flexible tool to create web applications without building everything from scratch. This ability can drive developers to build complex websites without understanding what is Drupal doing behind the scenes. The majority of Drupal performance talks mostly focus in aspects like infrastructure changes, caching strategies or comparisons between modules and architectures. Unfortunately when performance problems occur, development teams also follow strategies to replace different aspects of the platform looking only to standard aspects like slow queries without understanding and profiling the real problem. The majority of times it is fundamental to measure and analyze what is the application is actually doing to understand te real problems. Drupal is a platform used by million of websites worlwide and its performance can in most cases be compared after measured. In Acquia we do dozens of performance assessments per year, and even in most clients we find the same problems, often we find situations that only can be detected when measured and analized when looking to a profiler report. In this session, I will explain how to detect performance problems looking to simple data, from logs to profiler data and providing some nice targets that can be analyzed to understand what is causing the uncommon bad performance of a site. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/london2013-130304082500-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> Drupal is a powerful and flexible tool to create web applications without building everything from scratch. This ability can drive developers to build complex websites without understanding what is Drupal doing behind the scenes. The majority of Drupal performance talks mostly focus in aspects like infrastructure changes, caching strategies or comparisons between modules and architectures. Unfortunately when performance problems occur, development teams also follow strategies to replace different aspects of the platform looking only to standard aspects like slow queries without understanding and profiling the real problem. The majority of times it is fundamental to measure and analyze what is the application is actually doing to understand te real problems. Drupal is a platform used by million of websites worlwide and its performance can in most cases be compared after measured. In Acquia we do dozens of performance assessments per year, and even in most clients we find the same problems, often we find situations that only can be detected when measured and analized when looking to a profiler report. In this session, I will explain how to detect performance problems looking to simple data, from logs to profiler data and providing some nice targets that can be analyzed to understand what is causing the uncommon bad performance of a site.

My Site is slow - Drupal Camp London 2013 from hernanibf

]]> 4285 4 https://cdn.slidesharecdn.com/ss_thumbnails/london2013-130304082500-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 My site is slow /slideshow/my-site-is-slow/14847290 madrid2012-121023051305-phpapp01
Drupal is a powerful and flexible platform to build websites with rich funcionalities without building almost anything from scratch. This flexibility brought by the usage of a powerful framework and the work of a super active community can abstract people to understand what is Drupal doing behind the scenes. Most of performance talks regarding Drupal focus on aspects like infrastructure changes, caching strategies, and comparison of performance between modules or platforms. Unfortunately when performance problems occur, development teams also follow several strategies to replace several aspects in their platforms, jump directly to look for slow queries before trying really to understand where is the bottleneck. However, most of the times what really needs to be done is to look to what the application is doing and understanding why is it taking so long to do it. Drupal is a platform used by million of websites worldwide and its performance is easy to measure and compare. At Acquia we have done dozens of performance assessments, and even if we usually face the same problems, sometimes we found weird situations that are only possible to be detected when measured. Measuring and profiling is the only way to understand performance problems in a site and provide valid fixes. In this talk I will explain how to detect problems regarding performance in Drupal, using simple modules like devel, profilers like XhProf and looking to logs to understand the impact done on the application.]]>
Drupal is a powerful and flexible platform to build websites with rich funcionalities without building almost anything from scratch. This flexibility brought by the usage of a powerful framework and the work of a super active community can abstract people to understand what is Drupal doing behind the scenes. Most of performance talks regarding Drupal focus on aspects like infrastructure changes, caching strategies, and comparison of performance between modules or platforms. Unfortunately when performance problems occur, development teams also follow several strategies to replace several aspects in their platforms, jump directly to look for slow queries before trying really to understand where is the bottleneck. However, most of the times what really needs to be done is to look to what the application is doing and understanding why is it taking so long to do it. Drupal is a platform used by million of websites worldwide and its performance is easy to measure and compare. At Acquia we have done dozens of performance assessments, and even if we usually face the same problems, sometimes we found weird situations that are only possible to be detected when measured. Measuring and profiling is the only way to understand performance problems in a site and provide valid fixes. In this talk I will explain how to detect problems regarding performance in Drupal, using simple modules like devel, profilers like XhProf and looking to logs to understand the impact done on the application.]]> Tue, 23 Oct 2012 05:13:03 GMT /slideshow/my-site-is-slow/14847290 hernanibf@slideshare.net(hernanibf) My site is slow hernanibf Drupal is a powerful and flexible platform to build websites with rich funcionalities without building almost anything from scratch. This flexibility brought by the usage of a powerful framework and the work of a super active community can abstract people to understand what is Drupal doing behind the scenes. Most of performance talks regarding Drupal focus on aspects like infrastructure changes, caching strategies, and comparison of performance between modules or platforms. Unfortunately when performance problems occur, development teams also follow several strategies to replace several aspects in their platforms, jump directly to look for slow queries before trying really to understand where is the bottleneck. However, most of the times what really needs to be done is to look to what the application is doing and understanding why is it taking so long to do it. Drupal is a platform used by million of websites worldwide and its performance is easy to measure and compare. At Acquia we have done dozens of performance assessments, and even if we usually face the same problems, sometimes we found weird situations that are only possible to be detected when measured. Measuring and profiling is the only way to understand performance problems in a site and provide valid fixes. In this talk I will explain how to detect problems regarding performance in Drupal, using simple modules like devel, profilers like XhProf and looking to logs to understand the impact done on the application. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/madrid2012-121023051305-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> Drupal is a powerful and flexible platform to build websites with rich funcionalities without building almost anything from scratch. This flexibility brought by the usage of a powerful framework and the work of a super active community can abstract people to understand what is Drupal doing behind the scenes. Most of performance talks regarding Drupal focus on aspects like infrastructure changes, caching strategies, and comparison of performance between modules or platforms. Unfortunately when performance problems occur, development teams also follow several strategies to replace several aspects in their platforms, jump directly to look for slow queries before trying really to understand where is the bottleneck. However, most of the times what really needs to be done is to look to what the application is doing and understanding why is it taking so long to do it. Drupal is a platform used by million of websites worldwide and its performance is easy to measure and compare. At Acquia we have done dozens of performance assessments, and even if we usually face the same problems, sometimes we found weird situations that are only possible to be detected when measured. Measuring and profiling is the only way to understand performance problems in a site and provide valid fixes. In this talk I will explain how to detect problems regarding performance in Drupal, using simple modules like devel, profilers like XhProf and looking to logs to understand the impact done on the application.

My site is slow from hernanibf

]]> 2248 3 https://cdn.slidesharecdn.com/ss_thumbnails/madrid2012-121023051305-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Oxford DrupalCamp 2012 - The things we found in your website /slideshow/oxford-drupalcamp-2012-the-things-we-found-in-your-website/13432093 oxford2012-120623180338-phpapp01
]]>
]]> Sat, 23 Jun 2012 18:03:36 GMT /slideshow/oxford-drupalcamp-2012-the-things-we-found-in-your-website/13432093 hernanibf@slideshare.net(hernanibf) Oxford DrupalCamp 2012 - The things we found in your website hernanibf <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/oxford2012-120623180338-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" />

Oxford DrupalCamp 2012 - The things we found in your website from hernanibf

]]> 987 3 https://cdn.slidesharecdn.com/ss_thumbnails/oxford2012-120623180338-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 The things we found in your website /slideshow/porto2012/12816878 porto2012-120506062534-phpapp02
]]>
]]> Sun, 06 May 2012 06:25:32 GMT /slideshow/porto2012/12816878 hernanibf@slideshare.net(hernanibf) The things we found in your website hernanibf <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/porto2012-120506062534-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" />

The things we found in your website from hernanibf

]]> 1606 3 https://cdn.slidesharecdn.com/ss_thumbnails/porto2012-120506062534-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Acquia Commons /slideshow/acquia-commons/9500755 acquiacommons-111001102058-phpapp02
Presentation about Commons in Drupal Camp Sevilla 2011]]>
Presentation about Commons in Drupal Camp Sevilla 2011]]> Sat, 01 Oct 2011 10:20:56 GMT /slideshow/acquia-commons/9500755 hernanibf@slideshare.net(hernanibf) Acquia Commons hernanibf Presentation about Commons in Drupal Camp Sevilla 2011 <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/acquiacommons-111001102058-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> Presentation about Commons in Drupal Camp Sevilla 2011

Acquia Commons from hernanibf

]]> 2095 3 https://cdn.slidesharecdn.com/ss_thumbnails/acquiacommons-111001102058-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Drupal Performance - SerBenfiquista.com Case Study /slideshow/drupal-performance-serbenfiquistacom-case-study/5939176 drupalsb-101127183854-phpapp02
Presentation done for Drupal Meetup Porto 27th November 2010. ]]>
Presentation done for Drupal Meetup Porto 27th November 2010. ]]> Sat, 27 Nov 2010 18:38:50 GMT /slideshow/drupal-performance-serbenfiquistacom-case-study/5939176 hernanibf@slideshare.net(hernanibf) Drupal Performance - SerBenfiquista.com Case Study hernanibf Presentation done for Drupal Meetup Porto 27th November 2010. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/drupalsb-101127183854-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> Presentation done for Drupal Meetup Porto 27th November 2010.

Drupal Performance - SerBenfiquista.com Case Study from hernanibf

]]> 2986 2 https://cdn.slidesharecdn.com/ss_thumbnails/drupalsb-101127183854-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Drupal + selenium /slideshow/drupal-selenium/5467832 d6-selenium-101017164921-phpapp01
]]>
]]> Sun, 17 Oct 2010 16:49:10 GMT /slideshow/drupal-selenium/5467832 hernanibf@slideshare.net(hernanibf) Drupal + selenium hernanibf <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/d6-selenium-101017164921-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" />

Drupal + selenium from hernanibf

]]> 1948 1 https://cdn.slidesharecdn.com/ss_thumbnails/d6-selenium-101017164921-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Drupal Recipe /slideshow/d6-final/4334885 d6-final-100527173444-phpapp02
Featuring its hightlights, main uses and basic components]]>
Featuring its hightlights, main uses and basic components]]> Thu, 27 May 2010 17:34:22 GMT /slideshow/d6-final/4334885 hernanibf@slideshare.net(hernanibf) Drupal Recipe hernanibf Featuring its hightlights, main uses and basic components <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/d6-final-100527173444-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> Featuring its hightlights, main uses and basic components

Drupal Recipe from hernanibf

]]> 763 2 https://cdn.slidesharecdn.com/ss_thumbnails/d6-final-100527173444-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://public.slidesharecdn.com/v2/images/profile-picture.png https://cdn.slidesharecdn.com/ss_thumbnails/presentationtalk-hackersautomatebutthedrupalcommunity-180913062607-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/drupal-europe-2018-hackers-automate-but-the-drupal-community-still-downloads-modules-from-drupalorg/114208018 Drupal Europe 2018: Ha... https://cdn.slidesharecdn.com/ss_thumbnails/aimingddd-180705173810-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/aiming-for-automatic-updates-drupal-dev-days-lisbon-2018/104399306 Aiming for automatic u... https://cdn.slidesharecdn.com/ss_thumbnails/deployer-171115144608-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/deployer-deployment-tool-for-php-82108557/82108557 Deployer - Deployment ...