Add progressive enhancement in OOP post

[Bisaloo]

• The post specifies a license if you don't want to use the default CC BY
• All authors have an ORCID iD
• Relevant keywords / tags has been added. In particular, if you want your post to be shared on R-bloggers, you must tag it with R
• Images or other external resources have been committed and pushed
• The post uses pure quarto syntax, rather than HTML or R code, unless necessary

Right before merging:

• The date field has been updated
• All reviewers have been acknowledged in a short paragraph
• A PR has been opened in the blueprints to link to this post
• The post has been re-rendered and content of the _freeze/ folder is up-to-date

[netlify]

✅ Deploy Preview for tourmaline-marshmallow-241b40 ready!

Name	Link
🔨 Latest commit	2778702
🔍 Latest deploy log	https://app.netlify.com/sites/tourmaline-marshmallow-241b40/deploys/6687fb72b9b7570008d3fd9b
😎 Deploy Preview	https://deploy-preview-296--tourmaline-marshmallow-241b40.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[jamesmbaazam]

Thanks for the post, Hugo. I think it would have been nice to have more concrete examples but if that is not intended, this is still fine as nuggets of wisdom.

[jamesmbaazam]

I'm just realising we are inconsistent with the use of capitalisation and sentence case for our titles. We should probably harmonise this in a separate issue/PR.

[jamesmbaazam]

The statement "that downstream code uses good practice" doesn't follow smoothly after the command but I'm unsure of what you're trying to say.

[jamesmbaazam]

Thanks, Hugo. The added examples will enhance your points.