To further enhance the content creation process, it would come in handy to have a folder and file prefix option on the content type.
For instance, right now when a new article is created under the blog directory it is done as follows:
/blog/yyyy-MM-dd-slug.md
By using the prefix properties, it will be possible to create additional folders:
blog/2022/06/14/slug.md
To further enhance the content creation process, it would come in handy to have a folder and file prefix option on the content type.
For instance, right now when a new article is created under the blog directory it is done as follows:
- `/blog/yyyy-MM-dd-slug.md`
By using the prefix properties, it will be possible to create additional folders:
- `blog/2022/06/14/slug.md`
<!-- github-sync-id:1270790501 -->
Similar to #360, this setting can be defined on content type or page folder level.
Having the folderPrefix and filePrefix on folder level will allow using multiple content types and all content will be created the correct way for that folder.
Having it on the content type level means that this limits a content type to a certain folder. For example: if you only want this behavior on the posts folder, it could create issues when used on the content type.
If we introduce it on frontMatter.content.pageFolders, what would be the best names for them? @zivbk1 any ideas?
Similar to #360, this setting can be defined on content type or page folder level.
Having the `folderPrefix` and `filePrefix` on folder level will allow using multiple content types and all content will be created the correct way for that folder.
Having it on the content type level means that this limits a content type to a certain folder. For example: if you only want this behavior on the `posts` folder, it could create issues when used on the content type.
If we introduce it on `frontMatter.content.pageFolders`, what would be the best names for them? @zivbk1 any ideas?
<!-- github-comment-id:1156122859 -->
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.
To further enhance the content creation process, it would come in handy to have a folder and file prefix option on the content type.
For instance, right now when a new article is created under the blog directory it is done as follows:
/blog/yyyy-MM-dd-slug.mdBy using the prefix properties, it will be possible to create additional folders:
blog/2022/06/14/slug.mdSimilar to #360, this setting can be defined on content type or page folder level.
Having the
folderPrefixandfilePrefixon folder level will allow using multiple content types and all content will be created the correct way for that folder.Having it on the content type level means that this limits a content type to a certain folder. For example: if you only want this behavior on the
postsfolder, it could create issues when used on the content type.If we introduce it on
frontMatter.content.pageFolders, what would be the best names for them? @zivbk1 any ideas?This is available in the product, closing the issue.