Siegert Naber But indeed, we forgot to mention adding it in the article; it has now been updated. Sorry about that!

Hi Siegert Naber , I suppose you cloned the GitHub repository? But I'm not sure which branch you used, as the main branch already has this use : https://github.com/Codivores/tutorial-laravel-twill-inertia-vue3-vite-tailwind/blob/main/app/Providers/AppServiceProvider.php#L9

We find that Ziggy is a bit too complex for our needs, especially for a public website. The route export is quite verbose and, by default, it exports all routes unless they are filtered in the configuration file. As for Laravel Jetstream, I believe using Ziggy is not mandatory. You could simply remove the plugin use in the Vue entrypoints (app.js / ssr.js).

Yes, this should work with Laravel Jetstream (though we haven't tested it yet). You can use it as a foundation and adapt it to suit your project’s specific needs (although we prefer not to use the Ziggy package and instead inject our routes manually)

Not sure I understand the remark properly, the files from the external disks are copied one by one onto another external disk dedicated to backups (unless you prefer archiving locally, which doesn't seem like a very good idea to me 😁)

Hi Adrianito , thank you for your interest in our work! We haven't yet taken the time to look at this point in detail, but we believe it should be possible with significant Twill adaptations as we did for Module preview. Our customers don't really use the Editor so we prefer to disable it for the time being. We'll explore this further and keep you updated.