Feedback: Content is "hidden" in settings folder #373

Open
opened 2026-10-05 02:43:44 +02:00 by adam · 5 comments
Owner

Default content folder for markdown files for the FrontMatter project is placed in the .frontmatter subfolder, which I first perceived as a settings folder.
The frontmatter.json settings file is placed in the project root folder (which I'm quite happy with).

But shouldn't the root folder for the project also be the default content folder?
What is the purpose of hiding the content folder?

Edit: I noticed in the settings file that's there is some kind of distinction between publicFolder and pageFolders...

Default content folder for markdown files for the FrontMatter project is placed in the `.frontmatter` subfolder, which I first perceived as a settings folder. The `frontmatter.json` settings file is placed in the project root folder (which I'm quite happy with). But shouldn't the root folder for the project also be the default content folder? What is the purpose of hiding the content folder? Edit: I noticed in the settings file that's there is some kind of distinction between publicFolder and pageFolders... <!-- github-sync-id:1466335720 -->
Author
Owner

Hi @DennisL68, the .frontmatter folder is only for configuration. The content folder within it is for the configuration of the metadata of the content/media files.

Typically, you use Front Matter in configuration with a Static-Site generator or framework, which will define where the content is located. The pageFolders setting defines where Front Matter will need to create your content, and the publicFolder is the folder in which all your publicly accessible files live. This differs from the framework you use.

Hi @DennisL68, the `.frontmatter` folder is only for configuration. The content folder within it is for the configuration of the metadata of the content/media files. Typically, you use Front Matter in configuration with a Static-Site generator or framework, which will define where the content is located. The `pageFolders` setting defines where Front Matter will need to create your content, and the `publicFolder` is the folder in which all your publicly accessible files live. This differs from the framework you use. <!-- github-comment-id:1329214687 -->
Author
Owner

Ok, I see. The folder content actually contains content type origin documents?

Ok, I see. The folder `content` actually contains content **type** origin documents? <!-- github-comment-id:1332220010 -->
Author
Owner

Not necessarily; you can put these there. It is how you wish to link these.

Not necessarily; you can put these there. It is how you wish to link these. <!-- github-comment-id:1353243457 -->
Author
Owner

Do you currently actually need a frontmatter.json file outside of the .frontmatter folder?

Do you currently actually need a frontmatter.json file outside of the .frontmatter folder? <!-- github-comment-id:1430303508 -->
Author
Owner

Yes, the frontmatter.json file is supposed to be outside of the .frontmatter folder.

Yes, the `frontmatter.json` file is supposed to be outside of the `.frontmatter` folder. <!-- github-comment-id:1430936428 -->
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#373