I'm not sure if the title describes my problem. But I would like the user to have the option to add or remove one or more fields as is possible in the Gallery Block. I'm not sure if there already is a way to do this or if this doesn't really fit in with Automad. I'm thinking of developing it myself. If I have to do that in the end, could you give me some pointers of code I could reuse or where I should add it in. I hope you understand what I mean and would be very happy for some help. 😃 To demonstrate what I wish to do, here a few examples: Include project.php: <article class="projekt"> <h2>@{ title }</h2> <h3>@{ subtitle }</h3> <p>@{ text }</p> <img src="" alt=""> </article> if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Implementation in template: <section id="projekte"> <@ multi project.php @> </section> if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } I used a sort of prefix called "multi" which would add a button and define if the snippet is repeatable or not. PS: I used an include... maybe a snippet would be better for this idea.

Repeatable Fields

hudson

I'm not sure if the title describes my problem. But I would like the user to have the option to add or remove one or more fields as is possible in the Gallery Block. I'm not sure if there already is a way to do this or if this doesn't really fit in with Automad. I'm thinking of developing it myself. If I have to do that in the end, could you give me some pointers of code I could reuse or where I should add it in. I hope you understand what I mean and would be very happy for some help. 😃

To demonstrate what I wish to do, here a few examples:

Include project.php:

<article class="projekt">
  <h2>@{ title }</h2>
  <h3>@{ subtitle }</h3>
  <p>@{ text }</p>
  <img src="" alt="">
</article>

Implementation in template:

<section id="projekte">
  <@ multi project.php @>
</section>

I used a sort of prefix called "multi" which would add a button and define if the snippet is repeatable or not.

PS: I used an include... maybe a snippet would be better for this idea.

mad

hudson Hi there. I think a block field is covering that functionality, or maybe i misunderstand you?

hudson

mad Yes, the block field does cover the kind of functionality I am looking for. But not quite in the way I was thinking. In the block field you can add and remove many different single types of content. What I am looking for is a way to "extend" any field or group of fields (maybe except for the block field) so the user can add or remove 1 or more of that certain field or group of fields. The block field is great but sometimes I feel like it gives too much room for error to the user. Sometimes I would like to specify what the user can do instead of give the everything. And it would be cool to be able to add a group of fields at once instead of each one separately (not aware if this is possible already). I'm not sure if this is a direction you want to take with automad but I have had some use-cases where it would be helpful. 🙂

PS: maybe another way to do this would be to be able to customize a block field to limit it to certain types of content 🤷

mad

hudson I'm sure it will be supported in one or another way in the future. I guess it would be already enough to be able to define fields along with custom snippet blocks. That is however not possible yet since the UI has to be updated to support fields in custom snippets.

hudson

An example:

I have employees on a website. Each employee needs certain fields: photo, name (text), info (textbox). The number of employees can change, but I would like to only provide the fields needed in the backend. So if you add a new employee you get another set of photo, text and textbox fields to fill out and the CSS places them correctly. In the block field anything can be added, you have to add the fields separately, there can be unwanted content and it's harder to place and style with CSS.