My config

php
'enabled' => [
        'buckets' => true,
    ],

    'buckets' => [
        'homepage' => [
            'name' => 'Homepage',
            'buckets' => [
                'post_feature' => [
                    'name' => 'Featured Blog - Big',
                    'bucketables' => [
                        [
                            'module' => 'posts',
                            'name' => 'Posts',
                            'scopes' => ['published' => true],
                        ],
                    ],
                    'max_items' => 1,
                ],

                'post_top' => [
                    'name' => 'Side Feature - Top',
                    'bucketables' => [
                        [
                            'module' => 'posts',
                            'name' => 'Posts',
                            'scopes' => ['published' => true],
                        ],
                    ],
                    'max_items' => 1,
                ],

                'post_mid' => [
                    'name' => 'Side Feature - Middle',
                    'bucketables' => [
                        [
                            'module' => 'posts',
                            'name' => 'Posts',
                            'scopes' => ['published' => true],
                        ],
                    ],
                    'max_items' => 1,
                ],

                'post_bot' => [
                    'name' => 'Side Feature - Bottom',
                    'bucketables' => [
                        [
                            'module' => 'posts',
                            'name' => 'Posts',
                            'scopes' => ['published' => true],
                        ],
                    ],
                    'max_items' => 1,
                ],
            ],
        ],
    ],

The page looks like my expectations 😄

you could also query all buckets in a single query:

Feature::whereIn('bucket_name', ['post_feature', 'post_top', 'post_mid', 'post_bot'])->get()

then you'd get a collection where each item will have a

featured

relationship giving you access to the posts

Aaah I see

Thanks

Haven't measured it extensively (if at all) but from my experience, there's no significant performance penalty if your tables are indexed properly. For example,

related

is indexed by

browser_name

. I don't even think there's any real overhead on the Laravel side because the fully qualified model is stored in the DB.

Thanks for the information

something that's mentioned in the buckets documentation that is actually a recommendation overall is to setup morph maps for your Twill models

this does 2 things: you can change namespace without having to modify your database records, and it helps Twill for some features like search or buckets

I'm running in blocks not rendering issue with Twill 2.0 this is working in production it shows a text field on each block I digged the GH Issues and went on the docs to see the proper workflow for generating blocks in case I missed a step https://twill.io/docs/#development-workflow I possibly found a typo: "As of verison 2.2, it is not necessary to rebuild Twill's frontend when working with blocks anymore. Their templates are now dynamically rendered in Blade and loaded at runtime by Vue. (For <2.1.x users, it means you do not need to run php artisan twill:blocks and npm run twill-build" So me a < 2.1 user need or not to run npm run twill-build? either way from the laravels root folder I get missing script twill-build (maybe I have to go to twill's root)

verison is typoed too in that quoted text

You're right, I don't think

npm run twill-build

is right

It would be

php artisan twill:build

and if something is as of version 2.2 then users > 2.1 do not need

the no-build workflow is available since 2.0: https://github.com/area17/twill/blob/2.x/CHANGELOG.md#blocks-and-frontend-build-workflow

if you use custom Vue blocks, you still need to build

Thank you both I don't mean to suck dry your time No our block aren't custom as far as I can tell.

No worries 🙂 So, on Twill 2.0 you could simply create your blocks as single Blade files under

views/admin/blocks

did you try running

php artisan twill:update

?

php artisan twill:build worked for me

no this is a repeater, not custom

hmm. kinda puzzled now about the inner workings then but I'm still learning it maybe one day I can contribute a PR to pay you back guys 🙂

for now I will just keep in mind that twill build may solve blocks not rendering issue.

Yeah, there's some overlap conceptually (and visually) between blocks/repeaters/browsers... I get the confusion. Don't hesitate to suggest some updates to the docs, that would be more than welcome!

My confusion was mostly on the part that I use 2.0 and I still had to twill build to get those to render

but sure now I'm heads down on docs on my free time so I will try to Pr typos or suggestions if I track any

How to properly select a post based of a slug? and why is this not clearly found in the docs? I search on slug and slugs. And I might read over it but I cannot find it

@User for clarity, I think

twill:update

would have solved it for you