You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not optimal because with this, during entry creation in the Admin UI, I have an extra form input (folderName) to fill, that feels unnecessary.
exportdefaultconfig({collections: {post: collection({label: 'post',path: 'src/content/post/**/',slugField: 'folderName',schema: {slug: fields.slug({name: {label: 'The title of the post'},slug: {label: 'SEO-friendly slug',generate(name){constslugify= ...
returnslugify(name);},},folderName: fields.slug({name: {label: 'Folder name input'},slug: {label: 'Folder name output',generate(name){constslugify= ...
constnow=newDate();return`${now.getFullYear()}-${now.getMonth()}-${now.getDate()}--${slugify(name)}`;},}}),
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
My goal
I'm wondering if it is possible to have this workflow?
File structure
. ├── content └── post ├── 2024-10-28--post-1 │ ├── hero.jpg │ └── index.mdoc ├── 2024-10-29--post-2 │ ├── 3.png │ ├── 2.png │ ├── hero.jpg │ └── index.mdoc └── 2024-9-30--post-3 └── index.mdocEntry Frontmatter
Public URL of entry when deployed
All reactions