Blog /Company

DrupalEurope is this year’s largest European conference devoted to Drupal. In previous years, each edition of the conference (formerly known as DrupalCon) was attended by about 2000 participants. We already know the programme of the conference with 162 hours of lectures over the course of three days! Because I run a Drupal agency myself, the conference is super exciting for me. I decided to go through the programme and make a list of 13 lectures that I think are worth seeing. 1.

Since July 2018, our branch in Rzeszow is located in the new office. We've been looking for a comfortable and modern place for a long time. After a few weeks of research, we've found an ideal place - the SKYRES office building. Access and parking lot We wanted to choose an office with easy access to each point of the city and to the highway.  A space in the parking lot was also important to us.

At Droptica, remote work is something ordinary. From the very first day, we had two offices in Wrocław and Gdańsk. Recently, we also opened our third office in Rzeszów. Every day, developers, testers, graphic designers and other specialists work together in each of these locations. In addition, 90% of our clients come from abroad, like in the case of most software houses. Throughout several years, we have developed methods of effective and efficient cooperation in a dispersed team.

We recently wrote about  why SCRUM improves software development quality and why remote scrum teams are often a good choice.  Today we will discuss a very important part of scrum which is often neglected, what leads to reduced preformance, delays and mistakes - Sprint Retrospective.  What is Sprint Retrospective? This is one of the meetings in the SCRUM methodology. The meeting takes place on a regular basis, at the end of each sprint.

At Droptica, we have been regularly recruiting PHP developers for quite some time now. We often get asked what exactly does one have to know in order to join our team, mostly by people who are starting their careers as developers or who want to switch jobs or even industries.  The extent of “PHP development” knowledge is vast and our expectations regarding our candidates may not be obvious for some.

This year, Droptica turns 5! Many things in the company have changed during this time. We want to reflect these changes in the form of a new logo and describe our rebranding process. Our new logo represents who we are and who we want to be more accurate. Image change is part of our continuous development. The New Droptica The new visual identification system of Droptica is a revolutionary change. New logo. New colours.

Another year is over, and we are glad to acknowledge that we are very proud of what happened during this period! In short, 2017 was the best year in the company’s five-year history. That is why we decided to share a brief summary of the year with you. See what we achieved over the last 12 months and what we have in store for 2018.  Reasons to be proud At the beginning of the year, Clutch recognised us as a worldwide leader among Drupal development companies.

It is obviously necessary to look for and take advantage of tools which can be used when delivering Drupal development services. It's time for another dose of information about our work at the Droptica company. Today we'll cover file versioning and application testing. Subversion Initial projects implemented with Drupal (still as OPENBIT) used the Subversion system (also known as SVN, project website) for file versioning.

Clutch (a portal ranking development companies) named us as the global leader among companies working with Drupal. This is a great success. We are among the best companies working with Drupal worldwide. The results of our work are becoming increasingly more visible. Since the beginning, Droptica aimed providing the best drupal services.

For the last couple of months, we worked on our new website in Drupal 8. It took time because client work always takes precedence. But we finally did it! Here is the story. Design stage As with any new marketing website, we split the project into stages. First, we developed a content strategy - what do we really want to say and why? We wanted to avoid ad-hoc decisions done during development or design stages.