---
title: "#slack-platform articles | Hashnode"
description: "Explore the latest #slack-platform articles, tutorials, and guides on Hashnode."
url: "https://hashnode.com/tag/slack-platform"
---

Tag

# #slack-platform

0 posts · 0 followers

[SapotaCorp](https://hashnode.com/@sapotacorpvn) · [Jul 12](https://hashnode.com/posts/the-slack-app-manifest-yaml-structure-and-versioning/6a53c69a02e946222122ad17)

### [The Slack App Manifest: YAML Structure and Versioning](https://sapotacorpvn.hashnode.dev/the-slack-app-manifest-yaml-structure-and-versioning?utm_source=hashnode&utm_medium=feed)

Building the same Slack app across dev, staging, and prod by clicking through the UI is how config drifts and events stop firing. The Slack app manifest turns that whole setup into one YAML file you can version, diff, and promote.

8 min read · [sapotacorpvn.hashnode.dev](https://sapotacorpvn.hashnode.dev/the-slack-app-manifest-yaml-structure-and-versioning?utm_source=hashnode&utm_medium=feed)

[SapotaCorp](https://hashnode.com/@sapotacorpvn) · [Jul 12](https://hashnode.com/posts/slack-app-architecture-http-endpoints-vs-socket-mode/6a53c6f4759e8326f9c64a22)

### [Slack App Architecture: HTTP Endpoints vs Socket Mode](https://sapotacorpvn.hashnode.dev/slack-app-architecture-http-endpoints-vs-socket-mode?utm_source=hashnode&utm_medium=feed)

Picking between HTTP request URLs and Socket Mode is the first real architecture decision you make on any Slack app, and getting it wrong means a painful refactor later. Here is how the two connection models actually behave in production, w

9 min read · [sapotacorpvn.hashnode.dev](https://sapotacorpvn.hashnode.dev/slack-app-architecture-http-endpoints-vs-socket-mode?utm_source=hashnode&utm_medium=feed)
