Problem
The admin starter kit is intended to be a set of templates we can use to build admin systems in Laravel projects. Ideally it includes all the components we need for admin layouts. These will change over time as we add new layouts / update things.
How we can keep Laravel projects that use this repo up-to-date with new changes?
I see the admin templates as more of a design system than Amplify, which is a starting point for projects.
Solutions
We can review a few technical solutions on this, for example:
- Composer package, load the admin templates via Composer which means we'll have the CSS and base templates to use. We may need to override things in the local website we're working on.
- Node package, we've not done this before but it is a common way to load front-end package files (e.g. GOV UK Design System)
If we come up with a way to be able to keep the admin templates up-to-date what does this mean for HTML & CSS development on the admin templates work? Should this be kept more in sync with Amplify, what happens if it diverges? I'm not sure on the answer to these questions - but it would be good to discuss this.
Problem
The admin starter kit is intended to be a set of templates we can use to build admin systems in Laravel projects. Ideally it includes all the components we need for admin layouts. These will change over time as we add new layouts / update things.
How we can keep Laravel projects that use this repo up-to-date with new changes?
I see the admin templates as more of a design system than Amplify, which is a starting point for projects.
Solutions
We can review a few technical solutions on this, for example:
If we come up with a way to be able to keep the admin templates up-to-date what does this mean for HTML & CSS development on the admin templates work? Should this be kept more in sync with Amplify, what happens if it diverges? I'm not sure on the answer to these questions - but it would be good to discuss this.