SymfonyCon Madrid 2014

Cómo resolver los problemas más difíciles del comercio electrónico

Bojan Zivanovic  · 


HTML (pincha para descargar)



Extracto de la transcripción automática del vídeo realizada por YouTube.

my name is bland jovanovich and I am primarily a drupal developer I am a commerce development lead for commerce guys and my job is to deliver the next version of our big ecommerce platform called drupal commerce specifically my role is to determine architecture

leave the community leave the community contributors and then do all of the work that remains with a special focus on the libraries that solve the problem that we are going to see today here hands up who here has ever played with Drupal commerce or seen it

ok a few hands maybe five or six not too bad so our vision is very simple and very modest we want to roll the world so far we are still not there yet but I think we are getting closer and closer all of us put together have about seven years of experience doing

e-commerce from our co-founder has written ubercart on Drupal five and six and then we all got together and started fresh for Drupal 7 so Drupal commerce was a complete rewrite built from for Drupal 7 which the idea of being immediately familiar to anyone

who already knows triple seven so if you know Drupal 7 immediately know drupal commerce and you're probably asking why was Drupal 7 so important well we realized even back then in 2009 when we were starting development that no one builds sites like they

used to that the way people build sites has changed previously you had this big site provided by CMS and then you had your ecommerce store on a sub domain and those were two completely separate halves but no one builds ecommerce sites like that anymore unless

they're Apple so nowadays people really expect a strong blend of content and e-commerce your clients expect really strong content tools to be able to promote their products in the best way and to just tell their story and then be able to get money from

their customers along the way and Trubel is a good CMS and it proved to be a winning combination because many people recognize the need for a strong CMS behind a strong ecommerce solution and it's also changed the way we approach architecture we knew that

we needed to build an e-commerce framework not a complete ecommerce solution because most people won't take a complete ecommerce solution with a grid and then just slap a custom team and be done with it it's great for those who can but most of the

clients we work with have really custom requirements so you need a toolbox you need a set of tools that will allow you to make the flow that you needs to make the design that you need and to finish your project without fighting the underlying system and if

you've done ecommerce you know that that's not very easy especially in other projects so we knew we needed to make a framework that was completely decoupled if you only need product listings that's fine if you don't need a cart because you're

creating orders from the admin that's great maybe you don't have a front-end at all you're just serving stuff to a REST API no problem maybe you're remaking the admin panel completely and doing your own completely custom workflows that also

works but the important thing was to be able to enable all of these hard requirements and in the past three years so we released triple commerce in 2011 we've managed to reach more than 50,000 live sites live installations so we're obviously doing

something right and obviously we are getting our points across to our audience so I'm really happy to see that and we've managed to reach some really big sites a royal mail is powered by drupal commerce and it is commerce provides a REST API that then

communicates with various sub sites we use it on Cartier where they have their own completely custom administration screen and completely custom back off is that which then feeds per country sites and point-of-sale apps we use it for lush our newest and biggest

website we use it for other sites such as Willian Westwood and kenzo and Givenchy and many many others so we've had great success with stabilizing the plate platform and covering a wide range of use cases shipping websites digital downloads recurring subscriptions

multi-store whatever and wherever we were able to cover it and at least provide the developers the tools they need us to develop on top of us and provide the feature that they were missing as I said they work for commerce guys and we are the primary company

behind Drupal Commerce we have about 60 people in Paris London and an arbor michigan about twenty-five percent of our workforces remote including me i work from serbia and go to Paris every month for the wine and cheese apart from doing drupal commerce we

also have a cloud platform that's called platform that Sh which addresses the frustrations we've had with developing e-commerce sites from our local machines up to production and aiming to make that workflow simpler so platform is a tool we're

on which you would develop your site and on which you would go live so it will it would host your application or website but instead of having development and staging and master you have unlimited branches you have the branches that you usually have in your

get flow and every branch gets a completely built environment with the publicly available URL so if I go to the staging branch and create a branch called add coupon support platform will immediately create a complete clone of the server architecture so in

a minute I will get the clone of the my sequel database I will get the clone of Redis I will get the clone of solar and I will be able to start my development and immediately share that with my colleagues when I'm done I can merge all of that back we have

a stand where the booths are near the second tracks if you want to see a demo or get promotion codes feel free to do so I really think it's something special so on july first we created this organized this really big commerce to the text print and the

idea was to figure out what to do form for the immediate future the truth is in the past few years in the PHP world everything changed we built triple commerce one in 2009 but since then composer happened and Symphony happened and drupal 8 is happening and

our whole world changed around us so what we did was gather all of our partners who have been building sites using drupal commerce for years we gathered our friends from senseo labs from Aquino from smile and we gathered all of the feedback they've had

over the years we asked what it was that we could do to make building ecommerce sites simpler and just create an architecture that can drive us for the next five or six or many more years and what what came out of that sprint was of course the conclusion that

we needed to start from scratch to implement the ideas that we had which is not a bad thing and it allows us once again to be successful and what we realized then and even before then was that there is no such thing as the e-commerce use case just like there

is no such thing as the web application use case or a CMS use case ecommerce is a selection of problems a group of problems many different ones the some that are different from use case to use case but you always have this core set of problems that are always

the same so how do you handle taxes or pricing discounts addressing how do you accept payments how do you model your products all of these are completely separate problems and it's time for us to stop treating them as one hope because we constantly ask

how does silly as compared to Magento and how does Magento compared to Drupal commerce but we never really asked which of these has the best tax implant which of these has the best internationalisation which of these has the most powerful product modeling

tools if we start looking at these problems separately we will be able to create a better set of solutions because now we can say okay commerce has better taxes than Silius what do we need to do to make Silius better and then we go and do that and we have

[ ... ]

Nota: se han omitido las otras 3.894 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.