It's not uncommon for us to want to be able to delete an object property from an api response and when you have complete control over the api request/response cycle this may not be an issue. But, when you're consuming third-party services where the shape of the object may be of an unknown size or depth, or variable in shape, ensuring that sensitive data is not being leaked out is important. This short snippet will show you how you can remove keys of any depth in an object by taking advantage of a nifty little helper library omit-deep-lodash (that only has lodash as a dependency).

Following on from Part 1, this instalment of the post will show how you can generate nested slugs in Strapi by using the relationship fields to parent/child pages and the Page model's lifecycle hooks. Generating a full slug for each page will allow us to mimic the url structure typically found in a traditional CMS and will more accurately reflect the hierarchical nature of our content, particularly when you want your pages slugs closely resemble your navigational levels.

The JAM (Javascript / API's / Markdown) stack has been gaining huge traction in the last couple of years and has almost become the de-facto standard for many hobbyists, startups, and even enterprise-scale businesses looking to dip their toes into one of the hottest, modern development trends. Decoupling content from whatever framework or library you're using to render your frontend comes with it's own set of challenges, particular for those (like myself) who cut their teeth in more traditional content management systems (CMS) like Wordpress, Joomla and Drupal. This post is the first of 2 parts and looks at one solution I've been using to achieve relatively traditional navigation management in a headless CMS to provide flexibility on the frontend without sacrificing the ease-of-use for the end-user (and potentially the person paying for your services). The first part will look at setting up a basic slug system in Strapi and then using it to create a main menu which will be consumed by a simple React frontend. The second part will focus on generating nested slugs and adding additional levels to the menu.

To be honest, this post feels a bit weird to write (type?) as it's just about me and I find it pretty awkward being self-reflective and even struggle remembering how I ended up here at times, but hopefully it serves as an introduction into who I am, where I'm from and what has shaped me - all of which affects how I see problems and how I solve them.