Feature: Content Type view #105

Open
opened 2026-10-05 02:25:41 +02:00 by adam · 4 comments
Owner

Create a view to define your content types and related fields.

Create a view to define your content types and related fields. <!-- github-sync-id:1014357474 -->
Author
Owner

I personally like the simplicity of defining this in JSON files, I would probably not use the UI that much.

I personally like the simplicity of defining this in JSON files, I would probably not use the UI that much. <!-- github-comment-id:970710757 -->
Author
Owner

Would you rather have an overview of all settings? To make it easier to configure these?

Would you rather have an overview of all settings? To make it easier to configure these? <!-- github-comment-id:971328865 -->
Author
Owner

I would probably look to the docs for that, with nice examples for each setting that I can copy/paste from. An example configuration file would be a nice place to start.
I did like using the Forestry UI to help me build some of the templates when I first started, but once I understood the file syntax/structure, I made future edits in the files directly. With CloudCannon, there isn't a UI and I was able to build up the configuration files with the docs and a little help from the devs. But their config file format was a bit harder to understand at first than yours is.

I would probably look to the docs for that, with nice examples for each setting that I can copy/paste from. An example configuration file would be a nice place to start. I did like using the Forestry UI to help me build some of the templates when I first started, but once I understood the file syntax/structure, I made future edits in the files directly. With CloudCannon, there isn't a UI and I was able to build up the configuration files with the docs and a little help from the devs. But their config file format was a bit harder to understand at first than yours is. <!-- github-comment-id:971640797 -->
Author
Owner

Oh, that is great to hear! So good documentation like always is the key to perfection 🤓. In that case, if you have recommendations on where docs can improve, or want to contribute, feel free to do so. Appreciate the help here.

Oh, that is great to hear! So good documentation like always is the key to perfection 🤓. In that case, if you have recommendations on where docs can improve, or want to contribute, feel free to do so. Appreciate the help here. <!-- github-comment-id:971746296 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/vscode-front-matter#105