Site update

ferki · ferki · commit eb1bbc6d39fb · 2025-04-02T13:46:36.000+02:00
diff --git a/2025/04/02/rexfile-foundations/index.html b/2025/04/02/rexfile-foundations/index.html
@@ -49,8 +49,9 @@ <h1><a href="/2025/04/02/rexfile-foundations/">Rexfile foundations</a></h1>
     <section id="section-1">
         <p>Running ad-hoc commands as shown in <a href="/2025/03/21/minimum-viable-rex/">Minimum Viable
 Rex</a> provides a good way to start benefiting
-from Rex. Then sometimes we have to repeat our typical procedures. Other times
-it would work best if we could enable others to follow the same steps.</p>
+from <a href="https://www.rexify.org">Rex, the friendly automation framework</a>. Then
+sometimes we have to repeat our typical procedures. Other times it would work
+best if we could enable others to follow the same steps.</p>
 
 <p>Just like GNU Make uses a Makefile to describe actions, Rex uses a Rexfile to
 describe our common procedures as code through the following foundational
diff --git a/index.atom b/index.atom
@@ -18,8 +18,9 @@
         <content type="html"><![CDATA[
             <p>Running ad-hoc commands as shown in <a href="https://blog.ferki.it/2025/03/21/minimum-viable-rex/">Minimum Viable
 Rex</a> provides a good way to start benefiting
-from Rex. Then sometimes we have to repeat our typical procedures. Other times
-it would work best if we could enable others to follow the same steps.</p>
+from <a href="https://www.rexify.org">Rex, the friendly automation framework</a>. Then
+sometimes we have to repeat our typical procedures. Other times it would work
+best if we could enable others to follow the same steps.</p>
 
 <p>Just like GNU Make uses a Makefile to describe actions, Rex uses a Rexfile to
 describe our common procedures as code through the following foundational
diff --git a/index.html b/index.html
@@ -49,8 +49,9 @@ <h1><a href="/2025/04/02/rexfile-foundations/">Rexfile foundations</a></h1>
     <section>
         <p>Running ad-hoc commands as shown in <a href="/2025/03/21/minimum-viable-rex/">Minimum Viable
 Rex</a> provides a good way to start benefiting
-from Rex. Then sometimes we have to repeat our typical procedures. Other times
-it would work best if we could enable others to follow the same steps.</p>
+from <a href="https://www.rexify.org">Rex, the friendly automation framework</a>. Then
+sometimes we have to repeat our typical procedures. Other times it would work
+best if we could enable others to follow the same steps.</p>
 
 <p>Just like GNU Make uses a Makefile to describe actions, Rex uses a Rexfile to
 describe our common procedures as code through the following foundational
diff --git a/index.rss b/index.rss
@@ -13,8 +13,9 @@
             <description><![CDATA[
                 <p>Running ad-hoc commands as shown in <a href="https://blog.ferki.it/2025/03/21/minimum-viable-rex/">Minimum Viable
 Rex</a> provides a good way to start benefiting
-from Rex. Then sometimes we have to repeat our typical procedures. Other times
-it would work best if we could enable others to follow the same steps.</p>
+from <a href="https://www.rexify.org">Rex, the friendly automation framework</a>. Then
+sometimes we have to repeat our typical procedures. Other times it would work
+best if we could enable others to follow the same steps.</p>
 
 <p>Just like GNU Make uses a Makefile to describe actions, Rex uses a Rexfile to
 describe our common procedures as code through the following foundational
diff --git a/tag/rex.atom b/tag/rex.atom
@@ -18,8 +18,9 @@
         <content type="html"><![CDATA[
             <p>Running ad-hoc commands as shown in <a href="https://blog.ferki.it/2025/03/21/minimum-viable-rex/">Minimum Viable
 Rex</a> provides a good way to start benefiting
-from Rex. Then sometimes we have to repeat our typical procedures. Other times
-it would work best if we could enable others to follow the same steps.</p>
+from <a href="https://www.rexify.org">Rex, the friendly automation framework</a>. Then
+sometimes we have to repeat our typical procedures. Other times it would work
+best if we could enable others to follow the same steps.</p>
 
 <p>Just like GNU Make uses a Makefile to describe actions, Rex uses a Rexfile to
 describe our common procedures as code through the following foundational
diff --git a/tag/rex.rss b/tag/rex.rss
@@ -13,8 +13,9 @@
             <description><![CDATA[
                 <p>Running ad-hoc commands as shown in <a href="https://blog.ferki.it/2025/03/21/minimum-viable-rex/">Minimum Viable
 Rex</a> provides a good way to start benefiting
-from Rex. Then sometimes we have to repeat our typical procedures. Other times
-it would work best if we could enable others to follow the same steps.</p>
+from <a href="https://www.rexify.org">Rex, the friendly automation framework</a>. Then
+sometimes we have to repeat our typical procedures. Other times it would work
+best if we could enable others to follow the same steps.</p>
 
 <p>Just like GNU Make uses a Makefile to describe actions, Rex uses a Rexfile to
 describe our common procedures as code through the following foundational
diff --git a/tag/rex/index.html b/tag/rex/index.html
@@ -49,8 +49,9 @@ <h1><a href="/2025/04/02/rexfile-foundations/">Rexfile foundations</a></h1>
     <section>
         <p>Running ad-hoc commands as shown in <a href="/2025/03/21/minimum-viable-rex/">Minimum Viable
 Rex</a> provides a good way to start benefiting
-from Rex. Then sometimes we have to repeat our typical procedures. Other times
-it would work best if we could enable others to follow the same steps.</p>
+from <a href="https://www.rexify.org">Rex, the friendly automation framework</a>. Then
+sometimes we have to repeat our typical procedures. Other times it would work
+best if we could enable others to follow the same steps.</p>
 
 <p>Just like GNU Make uses a Makefile to describe actions, Rex uses a Rexfile to
 describe our common procedures as code through the following foundational
