References

References from some of our projects (excluding NDA projects) which we are especially proud of. In every project we have created something more than in a regular or common project. You can read more details below.

Project description

Habinator mobile App was published in both Apple Store and Google Play. The App "Digital Health Advisor and Life-Coach" allows user to reach personal goals and make lifestyle changes - which is the only real way to get healthy. The mobile App was implemented in React Native. The backend is Drupal 8 including Google Firebase, API's from social media sites to allow easy account creation and login, and external email service for efficient marketing purposes.

The project was made using known best practices and helper tools like Fastlane which allows us to make a release and upload it to both stores in minutes with one command. We also configured an optimized TIP Solutions hosting stack including AWS CloudFront for faster data delivery globally.

Benefits

Because Drupal 8.7 has JSON API and REST modules in core requesting and posting data between the App and backend is as easy as it gets. Additionally creating a new API Endpoint takes about two minutes.

Authentication and data encryption is done with an OAUTH module and it's dependencies which even anonymize the user (GDPR requirement).

Core's standard taxonomy, entity reference and node systems are known to give a powerful tool to create the data architecture as usual. Other benefits using Drupal are that the content can be generated using WYSIWYG editor and other common content creation tools - and then consumed by the App. Translations and multilingual properties are easy to build as always.

Challenges

Building the backend did require developing six custom modules which took about a month. These included implementing the social login options using Twitter or Facebook to create an account. Also, push notifications contrib modules we're not suitable for our purposes but we found official Firebase PHP bundles which we could use to build a perfect notification system. Additionally, security measures required a little work because we don't allow the App users to log in to the backend.

Conclusion

People has been asking if Drupal 8 is suitable for a mobile App backend?

We we're also very skeptic and we never would have recommented Drupal 7 but version 8 is a totally different system. Community's documentation about mobile App's gives a starting point.

The answer really seems to be "yes, it's very suitable" - even in the area of performance. The common conception is that "Drupal is slow" but the people doesn't understand that Drupal is only PHP code using a database and there are tools like Redis to make it very fast if the site is build correctly.

Project description

After completing the Kunnopaikka spa hotel website project we built a web store using Drupal Commerce which is an optimal solution for complex online stores. The hotel uses the Hotellinx ERP system to manage all room reservations, bookings, crafted offer packages, etc. in the system. The desirable state for the staff would be that they could create vendible rooms and offers only in Hotellinx and these "packages" would appear in the store automatically for sale. We released a series of articles about the technical implementation for other Drupal professionals.

The sellable "packages" or promotions might be available only with a campaign code or they could be restricted to be available with a certain criterion (e.g. date range or night count). Packages also should support multilingual capabilities for international sales.

The advantages would be to manage all sales themselves like updating room descriptions and promotions for sale without contacting a third party service. Additionally, these sellers (like booking.com) take a 10%-25% fee from all sales! Yet another advantage is that you can create promotions to be paid immediately online or when checking in which makes receiving the money faster (even if the customer decides not to come).

 

Hotellinx ERP and Drupal Commerce as webstore

 

 

The next release will include an additional step to the customer booking process where the customer can include additional services like champagne or a massage to their order. The goal is not only to increase the overall sales but to make the management of the purchased services easier for the staff and more convenient for the customer.

Conclusion

The shop is fully functional and without any additional marketing efforts there has been bookings from the first day on. The hotel is currently fully booked but of course there is a buffer build to restrict (or spare some rooms for unexpected customers) overbooking.

As a bonus for the sales staff we optimized the email flow and order management to be more efficient.

Project description

Kunnonpaikka is a well-being center in Kuopio, Finland with more than one hundred employees, offering a wide range of services such as rehabilitation, meeting rooms for businesses, restaurants and many sports facilities. The need for a new website had been there for some time, as the former publishing system did not fulfill today's needs, and many of the editing needs required the service provider's support. In other words, the former content management system (CMS) was not flexible enough to be configurable from the customer's side. Following the comparison of CMS, Kunnonpaikka chose the Drupal platform because of its flexibility, roles and permission system, multilingual properties which excel e.g over Wordress.

Kunnonpaikka has its own graphical guide (styleguide) for branding, and using the old site as a starting point, a slightly modernized layout was created for the target audience. Since the system has to serve all the departments that provide a large number of different parts of the site (such as a rehabilitation section implemented in a different color scheme), we used Panelizer to implement the flexibility. In this case, users in the admin role can click together pages that are different from each other and can lift for a visitor, for example, different promotions depending on the context.

The site utilizes scheduling functions e.g. for the weekly publication of lunch menus. In this case, the menus can be created already on previous week, by the chef himself (who alone has the right to edit the lists) and without the previous experience of managing any CMS said the process has been "surprisingly easy".

Most work on the project required two different calendars for front page monthly calendar and sport calendar which both also are site's most visited pages. The Drupal community did not provide a module for any desired functionality at the time of construction. But as always, the solution was found using Views + Exposed filter + Calendar + Quicktabs modules, and a little Javascript.

Conclusion

The biggest challenge in the project was to provide services to all Kunnonpaikka's parties who use the site and offer their services. This means that the site will be edited by many different people working in different positions. Sometimes this issue is solved by using multisites, where different departments in the company have completely different websites. Or there are 1-2 people in the company who update the site for others, which leads to e-mail conversations and waste of time. Although the Drupal platform has been criticized for poor editing experience, Drupal 8 seems to have solved most of the problem.

Project description

XRG Simulation is a company in Hamburg providing in modelling and simulation software. Their multiple products cover areas at industries like aerospace, power plants and automobile. The main purpose for the new CMS is to function as a marketing channel and provide information for the clients.

Branding material and design was already created by agency communication company E D W A R D T O N Y.  Our job was to build the new website and migrate the old one to it.

The new site was a pretty basic CMS project including multilingual support, responsive design, basic SEO and migration. We decided to build the site with Paragraphs module to solve the old problem that the end user (content manager) can break the design (for multiple devices) by embedding non optimized content to WYSIWYG editor. Using Paragraphs and responsive image styles there is always a right place for images and text.

Conclusion

Maybe the biggest separate job was to implement the product carousel on the front page and get it to work properly on all devices - from which we wrote a blog post because we also though it would be an easy job.

We are now using Paragraphs in every project and we have had only positive feedback from the content managers. The module seem to be a real game changer to the "challenge" that all content is included to a one text field through WYSIWYG editor. The investment to write a little bit more CSS (or LESS/SASS) before launch is definitely better than the end user fighting every time when creating new content or fixing design bugs to the live site. 

The project was also developed using Drupal composer template and Config split module together so the further development is fast and reliable.

Project description

Finn-US and Halmari are companies which core business is to ship cargo (like cars, motorcycles and containers) from USA to Finland and all over the world. 

Because the business is separated to two different companies there was a need to two similar websites. First finn-us.com was build from which we cloned the hal-mari.com site and applied the same concepts to design which can also be branded fast again when needed in the future. 

In the project the old Wordpress CMS website was migrated to Drupal CMS. The design was updated and the custom plugins / modules were ported. The most time challenging part was the cargo calculator which is used to calculate the order- and shipping costs and then directly order the shipment. On the way the module was enhanced to be E.g. multilingual and more usable to the user.

Other more time consuming part was implementing the warehouse address creation to Magaya-software where the user can follow her shipments. Here the Webform module was used and expanded with a custom module.

In design the main priorities were a) Simple b) Responsive. The point was the site is easy to use for every single visitor and works with every device.

TIP Solutions made all areas of the project.

Conclusion

In development the most hours were used to port the old modules. Other bigger part was to make the site usable as possible for the visitors.

Right after the website was published very positive feedback came from the old and new Finn-US customers how the new order process works.

The site is fully multilingual where other languages can be added easily when the new company expanses to other areas in the world.

As a hosting solution we used a standard TIP Solutions stack for Drupal 8 projects.