Any plans to support custom Inertia pages/templates?

[Anubarak]

Just a quick question as it would kinda influence the way I am going to work with Craft and the way I'll prepare my code.

Are there any plans to execute hooks/callbacks during your intertia initialization?
I am talking about this part:

cms/resources/js/bootstrap/cp.ts

Lines 81 to 103 in 4cfed41

	await createInertiaApp({
	pages: '../pages',
	title: (title) => `${title} - ${this.$config.get('systemName')}`,
	withApp(app) {
	app.provide(Queue, queue);
	app.provide(Axios, axios);
	app.provide(Config, config);
	app.provide(Craft, config);
	app.component('QueueManager', QueueManager);
	app.component('QueueManagerToolbar', QueueManagerToolbar);
	app.component('DeprecationErrors', DeprecationErrors);
	app.component('DeprecationErrorsToolbar', DeprecationErrorsToolbar);
	app.component('ClearCaches', ClearCaches);
	app.component('FindReplace', FindReplace);
	app.component('DatabaseBackup', DatabaseBackup);
	app.component('Migrations', Migrations);
	app.component('Updates', Updates);
	app.component('ProjectConfig', ProjectConfig);
	app.component('AssetIndexes', AssetIndexes);
	app.component('SystemMessages', SystemMessages);
	},
	});

Since you already published a few packages of yours (thank you very much for that, it's an awesome way to interact with the CP) it would be an incredible way to have a custom / empty Interia view with just an empty <component :is template where we as plugin developers could hook into and register our custom component in your hook.

Kinda like this

window.Cp.booting((CpInstance, app) => {
    app.component('MyCustomComponent', MyCustomComponent);
})

or

window.Cp.registerComponent('MyCustomComponent', MyCustomComponent);

So we could do things like this:

  return new CpScreenResponse()
        ->inertiaPage('your/general/page', [
            'component' => 'MyCustomComponent'
        ]);

Or even better

  return new CpScreenResponse()
        ->customInteriaPage('MyCustomComponent', [
            // other data
        ]);

and you would then render a general AppLayout with our component (or even better make '@/common/layouts/AppLayout.vue' usable for us). That would be change the way we could work with Craft and really be awesome.

Btw Craft 6 is really awesome to use. I really like the direction you are going.

[brianjhanson]

Plans? Definitely. Concrete ones? Not quite yet. I imagine we'll do something along the lines of that Statamic does which would allow plugin developers to register their own Vue components to be rendered within the CP.

import CustomComponent from './path/to/custom-component';

window.Craft.booting(({components}) => {
  components.register('custom-component', CustomComponent);
});

For full pages, I'm currently thinking we'll take the second approach you mentioned and provide plugin developers layouts they can use. At the least we'll provide composables or something that will let you replicate our layouts without too much trouble.

[Anubarak]

That's great, thank you very much for your fast reply. I highly appreciate it - would love such a way to work with Craft CMS. So far I really like the solution you came up with when it comes to the new frontend mechanisms.