Write article: Why Slugkit Starts with an API Contract #21

New issue

Open

opened 2026-06-27 14:43:44 -05:00 by erik · 0 comments

erik commented

2026-06-27 14:43:44 -05:00

Owner

Draft and publish a developer-focused article about the Slugkit API-first architecture.

Angle: The stable API contract is the shared piece; OpenAPI and metadata discovery make independent sites manageable by common tooling.

Outline:

/api/v1 as the compatibility surface.
GET /meta and OpenAPI discovery.
OpenAPI as source of truth.
Standardized error responses.
501 Not Implemented for optional/unsupported operations.
Why the CLI should not assume public website routes.
How this enables automation without centralizing site code.

Draft and publish a developer-focused article about the Slugkit API-first architecture. Angle: The stable API contract is the shared piece; OpenAPI and metadata discovery make independent sites manageable by common tooling. Outline: - `/api/v1` as the compatibility surface. - `GET /meta` and OpenAPI discovery. - OpenAPI as source of truth. - Standardized error responses. - `501 Not Implemented` for optional/unsupported operations. - Why the CLI should not assume public website routes. - How this enables automation without centralizing site code.

erik added the

labels

2026-06-27 14:43:44 -05:00