docs: Subscribe links on blog pages, x link in footer

amannn · Oct 30, 2024 · e1e10a6 · e1e10a6
1 parent eef6ab1
commit e1e10a6
Show file tree

Hide file tree

Showing 8 changed files with 26 additions and 8 deletions.
diff --git a/docs/src/components/Footer.tsx b/docs/src/components/Footer.tsx
@@ -21,6 +21,10 @@ export default function Footer() {
           <FooterLink href="/blog">Blog</FooterLink>
         </div>
         <div>
+          <FooterLink href={config.xUrl} target="_blank">
+            X / Twitter
+          </FooterLink>
+          <FooterSeparator />
           <FooterLink href={config.githubUrl} target="_blank">
             GitHub
           </FooterLink>

diff --git a/docs/src/components/StayUpdated.mdx b/docs/src/components/StayUpdated.mdx
@@ -0,0 +1,6 @@
+<hr className="my-8" />
+
+**Stay in the loop:**
+
+- [GitHub releases](https://github.com/amannn/next-intl/releases)
+- [X (Jan Amann)](https://twitter.com/jamannnnnn)
diff --git a/docs/src/config.js b/docs/src/config.js
@@ -4,5 +4,6 @@ module.exports = {
   baseUrl: process.env.VERCEL_PROJECT_PRODUCTION_URL
     ? 'https://' + process.env.VERCEL_PROJECT_PRODUCTION_URL
     : 'http://localhost:3000',
-  githubUrl: 'https://github.com/amannn/next-intl'
+  githubUrl: 'https://github.com/amannn/next-intl',
+  xUrl: 'https://x.com/jamannnnnn'
 };
diff --git a/docs/src/pages/blog/date-formatting-nextjs.mdx b/docs/src/pages/blog/date-formatting-nextjs.mdx
@@ -3,6 +3,7 @@ title: Reliable date formatting in Next.js
 ---
 
 import {Tweet} from 'react-tweet';
+import StayUpdated from '@/components/StayUpdated.mdx';
 
 # Reliable date formatting in Next.js
 
@@ -327,3 +328,5 @@ While the main focus of this post was on date formatting, there are a few relate
 1. [API and JavaScript Date Gotcha's](https://www.solberg.is/api-dates) by [Jökull Solberg](https://x.com/jokull)
 2. [The Problem with Time & Timezones](https://www.youtube.com/watch?v=-5wpm-gesOY) by [Computerphile](https://www.youtube.com/@Computerphile)
 3. [`date-fns`](https://date-fns.org/) by [Sasha Koss](https://x.com/kossnocorp)
+
+<StayUpdated />
diff --git a/docs/src/pages/blog/index.mdx b/docs/src/pages/blog/index.mdx
@@ -29,4 +29,4 @@ import BlogPostLink from '@/components/BlogPostLink';
   />
 </div>
 
-Subscribe for updates: [Jan Amann on X](https://x.com/jamannnnnn)
+Subscribe for updates: [X (Jan Amann)](https://x.com/jamannnnnn)
diff --git a/docs/src/pages/blog/next-intl-3-0.mdx b/docs/src/pages/blog/next-intl-3-0.mdx
@@ -3,6 +3,7 @@ title: next-intl 3.0
 ---
 
 import PartnerContentLink from '@/components/PartnerContentLink';
+import StayUpdated from '@/components/StayUpdated.mdx';
 
 # next-intl 3.0
 
@@ -189,6 +190,6 @@ A special thank you goes to <PartnerContentLink href="https://crowdin.com/">Crow
 
 —Jan
 
----
-
 (this post has been updated from an initial announcement for the 3.0 release candidate)
+
+<StayUpdated />
diff --git a/docs/src/pages/blog/next-intl-3-22.mdx b/docs/src/pages/blog/next-intl-3-22.mdx
@@ -3,6 +3,8 @@ title: next-intl 3.22
 subtitle: Incrementally moving forward
 ---
 
+import StayUpdated from '@/components/StayUpdated.mdx';
+
 # next-intl 3.22: Incrementally moving forward
 
 <small>Oct 21, 2024 · by Jan Amann</small>
@@ -234,7 +236,4 @@ With these changes out of the way, users can upgrade to modern APIs at their own
 
 —Jan
 
-**Stay in the loop:**
-
-- [GitHub releases](https://github.com/amannn/next-intl/releases)
-- [X (Jan Amann)](https://twitter.com/jamannnnnn)
+<StayUpdated />
diff --git a/docs/src/pages/blog/translations-outside-of-react-components.mdx b/docs/src/pages/blog/translations-outside-of-react-components.mdx
@@ -2,6 +2,8 @@
 title: How (not) to use translations outside of React components
 ---
 
+import StayUpdated from '@/components/StayUpdated.mdx';
+
 # How (not) to use translations outside of React components
 
 <small>Apr 21, 2023 · by Jan Amann</small>
@@ -135,3 +137,5 @@ If you’ve been working with React for a longer time, you might have experience
 By limiting ourselves to only format messages during render, we're in a similar situation: The rendered output of translated messages is always in sync with app state and we can rely on the app being consistent.
 
 Related: ["How can I reuse messages?" in the structuring messages docs](/docs/usage/messages#structuring-messages)
+
+<StayUpdated />