Are you chatting with yourself or expanding on your question? 😄

As usual, the answer was found after posting the question. 😅

good, but its good you @ yourself, otherwise you might not know it yet 😄

Hi @User, if you're using the Glide image service, one solution for this would be to use

original_media_for_extensions

in

config/twill.php

:

'glide' => [
        'original_media_for_extensions' => ['gif'],
        
        // ...
    ],

This makes

$item->image()

return the original file for all

.gif

images.

I believe you also get animated thumbnails in the Media Library

That worked like a charm, thanks so much @User

Hello, Does Twill support dynamic header menus? Is there any possibility for the user to add the menus and not statically on the code?

Hey @User, this should be possible... I think! I'm curious to know what is your use case for this? Do you want to allow users to customize the content of the menu, like hide items that are not relevant to them?

Yes, and also sometimes the header menu might be too small for many links. Being able to do it dynamically by the user without code, would help alot.

Hi @User! do you mean the header menu on your frontend or inside Twill?

I mean inside Twill.

Cool. I think the best (maybe only) way to build the CMS menu dynamically is through your

AppServiceProvider

:

public function boot()
    {
        Config::set('twill-navigation', [
            // ...
        ]);
    }

But then the hard part would be to build your "menu builder", so to speak. You would need a module like

TwillMenus

that would enable CMS users to customize their own menu.

What about front-end? I mean how can the user inside the admin panel modify the header links just like in WordPress.

So that he writes them, or hides them.

From the admin panel.

@User I believe @User is meaning building a menu builder so that CMS users can manage frontend menus, not Twill's menu itself

Ah yes, makes sense! It's a much simpler problem then 🙂

@User One way is to create a

Menus

module, where each item is a specific menu in your site's layout (header, footer, etc.), then use a

menu-item

repeater in your

menus/form.blade.php

. There's a

link

field partial that be useful: https://github.com/sauron/twill-form-partials#link-field

@User in Twill you have to think about the content model behind your frontend features. A menu is a list of links, with a label, a position, a publication status, maybe a few other things. So the idea is to create a Twill module that represents exactly the needs of your menus, not the needs of every menus you could think of.

you can also leverage what community members are using for their own menu management like https://github.com/cwsdigital/twill-capsule-menus or https://github.com/bwat-dev/twill-capsule-menus

Hello , I have 2 block\_editors in one module. The blocks are saved correctly, but the menu with available blocks is showing only some of the blocks that are defined in "blocks" formField argument

this is my code

php
@formField('block_editor', [
            'name' => 'lesser-block-editor',
            'label' => 'These will be at the end of this page',
            'blocks' => ['text', 'text_image', 'gallery'],
        ])

    @formField('block_editor', [
            'name'=> 'supreme-block-editor',
            'label' => 'These will be at the top',
            'blocks' => ['text', 'image_text', 'gallery', 'sliding_wysiwyg'],
        ])

is it on purpose that you have multiple blocks with similar names but reversed?

that is on purpose

alright, are all those blocks registered correctly when using

php artisan twill:list:blocks

?

How would incorrectly registered blocks looked like?

they wouldn't show up or would produce an error

😅 I noticed that few of these doesn't exist at all in our project, I deleted them from the arrays but the existing ones still don't get showed

I just updated my code snippet

so looks like your screenshot is now correct for the first one, is the second one not showing the sliding_wysiwyg one?