Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://tane.codes/users/tanepiper/statuses/112360288340757526">Tane Piper ⁂ (tanepiper@tane.codes)'s status on Tuesday, 30-Apr-2024 22:53:16 JST</a><a href="https://tane.codes/@tanepiper" title="tanepiper@tane.codes"><img src="https://gnusocial.jp/avatar/28333-48-20221124175640.webp" width="48" height="48" alt="Tane Piper ⁂" style="position: absolute; left: 0; top: 0;">Tane Piper ⁂</a><div><a href="https://fediverse.zachleat.com/@zachleat/112360222393049309" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/74034" title="zachleat@fediverse.zachleat.com">Zach Leatherman :11ty:</a></li></ul></div></section><article><p><a href="https://fediverse.zachleat.com/@zachleat">@zachleat</a> <a href="https://mastodon.social/@deadparrot">@deadparrot</a> <a href="https://indieweb.social/@dries">@dries</a> Over on LinkedIn... </p><p>By what they (the MACH Alliance) term it I guess it's all the right letters and they are in some order, but really it's a database with a GraphQL API, an integration layer, some orchestration and another GraphQL layer.  But the big thing is it's domain specific and in the end most MACH are just distributed monoliths.</p><p>There's no magic frontend either.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3017433#notice-5990331">In conversation</a><time datetime="2024-04-30T22:53:16+09:00" title="Tuesday, 30-Apr-2024 22:53:16 JST">about 9 months ago</time> <span>from <span><a href="https://tane.codes/@tanepiper/112360288340757526" rel="external" title="Sent from tane.codes via ActivityPub">tane.codes</a></span></span><a href="https://tane.codes/@tanepiper/112360288340757526">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/2569162">Yep, MACH isn't just another website and isn't for all scales (a SME would go bust implementing some of these stacks) - as you say the key thing is it's part of organisational change management, not site migrations. The dirty secret about the headless CMS is that it is not a Content Management System - it's a database with some specific Ul and domain language on top for data that can be used as content in many systems - and that needs the plumbing to go with it - and for a lot of businesses those are domain specific.</a></label><br><a href="https://cdn.masto.host/tanecodes/media_attachments/files/112/360/275/380/543/583/original/461baa9c2dda01a7.png" rel="external">https://cdn.masto.host/tanecodes/media_attachments/files/112/360/275/380/543/583/original/461baa9c2dda01a7.png</a></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Tane Piper ⁂ (tanepiper@tane.codes)'s status on Tuesday, 30-Apr-2024 22:53:16 JSTTane Piper ⁂
in reply to
- Stefan Baumgartner
- Zach Leatherman :11ty:
@zachleat @deadparrot @dries Over on LinkedIn...
By what they (the MACH Alliance) term it I guess it's all the right letters and they are in some order, but really it's a database with a GraphQL API, an integration layer, some orchestration and another GraphQL layer. But the big thing is it's domain specific and in the end most MACH are just distributed monoliths.
There's no magic frontend either.
In conversationabout 9 months ago from tane.codespermalink
Attachments
1. Yep, MACH isn't just another website and isn't for all scales (a SME would go bust implementing some of these stacks) - as you say the key thing is it's part of organisational change management, not site migrations. The dirty secret about the headless CMS is that it is not a Content Management System - it's a database with some specific Ul and domain language on top for data that can be used as content in many systems - and that needs the plumbing to go with it - and for a lot of businesses those are domain specific.
  https://cdn.masto.host/tanecodes/media_attachments/files/112/360/275/380/543/583/original/461baa9c2dda01a7.png

Public

Embed Notice

HTML Code

Corresponding Notice