Update front matters (bump-sh#257)

Co-authored-by: Christophe Dujarric <[email protected]>

src/_guides/technical-writing/git-workflows-for-api-technical-writers.md

@@ -3,6 +3,7 @@ title: Git Workflows for API Technical Writers
 authors: james
 canonical_url: https://bump.sh/blog/git-workflows-for-api-technical-writers
 excerpt: Explore the challenges and solutions of keeping your docs in sync with an evolving API design using git workflows.
+date: 2024-06-20
 ---
 
 Technical writers are often challenged with keeping API documentation in sync with an ever-evolving API design. This article explores the challenges and solutions for tackling this ongoing struggle, focusing on parallel development and leveraging automation to streamline the process.

src/_guides/technical-writing/how-our-api-docs-can-ease-the-pain-of-api-deprecation.md

@@ -1,7 +1,9 @@
 ---
 title: How Our API Docs Can Ease the Pain of API Deprecation
 authors: james
-excerpt: 
+canonical_url: https://bump.sh/blog/how-our-api-docs-can-ease-the-pain-of-api-deprecation
+excerpt: API become deprecated for a variety of reasons. Discover good practices to plan and communicate about deprecations, and minimize disruptions
+date: 2024-07-04
 ---
 
 APIs are not static, as new operations are added and existing operations are improved as API usage grows. As customer and business needs evolve, APIs need to adapt as well. This often leads to the inevitable process of API deprecation – the gradual phasing out of an old API in favor of a newer, improved version.