This might be an opportunity for a tool like FrontMatter to write straight to the 'Portable Text' (PT) format and allow someone to build UI for editing it like you have enabled with fieldGroups.
Block versions are stored in the data structure for rendering all the blocks as they were prior to a version or specified date.
Translations of blocks stored in the data structure for rendering different target language versions of the content and for a translation UI in the editor.
As I start loading up markdown files with more and more 'page_sections' and fieldGroup blocks, it seems that maybe putting all that in Markdown files is not the most ideal way to move forward and that something like Portable Text has some advantages.
Essentially, a form of 'Santiy Studio' as a VS Code extension. This is a HUGE ask, so feel free to ignore it.
This has been something I have been thinking about quite a bit lately, but there was an article that connected some dots and inspired me to post this issue here. https://www.smashingmagazine.com/2022/02/thoughts-on-markdown/
This might be an opportunity for a tool like FrontMatter to write straight to the 'Portable Text' (PT) format and allow someone to build UI for editing it like you have enabled with fieldGroups.
Here are some links of interest:
- Sanity Projects - https://github.com/sanity-io/sanity
- PT Spec - https://github.com/portabletext/portabletext
- PT Editor - https://github.com/sanity-io/sanity/tree/next/packages/%40sanity/portable-text-editor
- PT Block Tools - https://www.npmjs.com/package/%40sanity/block-tools
I would be personally interested in using it for a SvelteKit site. https://github.com/portabletext/svelte-portabletext/
Some other ideas that come up from this concept:
- Block versions are stored in the data structure for rendering all the blocks as they were prior to a version or specified date.
- Translations of blocks stored in the data structure for rendering different target language versions of the content and for a translation UI in the editor.
As I start loading up markdown files with more and more 'page_sections' and fieldGroup blocks, it seems that maybe putting all that in Markdown files is not the most ideal way to move forward and that something like Portable Text has some advantages.
<!-- github-sync-id:1143765371 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Essentially, a form of 'Santiy Studio' as a VS Code extension. This is a HUGE ask, so feel free to ignore it.
This has been something I have been thinking about quite a bit lately, but there was an article that connected some dots and inspired me to post this issue here. https://www.smashingmagazine.com/2022/02/thoughts-on-markdown/
This might be an opportunity for a tool like FrontMatter to write straight to the 'Portable Text' (PT) format and allow someone to build UI for editing it like you have enabled with fieldGroups.
Here are some links of interest:
I would be personally interested in using it for a SvelteKit site. https://github.com/portabletext/svelte-portabletext/
Some other ideas that come up from this concept:
As I start loading up markdown files with more and more 'page_sections' and fieldGroup blocks, it seems that maybe putting all that in Markdown files is not the most ideal way to move forward and that something like Portable Text has some advantages.