feat: add Resource collection for programmatic content#94
Open
riboflavin wants to merge 3 commits into
Open
Conversation
Introduce a dedicated Strapi collection for programmatic content with campaign grouping, separate from editorial Articles.
Add per-endpoint OpenAPI docs for the /resources REST API.
Refresh OpenAPI-derived client types and Strapi content type definitions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Resourcecollection for programmatic/batch content, separate from editorialArticle/ Learn content.campaignfield (kebab-case slug) for URL grouping; no categories, tags, authors, or featured for v1.@cowprotocol/cmsclient / Strapi types.Proposed site URL model (frontend follow-up)
/resources— list campaigns/resources/[campaign]— list resources in a campaign/resources/[campaign]/[slug]— resource detail (global slug uniqueness)Discoverability: footer link only (no main nav) in the companion cow-fi PR.
Post-merge ops
Please enable in staging/prod after deploy:
resource.find,resource.findOneThen publish a new
@cowprotocol/cmsversion so the cow-fi PR can depend on typed/resourcesendpoints.