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 -->
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 -->
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.
Default content folder for markdown files for the FrontMatter project is placed in the
.frontmattersubfolder, which I first perceived as a settings folder.The
frontmatter.jsonsettings 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...
Hi @DennisL68, the
.frontmatterfolder 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
pageFolderssetting defines where Front Matter will need to create your content, and thepublicFolderis the folder in which all your publicly accessible files live. This differs from the framework you use.Ok, I see. The folder
contentactually contains content type origin documents?Not necessarily; you can put these there. It is how you wish to link these.
Do you currently actually need a frontmatter.json file outside of the .frontmatter folder?
Yes, the
frontmatter.jsonfile is supposed to be outside of the.frontmatterfolder.