I still do client work besides Kirby and one of my biggest client projects launched about a year ago. You can find it here: http://nimbus-lighting.com In fact it’s actually four connected sites:
- http://nimbus-lighting.com
- http://nimbus-group.com
- http://nimbus-mockup.com
- http://rosso-acoustic.com
The first specialty in this case is the multi-site setup which is run by a single Kirby installation linked to multiple content and site folders depending on the domain.
The installation is separated into two repositories. One for all the site stuff, assets, Kirby’s core and panel and one for the content. The content folders hold about 4 GB of data and all changes made via the Panel are automatically committed and pushed to a private Gitlab installation via a cronjob. That gives us a very simple but effective secondary backup system for all content changes. All content editing is done on a private staging server. The production server does not have a panel installation at all. When content changes are made in the panel on the staging server, the editors can publish those changes to the production server with a small button on Kirby’s dashboard. In the background the production server simply pulls the latest content from Gitlab coming from the staging server.
Nimbus has a massive catalogue of led luminaires. Each product has subproducts with lots of documents and files, which can be downloaded by visitors. Downloads are automatically bundled by product with custom routes, which start a PHP Zip script.
All construction illustrations for luminaires are stored as EPS files coming from the design department. Those EPS files are converted with ImageMagick to PNGs and displayed on the product pages.
Nimbus has a great collection of real life projects, which use their luminaires. For all those projects the editors can add as many pictures as they have available and set in the panel which luminaires have been used in each picture with a simple file field. On the product pages Kirby will then pull in a list of all related projects and also create a nice gallery with random project pictures.
Internally the website is used as an important source for employees and retailers to fetch information about their product catalogue. For each product family and product there’s a simple URL-based API, which can be used to export Excel sheets with all the data available. Those Excel sheets are generated on the fly.
The site has many other features, including an Angular-based Product search, a file-based retailer database, a massive news archive and more. We are currently also working on an integration with their SAP system to import all product updates directly into Kirby and use it as a single data source.