The original idea was to have a configuration dashboard similar to VSCode, but more driven toward the settings of Front Matter.
This would make it easier, as you don't have to fiddle around in JSON and can, for instance, configure content types, manage your folders, and all other settings.
The original idea was to have a configuration dashboard similar to VSCode, but more driven toward the settings of Front Matter.
This would make it easier, as you don't have to fiddle around in JSON and can, for instance, configure content types, manage your folders, and all other settings.
<!-- github-comment-id:1272284102 -->
This is for programmers or other people? I don't see programmers having an issue reading or editing the settings file directly.
This is for programmers or other people? I don't see programmers having an issue reading or editing the settings file directly.
<!-- github-comment-id:1272418190 -->
I think there's value for both sorts of users. Arguably VS Code itself is for people who primarily write/edit plain text, and has a UI for settings. Given how Front Matter improves the UX/DevX of a lot of things I can already do myself in plaintext, I think that's an even bigger win for people less comfortable with editing JSON configurations by hand.
The ability to also provide better in-context documentation for users is something I don't think we should overlook either. In a JSON configuration, you only know about the available settings when they're already in place or if you know enough to auto-complete through the list of valid keys (hovering on each to see what they do until you find the right one). Being able to search settings, see the options and their current configuration alongside summary documentation, and click a link out to the docsite is a big win for UX in my opinion.
I think there's value for both sorts of users. Arguably VS Code itself is for people who primarily write/edit plain text, and has a UI for settings. Given how Front Matter improves the UX/DevX of a lot of things I can already do myself in plaintext, I think that's an even bigger win for people less comfortable with editing JSON configurations by hand.
The ability to also provide better in-context documentation for users is something I don't think we should overlook either. In a JSON configuration, you only know about the available settings when they're already in place or if you know enough to auto-complete through the list of valid keys (hovering on each to see what they do until you find the right one). Being able to search settings, see the options and their current configuration alongside summary documentation, _and_ click a link out to the docsite is a big win for UX in my opinion.
<!-- github-comment-id:1272436742 -->
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.
Settings overview page to make it easier to review each setting of the extension.
Is this directed at the dashboard or the documentation or both? Can you expand on this a little?
The original idea was to have a configuration dashboard similar to VSCode, but more driven toward the settings of Front Matter.
This would make it easier, as you don't have to fiddle around in JSON and can, for instance, configure content types, manage your folders, and all other settings.
I think this would be a great idea tbh.
This is for programmers or other people? I don't see programmers having an issue reading or editing the settings file directly.
I think there's value for both sorts of users. Arguably VS Code itself is for people who primarily write/edit plain text, and has a UI for settings. Given how Front Matter improves the UX/DevX of a lot of things I can already do myself in plaintext, I think that's an even bigger win for people less comfortable with editing JSON configurations by hand.
The ability to also provide better in-context documentation for users is something I don't think we should overlook either. In a JSON configuration, you only know about the available settings when they're already in place or if you know enough to auto-complete through the list of valid keys (hovering on each to see what they do until you find the right one). Being able to search settings, see the options and their current configuration alongside summary documentation, and click a link out to the docsite is a big win for UX in my opinion.