From 8966f9e2336758073fc48f147dbf691d5902aabd Mon Sep 17 00:00:00 2001
From: Paul Buetow <paul@buetow.org>
Date: Sat, 7 Sep 2024 16:45:26 +0300
Subject: Update content for gemtext

---
 gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi     | 2 ++
 gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi.tpl | 2 ++
 gemfeed/atom.xml                                               | 4 +++-
 3 files changed, 7 insertions(+), 1 deletion(-)

(limited to 'gemfeed')

diff --git a/gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi b/gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi
index 56105315..4500e7bb 100644
--- a/gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi
+++ b/gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi
@@ -67,3 +67,5 @@ It is important that runbooks are not a "project to be finished"; runbooks have
 By structuring the onboarding process with KT sessions, shadowing, comprehensive runbooks, and a feedback loop, we've been able to fast-track the process from six months to just six weeks. This not only prepares our engineers for the on-call rotation quicker but also ensures they're confident and capable when handling incidents.
 
 If you're looking to optimize your on-call onboarding process, these strategies could be your ticket to a more efficient and effective transition. Happy on-calling!
+
+=> ../ Back to the main site
diff --git a/gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi.tpl b/gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi.tpl
index 9f71542b..b07e94fa 100644
--- a/gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi.tpl
+++ b/gemfeed/2024-09-07-site-reliability-engineering-part-4.gmi.tpl
@@ -64,3 +64,5 @@ It is important that runbooks are not a "project to be finished"; runbooks have
 By structuring the onboarding process with KT sessions, shadowing, comprehensive runbooks, and a feedback loop, we've been able to fast-track the process from six months to just six weeks. This not only prepares our engineers for the on-call rotation quicker but also ensures they're confident and capable when handling incidents.
 
 If you're looking to optimize your on-call onboarding process, these strategies could be your ticket to a more efficient and effective transition. Happy on-calling!
+
+=> ../ Back to the main site
diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml
index c243b8ba..927de5ef 100644
--- a/gemfeed/atom.xml
+++ b/gemfeed/atom.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <feed xmlns="http://www.w3.org/2005/Atom">
-    <updated>2024-09-07T16:40:35+03:00</updated>
+    <updated>2024-09-07T16:44:29+03:00</updated>
     <title>foo.zone feed</title>
     <subtitle>To be in the .zone!</subtitle>
     <link href="gemini://foo.zone/gemfeed/atom.xml" rel="self" />
@@ -89,6 +89,8 @@ jgs \\`_..---.Y.---.._`//
 <span>By structuring the onboarding process with KT sessions, shadowing, comprehensive runbooks, and a feedback loop, we&#39;ve been able to fast-track the process from six months to just six weeks. This not only prepares our engineers for the on-call rotation quicker but also ensures they&#39;re confident and capable when handling incidents.</span><br />
 <br />
 <span>If you&#39;re looking to optimize your on-call onboarding process, these strategies could be your ticket to a more efficient and effective transition. Happy on-calling!</span><br />
+<br />
+<a class='textlink' href='../'>Back to the main site</a><br />
             </div>
         </content>
     </entry>
-- 
cgit v1.2.3