 Tako, če vidimo, dva dobro, a dobro da se pravimo, kako je drupal. Mne je Tammer Zoubi, jaz je nekaj z Zagreb Kroesha. Mamo v sveti, srednjih vkrošenih wettos, HR, je drupal vsega, da je kroesha. Tvoja je drupal vsega, vsega nasličenja, v lokalnih metupov, in imam da je drupalist kotibutiv na drupal.org v moj frejtime. Imam zelo način nekaj loudspeaker, tako, da ne pačeš, poživajte. Zelo tudi igrali te 5 seksu. Zelo se prej drupal. Zelo se, kako drupal Zelo najbačno vseči izmeni in stvorili, da je to nači vseči, da počušim pomega dvoj ruple 1-8, da se očuči na zelo kajom ruple in zelo vseči in zelo da se očuči na vseči. Veskaj, pri zelo pri ruple recimo, da je to način v 90-jih, ispočili smo najbolj na zelo, da je vseh hradične, vzelo v hradične, in v zelo vzelo. V zelo v midnjiče, smo zelo css, vzelo vzelo v zelo, in vzelo v zelo, vzelo vzelo vzelo. Vzelo v zelo v zelo, vzelo vzelo vzelo. Vzelo vzelo vzelo, kontenem, skupem, vinjetem in phpnjukem. Vsi vse je vse popljavati na vse počke, ali tudi vsi je vse vse vse in Drupal je vse vse vse vse vse. Zato, če je Drupal vse vse in tudi nekaj? Kaj, kaj sem izgleda v 15 rojnih, history of Drupals. I think it got four main points. And those are the open source. From its first version, Drupal is a GPL license. And this set corner store for the community we have today. Then it's the modularity. It introduced modules and hooks also from its very first release. Those are commonplace in today platforms. It took concepts of nodes rather than pages, where we are starting to see recently that web start to evolve less and less around pages, where we can have the node approach, which give us opportunity to display different content on different devices. And then we have constant evolution and reinvention over the backward compatibility, meaning that Drupal, also from the very early beginning, chose not to preserve the backward compatibility, because that would require you to direct some historical baggage. And this would come at a significant cost. So it was chosen that we can break people code, but we cannot break the people's data. And basically now you know why it's so hard to migrate from one major version to another in Drupal. And to see why and how Drupal was created, I would quote Dries, the founder, who said that for me the history of Drupal is a chain of interesting surprises. And the first surprise begin in 1998, when this guy, at the time a Belgian student, he began constructing the local internet message boarding site where he could discuss some technology news with his university friends. And after he left the university, he kept the discussions going by moving the internet site to the internet, and he called it drop.org. And actually the story behind that was a typo, because he meant to register a domain named Dorpje, which means village in Dutch, but he mistited and he got drop and actually it sounded fine, so he went with it. And later when he was naming his software, he back-translated drop into Dutch. So he got Drupal, which sounded as Drupal in English. So like two days before the new year of 2000, in this legendary commit, he baptized his software Drupal and he also added the GPL license to it. So then only after two release candidates on the 15th of January, 2001, we got Drupal 1.0. It was mainly used for a news drive or a portal sites. It was storing content in stories and books. And mainly it was written after some other popular message boarding systems like Slash and Scoop at the time. It also didn't have any menu router, so you would access everything through a set of PHP files, like admin PHP or account PHP. It was having this funny naming for guest users. They were called anonymous chicken. So also one of the important features that it had was the database abstraction layer. At the moment it was just supporting my SQL table, but it should be straightforward reported to other databases. And from its first version it had functions like dbQuery, dbFetch object, which we all know they are still used in Drupal 7. At the moment it didn't have the install script. It was coming with SQL dump, so you had to manually import it. And it had 15 tables on. And when you would import that file, you would get this, your very own first Drupal site. As you can see it was very basic with just a few of the functionalities. And those functionalities where you could submit stories and diaries, you could have accounts. No, no, you were in here. Yeah, yeah, it's fine. So you could also have user logins, registrations, we had comments, search. There was a calendar. So you could reach in the archive content. This is the sample of how entering the content looked in Drupal 1. There was no visi we get it, or it was very simple. A few allow the HTML tags. And also from the very first version, Drupal was modular because Dries wanted to have the modular system so that other people could adjust it to its own needs. And in the beginning the modules looked very primitive compared to today. There were just a single PHP file called .module and it was located in the modules directory. And basically, if you would log in as an administrator, you would be able to see all modules from here. But as you can see, there was no option to enable or disable the modules. It was actually manual process you had to copy or delete them from the modules directory, actually. And in the first version, there was 18 core modules. And as you can see, in the administration interface looked different than the client-side interface because in the first few versions Drupal had this separated. So the administrator didn't really have any team. It was just like a bunch of configuration links in the header. And how modules worked, well, the idea was to be able to run the random code at the given places in the engine and those places where you could run the code were called hooks. And at the beginning, this is the list of all Drupal 1 hooks. There were just like seven of them. And impressively, three of those hook are still used in Drupal 7. They are like hook hell, hook crone, and hook block. So also, from the very first version, Drupal had a teaming system, so he tried to separate it in the backend from front-end. So inside the team, you could control the colors, the markup, the layout, and even the position of the boxes or the blocks, as we call them today. And as the modules, the teams were also very simple. That was just a single team file, which you could place in a teams directory. And this team file was just PHP, implementing a team class, which had like five functions, like header and footer. And then you would override those functions and output your own HTML in there. So, yeah, each user could change his own team in the site preferences. There was no option to set it globally for all the users. And also, as we said, from the very first version, it was open-sourced, GPL-licensed, so it, Dries had the vision that every user should be and could be the contributor to the Drupal. And from the beginning, he made the instructions that people should use diff and patch over directly committing to the repository, because that makes better content control. And in the first version, the patches would be submitted to the email and in plain text to the Dries himself. So, soon the community would grow. This is the, at the moment, the only Drupal one site that I know was running was drop.org. And soon the discussion about Drupal will start to take place in here. So, then only after two months we got Drupal 2. That was, like, on 15 of March, 2001. It added an important feature that was translation. So, it introduced the t function, which is still in use today. But, however, adding the new language required you to manually edit the configuration file and to manually edit the tables inside the SQL. And you couldn't have the language switcher, so it was only, like, one language at the time. And so, from other features that were added in Drupal 2, we got user access. It's still used, I think, until Drupal 8. That is the permissions system. It added something that didn't live long. That was the user ratings. They were quite popular in the early 2000s. It added the sections for stories. Later this will evolve in a taxonomy module. There were some rewrote of the existing modules, like comments and discussions. And this is Drupal 2. And as we see, except for logo and maybe few links, nothing much changed on the client side. And this is a sample how editing the user account from the admin side looked like. As you can see, there are many fields that have the same name even in Drupal 8 today. And this is a screenshot of one of the Drupal sites. Now we start to see more and more. Drupal sites start to appear online. This was globalgreens.org and as you can see at the beginning they all looked very similar to drop.org. There was no customized front page. It was just a list of node teasers and even they all had the same menu links. It wasn't even possible to change them in the first versions of Drupal. It had this configurable boxes like calendar or sections. And this is the drop.org. Soon, like after the release Drupal, the discussion started to be more toward the Drupal about the news as he imagined this site would be. Soon he opened Drupal engine section of the site where you could find all the Drupal relevant information. This is just some statistics. There are 22 core modules 2 months in development. And then on 15 of September that was about 6 months in development in Drupal 3. And in here Drupal introduced nodes. So now everything is based on nodes. Basically, in the first two versions of Drupal it was using stories and books to store the content. But soon as Drupal started to evolve and it wasn't used anymore for just like a message boarding sites like drop.org. We started to see more and more content like blogs and forums and diaries. And all of them had the same fields like title, author, date, published or other properties. And at the moment like lots of code was duplicated to make that happen. So since Drupal was already being modular it makes sense to make framework for the content. And then the nodes were born around which all the content types would be based. So this is the second key success point that we talked about because it won't be until 10 years later that we see the rise of mobile phones that the web started to evolve less and less on out pages and it's more now about nodes where you can use the content in a different way on different devices. And when you would install Drupal 3 it's like a new logo. We got a new team and we have some more links than in previous versions. And the admin side remained pretty much the same. But we got now the administer permissions page. Basically you could add new roles and you could manage the permission for each role. Basically this is the very same interface that we use even in today's Drupal to manage the permissions. And still we see some Drupal 3 sites at the time. This is like Void Style, somebody's blog. They look very similar in content. And then shortly after Drupal 3 got released Dries opened Drupal.org that was in April of sorry, it was in December of 2001. Basically the discussion on Drup.org became overwhelming because everybody started to talk about Drupal. So he decided to open a separate site where the discussion will start to take place. Some statistics some increase in number of core modules. And then Drupal was basically evolving quietly until 2002. That's when Dries initiated a relationship with Jeremy Andrews. Jeremy was the author of kerneltrav.org. It was a very popular Linux news site at the time and it periodically go down because it had lots of traffic coming in. So Dries suggested him to switch from PHP Nuke to Drupal and he did that and on the February of that year he launched his site on Drupal 3 and it was this relationship proved to be a success not only Jeremy became one of the top Drupal contributors but he also reported about his conversion to Drupal on his site and as Dries said this report opened eyes of many technical people about Drupal. So now Drupal is starting to gain more and more popularity with Dries. So in the June of the same year it's about nine months of development we got Drupal 4. Now we started to see more and more major sites running on Drupal. We also get more contributors from Europe from the US so it start to become more of an international open source project. And then Drupal 4 when you would install it it's still a similar team we got new logo, it's now 3D logo type and some more links there was also footer added but it's not visible here. And then the big change in Drupal 4 was the meta taxonomy that was a hierarchical tagging system so basically after now Drupal was using the meta module and it had meta tags and attributes and it was like classifying the content like in child parent relationship but those relationship wouldn't be used in a proper way. So there was actually a huge discussion in Drupal.org and then the community actually built the taxonomy model and basically it was working with the concept of having a global vocabulary that you could create new vocabularies for storing the tags and then you could be able to bookmark on each node to which tag this node built along and it was all hierarchical and it was I think at this point that Drupal started to look more like an enterprise content management system. This is a sample how basically creating a new vocabulary looked like basically you would have to choose on which types of node you can apply this vocabulary. It was used I think on Drupal 6 then in Drupal 7 it was replaced with the term reference module. This is the adding the new content in Drupal 4 now we are starting to get more and more options as we see down there we got the revisions that was also an important features of Drupal 4 we also have the teaser we can put the navigation link which is something like a main menu and we also have the properties like published or promoted to front page and basically the similar properties we are still seeing them today even in Drupal 8 and also big change in Drupal 4 is that now you are able to enable or disable the modules directly from the user interface so no more manually copy or deleting them from the directory and also in Drupal 4 we introduced some concepts that didn't live long there was like this authentication system based on Drupal 4 or Yahoo logins it never really lived up as it was hoped to also had the blogger API support that was silently removed as of Drupal 7 it had the notification to web blogs it never lived that long and then with Drupal 4 it was decided to have like a minor version Drupal 4.1, 4.2 each one had new features so it was actually like a major release so on the February in 2013 we got the Drupal 4.1 it introduced the profile module so now you could extend the registration page you could add like address field or phone numbers to the registration form however it was kind of hardcoded so you couldn't add the new fields from the interface through the module we are also seeing like first teaming functions they were called like team invoke later they will evolve and become the team function which is still in use today and we got some other improvements to the forums and comments and etc also Drupal 4.1 it had some concepts that didn't live it removed the rating module which was added in Drupal 2 it added the throttle module that was the module that Jeremy wrote for the kernel trap.org it was actually an auto throttle congestion control so basically you could set your site disable images or blocks or modules inside in the case that it gets too busy in terms of traffic or users so as of Drupal 7 it was actually removed from the core because I think to there there are far better solutions like caching or even the servers are much more powerful than there were 10 years ago so in this feature I don't think somebody would disable images today on his site so then after another 6 months we got new Drupal it now had clean URLs as we know them today and we are getting to see the first idea toward some sort of menu router in Drupal basically now we don't have individual PHP files like admin PHP or account PHP now everything goes through index PHP and it introduced a queue parameter and then this parameter would call hook page so basically each model was implementing his own routing inside that hook so for example now you could access nodes through node slash view slash node ID and that would call node page function with two parameters one would be view and another one would be node ID you know what to do and what kind of output to retool and for example before this it had this kind of URL it was like node PHP and then bunch of ugly parameters and from other features we are starting to see support for the visivig editors we also got support for Microsoft SQL server so basically at the moment Drupal here was supporting like three databases layers that was like MySQL EGSQL and now Microsoft so it was actually still coming with three database dumps and it was at this time that people started to discuss about automating this process and to start making an installation script so eventually in later versions of Drupal will have the install script as we know it today we also got node API so we can better integrate the nodes I think if anybody worked with Drupal 6 this was like highly used later it was replaced with hook entity operation hooks we are starting to see EGS template this was like a teaming template which start to replace the custom made team class that was used for the Drupal teams later this EGS template it will be replaced by PHP template and then during the same year in the summer of 2003 the interest in Drupal got like a really significant boost when it helped build a dean space that was a promotional website for Howard Dean it was one of the 2004 presidential candidates basically dean space was something like a Drupal distribution it was like preinstalled set of models and content which then supporters could download and install to have their own version of the dean site for promoting his campaign and basically as this campaign started to growing up we saw like huge increase of people and activity on Drupal.org documentation and modules this was the dean space website from 2004 as you see it remained in the footer like a build on Drupal so basically this was the first time when many of people heard about the Drupal so eventually in the summer of 2004 the Howard Dean didn't get elected and it was pronounced that this project was dead however there was now at the time many Drupal developers that were working on this so they started to turn Drupal into like some other applications like for NGO or similar and then one of them was a civic space so eventually the same developers that work on civic space will work with Drupal developers to promote the idea of having Drupal distributions officially and they wouldn't need to fork Drupal and modules and maintain it in a separate bridge and this will eventually happen in Drupal 5 in the meantime the Drupal was struggling between 4.0 something versions so we got only after 3 months of development we got another version which now had like path module for URL aliases it's still used in Drupal 8 in database prefixing so you could basically install multiple Drupal sites on one database which is important for the share costing where you cannot have more than one database and it will do some minor things like breadcrums and mass node operations and then Drupal 4.4 it added the file API so now it could finally start uploading the documents attachments added the field set as we know them today and now we are starting to see the better team functions in Drupal so now everything that's teamable is being outputted through team underscore functions and this greatly improved teamability where other modules could extend output of other modules it's still the same very same functions are used even today and also as number of contributors started to grow we are starting to see more and more advanced modules so one of them was e-commerce module this was actually a whole set of sub modules which should turn your Drupal 4 site into a full e-commerce application then after another 7 months in Drupal 4.5 now we have like configurable menus also very important the hook menu is born so now every model is actually defining his own paths this is something like basically a menu router in Drupal it was used until Drupal 8 now it's being replaced by a symphony router it also introduced the tape based user interface which are showing shortly which is basically the look and feel of Drupal that we all know today and it made possible to add multiple user roles and some other minor things and also one big improvement was that's finally since Drupal 2 we are seeing major improvements on the translation so basically now you could manage the translations through the user interface so you could like start to add languages you could have multiple languages there was the language switcher so now you could really have a multi-lingual site, started to support the get ex files so you can import and export strings for the translation and as we see up there we are starting to getting this tapped interface and this is now the admin user interface is looking like it's basically now the admin and the client side of the application is is looking the same they are not using the separate team anymore so then we got first Drupal conference in the February of 2005 this happened in Antwerp in Belgium it's now known as the first Drupal basically there were like only 15 attendees and usually because the internet connection would be bad it would load the whole Drupal contributant repository with them and then come on the conference and work offline this is like today maybe impossible with 30,000 models and more and now we are seeing that the community is growing and there are more Drupal cons and sprints organized and then Drupal 4.6 it started to support PHP5 now you could have like multiple sites installed on a single code based you are getting also the image API for managing resizing and cropping of the images and now some more famous projects are starting to use Drupal this is the NASA for one of their project and then Drupal 4.7 actually took quite bit to develop I think around bit more than a year and at the time there was already more than 55,000 Drupal sites online there are more than 300 contributed modules in the repository and we get more and more contributors and patches working on this Drupal and also in 2006 the views contributed module was born basically it will become one of the most popular Drupal modules now in Drupal 8 it is included in core in Drupal 4.7 it got lots of javascript and Ajax which was still relatively new technology at the time it also reworked the forums API so basically now you could like alter and extend any form in Drupal this is very similar to what we have today but however it disfrustrated many users on Drupal.org because this new API broke like hundreds of contributed modules and it ended up that it was a real pain to update them and people were late with their work eventually they see that the payoff was huge because this new form API was much better and flexible and this is the fourth key success point that I mentioned this is the constant evolution and reinvention over the backward compatibility and also there were some module improvements you could install each module could now install its own database table the install file as we know it today and there were some big team improvements there was the Adrian Rousseau who specifically for Drupal he wrote PHP template system so basically the x template engine was removed and all the core teams are ported to the PHP template and it was using like individual tpl PHP files to team the Drupal team underscore functions it was great if you know a little bit of PHP you could make a really advanced layouts and eventually the PHP template will now be replaced in Drupal 8 with better one which is a tweak and now we are starting to see more and more popular sites using Drupal now we have MTV, CoUK Playstation Asia Hillary Clinton they are all now on Drupal 4 in numbers we got more contributed modules sorry core modules and in total it took over 50 months for all Drupal 4 releases and then on 15 of January 2007 this was actually Drupal 6 birthday we are getting Drupal 5 0 released Drupal 4 was released back in 2002 and then the community felt ready to move to a next major version so they decided to have 5 0 release and it had like record number of contributors and patches and over 2000 contributed modules so it introduced the web based installer so no more manually importing the SQL files it reorganized the modules so now each module is not anymore a single PHP file it has its own directory it has its own install files info files css and javascript and other includes and now we separated the contributed modules they go now to sites old directory and in the modules the core modules remain also in the introduction of info files we are getting the module dependencies and this was very important because now each module could build a small part of functionality and then together they would build a feature which is better than having a module building the whole feature which is something like I don't know plugins in WordPress have which can bring incompatibility between different modules also it has more cache backends so you don't need to use the database caching now there is like other like memcache or file caching we are getting the jacquery in core the Drupal was a very early adapter of jacquery today it's basically used on over 60% of top million sites we also got custom content types and you could create your own additional content types and we added the support for Drupal distributions as we mentioned earlier now basically they are like ready made loadable packages of preset modules and content and then from team improvements we got garland, it's a new default team still my favorite even Drupal 7 there was this color module but I don't think it was ever used that much we also got css caching which greatly increased the speed of your site this is now how Drupal 5 start to look like basically it's more like a modern day Drupal as we know it today and now with this release we are getting more and more Fortune 500 companies on Drupal we have like Warner Bros, Fox Yahoo, OpenOffice et cetera we are seeing some increasing number of core modules in here and then Drupal 6 it took 13 months to develop it was released in February of 2008 and actually it was end of life recently that was on 24 February this year so that means if you still run on Drupal 6 there won't be any more security updates so it's time to start migrating to a new version of Drupal still there are like estimated of 120,000 Drupal sites online today and in total there were like 7,000 contributed modules over 600 custom teams in the repository it introduced lots of new features like better installer we got drag and drop administration so you could move the menus and taxonomies and blocks we got Drupal menu system was rewritten from scratch so it became much more faster and it got improved security, we got update module so you would be satisfied when there is a security release and there was a security announcement email list on drupal.org where all you can still subscribe today and get the latest information about new security releases so after October the white house goes to Drupal basically it was a huge milestone because in terms of security because now Drupal are starting to rely that people are starting to rely that Drupal is more secure because white house made strict security audit before choosing the CMS for their own website so basically some statistics for Drupal 6 we got over 30 core modules now and it took more than a year to develop and then almost 10 years after we got Drupal 1 Drupal 7 is released now it's used to build any kind of website like from blogs or macro sites to the full enterprise level CMS systems at the moment it has more than 11,000 modules and 600 teams and over 200 distributions in the repository and the big change in here is that it is an entity so not only the content types now we have taxonomy users and you can create additional custom entity types meaning you can add all of those fields and displays basically to anything in Drupal 7 it's now all about the web applications like for example I'll give the go send this is one of the largest projects that we are working on