Created a draft of messaging-first-architecture

.editorconfig

@@ -1,4 +1,4 @@
 root = true
 
 [*.md]
-max_line_length = 100
+max_line_length = 400

.gitignore

@@ -3,3 +3,28 @@
 *.iml
 out
 gen
+# build output
+dist/
+
+# generated types
+.astro/
+
+# dependencies
+node_modules/
+
+# logs
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+
+# environment variables
+.env
+.env.production
+
+# macOS-specific files
+.DS_Store
+
+pnpm-lock.yaml
+.vercel
+.vscode

AUTHORS.md

@@ -0,0 +1,6 @@
+| Zuhlke Abbrev | Full Name     | Email                     |
+| ------------- | ------------- | ------------------------- |
+| rumi          | Mika Ruch     | mika.ruch@zuehlke.com     |
+| madj          | Djordje Madic | djordje.madic@zuehlke.com |
+| patw          | Patrick Wilmes| patrick.wilmes@zuehlke.com |
+| tigr          | Tim Grünewald | tim.gruenewald@zuhlke.com |

LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 RATIU5
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -1,51 +1,80 @@
-# software-engineering-corner
+# the dev exchange
 
-Repository for our Zuehlke dev blog: [https://software-engineering-corner.zuehlke.com](https://software-engineering-corner.zuehlke.com)
+Repository for our Zuehlke dev blog: [https://thedevexchange.com](https://thedevexchange.com)
+
+## Are you a first time contributor?
+
+Create a PR where you add your name to the [AUTHORS.md](./AUTHORS.md) file.
 
 ## How to add a blog post
 
-To add new blog posts without having to ask for being added to the Zuhlke organization, the easiest way is forking this repository with your github user and write your blog post in your fork of this repository. If you need help with how forking works, please refer to this guide by github: https://docs.github.com/en/get-started/quickstart/fork-a-repo.
+To add new blog posts, fork this repository with your GitHub user and write your blog post in your fork of this repository.
+If you need help with how forking works, please refer to this guide by GitHub: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo
+
+Please start your post in the directory `src/articles/<article-name>`.
+After that, you can start working on your blog post in your repository.
+
+## Publishing the Article
+
+When you are ready, you can then open a pull request to this repository and set somebody from the organisation as the reviewer.
+Once you have created a PR, you will see a comment from Cloudflare with a preview URL, where you can preview the deployed article.
 
-Please start your post in the directory `drafts`. It will be moved to published as soon as it is actually published.
-After that, you can start working on your blog post in your repository. For information about the metadata in your blog post and specific markdown of Hashnode please refer to their template repository: https://github.com/Hashnode/Hashnode-source-from-github-template
+If you're unfamiliar with this, please refer to this guide on GitHub: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
 
-When you are ready you can then open a pull request to this repository and set somebody from the organization as the reviewer. As soon as this person has reviewed your PR and everything has been resolved, it can be merged into the main branch. If you're unfamiliar with this, please refer to this guide by github: https://docs.github.com/en/get-started/quickstart/github-flow
+As soon as this person has reviewed your PR and everything has been resolved, the editorial team will merge it into the main branch.
+**Please note**: **Merging the PR does not mean immediate publishing**.
+The editorial team creates a separate publishing timeline, ensuring consistent release cadence, topic diversity, and relevance.
+Please be patient, your article will get published eventually.
+Reach out to the editorial team privately if you need a time-sensitive publication.
 
-### Top Tip
+## Local Testing
 
-It is helpful to write each sentence on a new line. That can make reviews simpler for pinpointing comments. Markdown will ignore these new lines, and the paragraph structure will look as you intend. Take care in bullet point lists though, and validate with preview that it looks as you'd wish. 
+Astro powers the blog.
+You will need Node (or something similar, like Deno or Bun).
 
-## Frontmatter
+1. Install Dependencies: `npm install`
+2. Run: `npm run dev`
+3. Go to http://localhost:4321
 
-We recognized that there are some things which are important in the frontmatter of the articles:
+## Images
 
-1. Please add a `saveAsDraft: true` to the frontmatter. We will remove this when we publish the article.
-2. Please add a `hideFromHashnodeCommunity: false` to the frontmatter. This makes the blog post searchable from within Hashnode.
-3. Use your **Hashnode** username for `publishAs`. You can see it in the [Hashnode user settings](https://hashnode.com/settings).
-4. Use tags which are listed here [https://github.com/Hashnode/support/blob/main/misc/tags.json](https://github.com/Hashnode/support/blob/main/misc/tags.json) (use the **slug**) or ensure they exist via the Hashnode search (select "tags"). If you do it wrong, Hashnode may fail to import the article.
+Please add all the images to your article folder.
+Like this, astro can optimise them, and the readers have a better experience overall.
 
-If you like to have a table of contents shown, you can add `enableToc: true`.
-Only use it for longer articles.
+## Front Matter
 
-## Upload and use pictures
+```
+---
+title: <short title>
+description: <description for the rss feed>
+released: <date of when it will be released <- add todays date in ISO 8601 format here>
+cover: <path to the cover image>
+author: <Your Name>
+tags: <list of tags (they don't do anything yet)>
+shortDescription: <short description for sharing preview (twitter, facebook, linkedin) max 200 characters>
+---
+```
 
-To use pictures you can upload them with the Hashnode [uploader tool](https://hashnode.com/uploader). This will output a URL that you can include in your blog post.
+Please add this to the start of your article. For reference, please refer to the format of already published articles.
+
+## Top Tip
+
+It is helpful to write each sentence on a new line.
+That can make reviews simpler for pinpointing comments.
+Markdown will ignore these new lines, and the paragraph structure will look as you intend.
+Take care in bullet point lists, though, and validate with a preview that it looks as you'd wish.
 
 ## Style
 
 ### Point of View: I vs. We
 
-The use of "I" vs. "we" depends on whatever fits the context / type of article best.
+The use of "I" vs. "we" depends on whatever fits the context/type of article best.
 If it's about patterns/technologies/methods we regularly use and apply in customer projects, go with "we".
-In guides and walkthroughs "we" could also be applied, referring to author and reader, or a larger community (web devs, mobile engineers, technology sector, …).
-In general, only use "I" when talking about personal opinions, first-hand experiences, or when explicitly refering to you as the author.
+In guides and walkthroughs, "we" could also be applied, referring to the author and reader, or a larger community (web devs, mobile engineers, technology sector, …).
+In general, only use "I" when talking about personal opinions, first-hand experiences, or when explicitly referring to you as the author.
 
 ### Cover Image
 
 Look at previous articles on the blog page to get an idea of the desired style.
 Try to avoid overly complex imagery, text or diagrams, or screenshots.
 [Unsplash](https://unsplash.com) is a useful source for free high-quality images.
-
-## Links
-
-It seems that Hashnode adds backslashes when using an underscore in a URL. So encode underscores with "%5F".

astro.config.mjs

@@ -0,0 +1,33 @@
+// @ts-check
+import {defineConfig} from "astro/config";
+import tailwindcss from "@tailwindcss/vite";
+
+import react from "@astrojs/react";
+
+import expressiveCode from "astro-expressive-code";
+
+import mdx from "@astrojs/mdx";
+
+import sitemap from "@astrojs/sitemap";
+
+// https://astro.build/config
+export default defineConfig({
+  site: 'https://thedevexchange.com',
+  output: 'static',
+  vite: {
+    plugins: [tailwindcss()],
+  },
+
+  integrations: [react(), expressiveCode(), mdx(), sitemap()],
+
+  trailingSlash: 'always',
+
+  image: {
+    service: {
+      entrypoint: 'astro/assets/services/sharp',
+      config: {
+        limitInputPixels: false
+      }
+    }
+  },
+});