Hi @delta107, Laravel has factories and seeders for that, is there something specifically you're trying to mock?

oh great I'll check Laravel documentation!

thanks, sometimes knowing what to search for is enough!

Is there a recommended approach for content which is shared across pages - e.g footer content, navigations, contact details? Is a specific 'Globals' module with a single record the way to do this, or is there a better way?

@User Not sure if it's the right/best way, but to do so, I use Twill Settings or modules and create a ViewServiceProvider to inject data in my blades templates (https://laravel.com/docs/8.x/views#view-composers)

View::composer('*', function ($view) {
            if (!request()->routeIs('admin.*')) {
                // Fathom Analytics.
                $fathom_site_id = Cache::rememberForever('site.fathom_site_id', function () {
                    return app(SettingRepository::class)->byKey('fathom_site_id') ?? '';
                });
                $view->with('fathom_site_id', $fathom_site_id);
            }
        });

        View::composer('site.layout.main', function ($view) {
            $locale = app()->getlocale();

            // Menu.
            $menuId = Cache::rememberForever('setting.menu.header', function () {
                return (int) app(SettingRepository::class)->byKey('menu_header_id') ?? '';
            });
            $menuHeader = Cache::rememberForever('menu.' . $locale . '.' . $menuId, function () use ($menuId, $locale) {
                $menu = Menu::getFront($menuId, $locale);
                if (null !== $menu) {
                    $menu->load('translations', 'blocks');
                }
                return $menu;
            });
            $view->with('menu_header', $menuHeader);
        });

Cool, thanks @User !

I fixed this error. now it is able to find my manifest file, but css isn't loaded anymore. How can i fix this. I am running twill:dev in my docker container.

Hello! I was wondering, how am I supposed to extend existing migrations? Especially when there are translation tables involved as well? Do I simply create 2 laravel migrations which would add new columns to the existing tables and everything will work out of the box, or is there a twill-way which is required?

Don't think there is a twill-way, I use classic migration files to add columns (if a feature adds columns in model and translation table, I group them in one migration file)

twill:dev

launches a dev server behind the scenes (

vue-cli-service serve

) which runs on port 8080. With sail, you can expose this port by adding to your `docker-compose.yml`:

services:
    laravel.test:
        ...
        ports:
            - '${APP_PORT:-80}:80'
            - '8080:8080'
        ...

How do you determine the "published" date?

do you mean without using

publish_start_date

?

hmm setPublishStartDateAttribute so as far as I understand this method sets it, but I don't understand why when I publish publish_start_date is not set

so who calls setPublishStartDateAttribute ?

well Laravel is when the property is being set

do you mean when you set it in the right sidebar, it doesn't save?

oh I see what your expectation is

you're expecting that it would change automatically on publish?

yeah

that's not what it does, it gives manual control to the user that's it

aha great thanks

you could totally implement it though

will think about it

during before or afterSave, you could check if the model was just published and programmatically change it

hmm oh great thanks for the idea!

Hi, how can i use/display handletags / tags in front end? something like $page->tags

You can use

getTags()

or `getTagsList()`: https://twill.io/docs/api/2.x/A17/Twill/Repositories/Behaviors/HandleTags.html

i dont get it...

What are you trying to get? All tags for one record?