adam/vscode-front-matter
1
0 Fork 0
mirror of https://github.com/estruyf/vscode-front-matter.git synced 2026-11-04 01:22:21 +01:00
Code Issues 77 Packages Projects Releases Wiki Activity

Enhancement: Website settings #614

New Issue
Open
opened 2026-10-05 02:56:26 +02:00 by adam · 1 comment
adam commented 2026-10-05 02:56:26 +02:00
Owner
Copy link
Copy source

I know this is far out because every SSG has a different system of adding settings, but in the end, those settings are in TOML, YAML, JSON, or INI-kind files. It would be nice to have some form of configurable option to load and edit items in the aforementioned formats and save them back.

This is a very un-thought-out idea and probably not easy to implement. But let's look for instance (selfishly) at GoHugo: We have a config directory with a _default subdirectory (or other "environment" subdirectories that are merged on top of _default when GoHugo runs). Then we have files like hugo.toml and module.toml in that _default directory. Those values are either key-value pairs or arrays and tables.

This principle could (in GoHugo) then later on even be adapted for the i18n folder that translates themes and modules.

I know this is a huge feature, so delete if it's a general "no thanks", or think about it :)

PS: there might be a general usefulness to have a TOML/YAML/JSON-to-form mechanism. Abstract without having to work on settings or translations.

PPS: Configuration option definitions could work based on a schemata file like the frontmatter schematas.

I know this is far out because every SSG has a different system of adding settings, but in the end, those settings are in TOML, YAML, JSON, or INI-kind files. It would be nice to have some form of configurable option to load and edit items in the aforementioned formats and save them back. This is a very un-thought-out idea and probably not easy to implement. But let's look for instance (selfishly) at GoHugo: We have a `config` directory with a `_default` subdirectory (or other "environment" subdirectories that are merged on top of `_default` when GoHugo runs). Then we have files like `hugo.toml` and `module.toml` in that `_default` directory. Those values are either key-value pairs or arrays and tables. This principle could (in GoHugo) then later on even be adapted for the `i18n` folder that translates themes and modules. I know this is a huge feature, so delete if it's a general "no thanks", or think about it :) PS: there might be a general usefulness to have a TOML/YAML/JSON-to-form mechanism. Abstract without having to work on settings or translations. PPS: Configuration option definitions could work based on a schemata file like the frontmatter schematas. <!-- github-sync-id:2200315680 -->
adam commented 2026-10-05 02:56:27 +02:00
Author
Owner
Copy link
Copy source

@davidsneighbour thanks for this suggestion 🙏

@davidsneighbour thanks for this suggestion 🙏 <!-- github-comment-id:2017547797 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/vscode-front-matter#614