Blog or content site with an admin
FreeSystem map@rabbinatix/blog-cms-architecture by Rabbinatixupdated Oct 13, 2026
A public website reads posts from your content API; editors write them in an admin app; images go to an image service.
4 systems and 8 APIs. Every API is declared on both sides, so every contract starts healthy. Rename or change anything once it is on your map.
3 connections · 8 APIs
- Public Website → Content API
GET /api/v1/postsPostsGET /api/v1/posts/{slug}One post
- Admin App → Content API
GET /api/v1/postsPostsPOST /api/v1/auth/registerCreate an accountPOST /api/v1/auth/loginLog in with email and passwordPOST /api/v1/auth/logoutLog outPOST /api/v1/postsWrite a postPUT /api/v1/posts/{id}Edit a post
- Admin App → Image Service
POST /v1/uploadUpload an image
Systems (4)
Public Website
What readers see.
Admin App
Where editors write and publish.
Content API
Posts, pages and editors.
Image Service
Stores and resizes images, like Cloudinary.
A system you already have under the same name is used, not copied. Outside APIs don't count towards your plan.
Also as a flow
Versions
