Map

The site map is how you layout the various routes in your application. It is divided into two sections ‘web’ and ‘api’. Public routes will go in the ‘web’ domain where api routes will go in ‘api.’ If you would like to include a version number in the path of your api, you can configure the api route in the config file.

Each level of the domain gets defined as a

api

woo

todo: Return list of all parents

web

woo

children

foo man choo

type

default

By default a route will generate a single action controller with a __invoke() method. A todo will be included to implement the default controller, and can be over written by a more explicit todo.

crud

Set the type to CRUD to create templated Create, Read, Edit, Destroy and Index views. If an entity is included, the methods will be templated for the entity and each visible field on the entity. If no entity is present, it will template the methods and provide Todos to complete the methods. Some of the specifics will change based on the chosen frontend.

directory

The directory interface is a single page interface with a searchable index of all records, and a preview panel to view the full record. From the view the user can click on the content and be able to edit it. Changes are stored to a dirty state until the user chooses to save their changes or press enter. The view is currently only available for Livewire. An inertia frontend is coming.

methods

If present the methods array will overwrite any methods. Available methods are index, create, store, show, edit, update, destroy, and directory.

frontend

default: set in config The default frontend can be set in the architect config file, or can be specified for each web route. Options are blade, livewire, or inertia

todo

default: Implement method Todos are added to each route which isn’t scaffolded.