Thinkmill / Thinkmill/keystatic
Document custom blocks
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 159
- Avg merge
- 21h 41m
- Merged PRs (30d)
- 2
Description
Keystatic should aim to support at its core the ability to add our own field (and collection types if that can be done)
Coming from TheOtherPopularPlatform™️ , people would probably expect it to be able to:
- define the field storage data type
- define serialiser and deserialiser behaviour
- define how the UI of the field functions
additionally, (and seperately)
Something that didn't make sense to me from TheOtherPopularPlatform™️ was
- define how the renderable preview result would look while in the cms? Why cant we just support Customising how an item in a collection is rendered as a preview?
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 by breaking down the requested custom field and collection capabilities: storage types, serialization and deserialization, field UI, editor plugins, and collection previews. Done would require a defined, implemented approach for these extension points, but the issue does not mention specific files, tests, or entry points to inspect.
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
- Needs clarification
- Newbie friendliness
- 25/100