Development

When implementing classic website projects, we rely on open source-based content management systems (CMS) such as Wordpress and Drupal.

In addition, we have our own developments for smaller, agile projects, but also headless solutions. Webflow is also becoming increasingly popular with us.

If a backend system is not only to play out content via a classic website frontend, but also publish data via different multichannels (such as apps, social media platforms or online shops), we use headless systems. We organise a central publication and licence management of media files through media asset management systems such as SixOMC.

Since open source systems can have many disadvantages, we also work with the Swiss enterprise CMS provider Magnolia. The system is characterised by a high degree of flexibility and user-friendliness and is suitable for both small and large projects thanks to various price models. As a licensed development partner, we cover all areas of the development process from consulting and planning to implementation.

The programming of websites, prototypes or individual applications relies on a base of HTML, VUE.JS, STORYBOOK, ESLint, SCSS and Atomic Design.

Our workflow in a typical project can be divided into four essential areas:

Control and documentation

Every project is individual, but that doesn't mean we don't use standards. For project and task management, we rely on the industry standards Jira and Confluence from Atlassian. Depending on the size of the project and the requirements, these tools are already used during the creation phase or only during programming.

Our creation process

In the design and conception phase of a project, individual production and development steps are usually structured with the help of a ticket system and Kanban boards (→ Jira) and tendered within the development team.

Staging & Deployment

All development steps of a project are usually first executed and tested in a development environment (stage). Only after the successful completion of a project goal are these results transferred to the live side (deployment).

Code repository

The data material produced for both the implementation and maintenance of a project then ends up in project-specific code repositories (→ Bitbucket).

Development results are tested as follows:

• Browser check
• Hardware/Device Check
• Platform/Operating System Check (Mac OS, Windows)

A website should offer maximum accessibility for all target groups. Therefore, every website developed by Henkelhiedl is fundamentally barrier-free. The following points are taken into account during implementation:

• Implementation of the frontend with standard-compliant and semantic markup according to W3C guidelines
• The CMS used is prepared in such a way that meta data on images can be filled in. This applies especially to the alt and title attributes, which can be read by screen readers. Set a jump mark »to content« for screen readers so that the navigation is not read out each time.
• In addition, accessibility can also be achieved if desired. In this case, it must be clarified in advance what level of accessibility the party placing the order wants or needs to achieve (BITV 2.0 priority list 1 and 2, WACG).

In short: We also take care of the hosting of a site, of course. Including support and maintenance. Because: A digital product is a process and not a project aka never really finished.

Of course, we take search engine optimisation into account as a matter of principle, also provide advice on this and constantly keep up to date on new developments and tools.

Whether newsletters or marketing campaigns via social media, the basis is the for many of our projects we programme and/or configure an interface/API to existing data sets. This may not necessarily be the issue for measures in the pure presence area, but besides business cards on the net, we also have experience with large website projects.