Thinkmill / Thinkmill/keystatic
Feature request : Better control over content organisation needed
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 159
- Avg merge
- 21h 41m
- Merged PRs (30d)
- 2
Description
As of now, content can be organized as explained in docs here
However, some of the projects needs better control content destination. Eg into year/month directories for example.
Decap CMS supports this - for example path: '{{year}}/{{slug}}' as explained here
It would be nice to see similar support in content static.
may be, path can support a template syntax which can use any of the fields from schema, or it could be made a function which takes the content object as argument and returns a path string.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the content organisation documentation linked in the issue and compare its current destination behavior with Decap CMS's collection-folder examples. Decide whether the supported API should use field-based templates or a function receiving the content object. Done means content destinations can be controlled for cases such as year/month directories and the behavior is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100