Storing your uploaded assets in Digital Ocean Spaces is a great alternative to S3, and less of a pain in the ass than storing them in a local folder, no more having to manually sync files back and fourth.

Cache busting is telling the browser to refetch assets because they have changed, caching assets allows the browser to retain a file "in memory" without having to download it each time it visits your website, making the page load faster, however if you have done some changes to the styling or logic in your JS, you want to "bust the cache" so the browser gets the new updated files.

In Craft CMS 3.1 the long awaited project config feature was added, which, when an administrative setting (channel is added, field is created or updated, assigned to a section, or plugin installed) is updated, the project.yaml file in the config folder will store the change, you can then "sync" those changes to the production database when deploying your changes, here is how our team utilize this feature.

Learn how to mark your navigation links with an active class in Craft CMS using Twig macros and various other methods.

At our agency (Guilty AS) we use Mailgun as the email sending service of choice for transactional emails, here is how we add support for it in our Craft CMS projects.

I've recently experimented with the awesome plugin "Blitz", which is a full page caching plugin for Craft CMS that generates static HTML files of your pages, so you can serve them ultra-fast using Nginx or Apache.

Hubspot is a marketing automation suite of tool that allows marketers to create landing pages, blog posts, hosted lead forms, and also comes with a CRM system, when a company is already using Hubspot to power their content marketing, but are looking to refresh their website, they might want to integrate the existing content from their HubSpot portal into their new website, we at Guilty encountered this with one of our latest project, and thought we might as well build a plugin for this that can be used by our self and others in the future to make this task a bit easier.

If you're using Laravel Forge as your hosting and provisioning tool, you might come across instances where you need to connect to a remote database via a kocal GUI tool like Sequel Pro or HeidiSQL, but Forge by default only allows SSH connections, here is how to get around it.

Depending on your own and your team's workflow, disabling the ability for clients and developers to update the CMS and plugins in a production environment might be a smart thing to do to simplifiy your deployment strategy, here is how.