Adapt erikcraddock.me to Slugkit API #4

New issue

Open

opened 2026-05-19 19:51:44 -05:00 by erik · 0 comments

erik commented

2026-05-19 19:51:44 -05:00

Owner

Goal

Audit and adapt the current erikcraddock.me site against the Slugkit API contract so it can serve as the grounded reference implementation.

Reference docs: docs/reference-site-findings.md, docs/api-design.md, and all route specs in docs/specs/.

Requirements

Use the current repository ~/Private/code/github/evcraddock/erikcraddock.me as the reference; do not use erikcraddock-old.me.
Compare the current site API/OpenAPI behavior against the Slugkit API specs.
Identify mismatches in route names, resource terminology, request JSON, response JSON, auth behavior, OpenAPI operation IDs, and standardized error shapes.
Adapt the current site where practical to expose the Slugkit-compatible API surface.
Preserve existing site behavior unless the Slugkit contract intentionally changes it.
Document any contract gaps that cannot be adapted immediately and create follow-on tasks if needed.
Verify compatibility with slug doctor and representative CLI commands once available.

Acceptance criteria

Current erikcraddock.me API is audited against every Slugkit route spec.
API terminology uses Slugkit names such as contacts, generic social/audience routes, and /api/v1 where required.
Request and response JSON match the relevant Slugkit specs or documented gaps exist with follow-up tasks.
OpenAPI output matches implemented Slugkit-compatible routes and operation IDs.
Standardized auth, validation, not-found, and 501 Not Implemented responses are used where applicable.
slug doctor succeeds against the reference site when the CLI is available.
Representative content commands work against the reference site or have documented follow-up tasks.

Dependencies

task-c272cbda
task-47be19ea
task-782a7074
task-8fbb8c0c
task-e8b46ccd
task-43f5a652
task-fb0840e3
task-8b14c508
task-a5f5c185
task-11469f4d
task-b26679e3
task-64b4aa7e
task-7dac3c73

## Goal Audit and adapt the current `erikcraddock.me` site against the Slugkit API contract so it can serve as the grounded reference implementation. Reference docs: `docs/reference-site-findings.md`, `docs/api-design.md`, and all route specs in `docs/specs/`. ## Requirements - Use the current repository `~/Private/code/github/evcraddock/erikcraddock.me` as the reference; do not use `erikcraddock-old.me`. - Compare the current site API/OpenAPI behavior against the Slugkit API specs. - Identify mismatches in route names, resource terminology, request JSON, response JSON, auth behavior, OpenAPI operation IDs, and standardized error shapes. - Adapt the current site where practical to expose the Slugkit-compatible API surface. - Preserve existing site behavior unless the Slugkit contract intentionally changes it. - Document any contract gaps that cannot be adapted immediately and create follow-on tasks if needed. - Verify compatibility with `slug doctor` and representative CLI commands once available. ## Acceptance criteria - [ ] Current `erikcraddock.me` API is audited against every Slugkit route spec. - [ ] API terminology uses Slugkit names such as `contacts`, generic social/audience routes, and `/api/v1` where required. - [ ] Request and response JSON match the relevant Slugkit specs or documented gaps exist with follow-up tasks. - [ ] OpenAPI output matches implemented Slugkit-compatible routes and operation IDs. - [ ] Standardized auth, validation, not-found, and `501 Not Implemented` responses are used where applicable. - [ ] `slug doctor` succeeds against the reference site when the CLI is available. - [ ] Representative content commands work against the reference site or have documented follow-up tasks. ## Dependencies - task-c272cbda - task-47be19ea - task-782a7074 - task-8fbb8c0c - task-e8b46ccd - task-43f5a652 - task-fb0840e3 - task-8b14c508 - task-a5f5c185 - task-11469f4d - task-b26679e3 - task-64b4aa7e - task-7dac3c73

erik added the

labels

2026-05-19 19:51:44 -05:00

erik added

priority:low

and removed

priority:medium

labels