Our company has experience with a wide variety of tools and systems, ensuring we always choose the approach best suited to the project. This can help keep development time down, and compatibility up. By choosing the newest technologies, we can offer a flexibility that simply wasn’t possible before now. This can mean an optimal experience for the majority of your users. Below you’ll find a list of technical aspects, for those clients who want to know.
We can supply our projects as docker images, docker-compose projects, or straight up source files. If you're looking to deploy a project in a particular way (such as via Heroku), let us know in advance, and we will give you the relevant information. By default, our projects are typically tested and developed in docker containers, as it offers us an easy way to shift current development snapshots to servers, or between workstations.
As websites become more complex, optimization is becoming more and more necessary. Access from mobile devices has increased in recent years, and as such, our patience for slow-loading sites has dwindled. In order to have the site load as quickly as possible, we use tools such as gulp or webpack, alongside approaches such as critical CSS, to reduce the size of the site as far as possible, and to load the more important aspects first.
CMS or not to CMS?
CMS (Content Management Systems) are ways for editors or copywriters to easily edit the content of a website - be it text, or images. Some examples are Wordpress, Drupal, Django CMS, and Bolt CMS. However, they're not the only way to create a website, and oftentimes they require a lot more processing power than necessary for small sites. In such cases, there are tools called static site generators (such as Jekyll, or Pelican), and also API-first CMS like CockpitCMS. While discussing any projects with us, we will aim to make suggestions for what approach may best suit the project.
All projects are created in git repositories, allowing for easy versioning of each file in the project. If you require a different version control system (such as svn), let us know, and we will adapt our approach for you. Depending on the client and the project, we can also upload the repository to a private gitlab repository, and give you access to it. This gives us a bug tracker, and a wiki, for close communication with clients during the development process (and beyond).
We are capable of using the newest technologies - be it React, AMP (Accelerated Mobile Pages), CSS Grid, or Flexbox. The old standards are also supported - floats, PHP, jQuery. We will tailor our approach depending on what your project and company would benefit from.
We generally supply basic documentation for using the CMS and any important information about the actual implementation of the website - this is because copywriters can change, and sometimes it's not possible to re-hire a developer to make changes. This way, there should be at least basic documentation for anyone new to the project. We typically create it using Sphinx, and can therefore supply the documentation as a PDF, an ePub, or HTML files.
We have experience with such approaches - using software like FOG we can set up an imaging server to store device images (and allow easy network cloning). Software such as Clonezilla can also be used to image and clone smaller numbers of machines (without requiring a dedicated server).
We have managed and handled macOS, Windows, and Linux/Unix systems. This includes such things as network boots, active directory systems, and virtualization (such as with UnRAID).
We can image, repair, clean, and otherwise repair macOS, Windows, and Linux/Unix devices. Even devices not capable of booting on their own can be at least diagnosed with our various bootable rescue discs.