(Note: @XertroV wrote the body)
there are some options for how to handle building a second UI output, we should think carefully in-case we want to add more UI outputs in future (e.g. to include accessibility features).
general patterns I can think of:
- create new packages using vue-cli and add the
ui package as a dependency; each of these new packages is a simple shim and all UI components are still kept in ui package
- outputs to a directory specific to the package (e.g.
./packages/ui-admin/dist)
- add a new output to
ui package via webpack config options
- outputs to new subdirectory (similar to what we do now where the app is published to ./dist/v/); example ./dist/admin
Personally I feel like option 2 is best here, which is what I've based the checklist below on
(Note: @XertroV wrote the body)
there are some options for how to handle building a second UI output, we should think carefully in-case we want to add more UI outputs in future (e.g. to include accessibility features).
general patterns I can think of:
uipackage as a dependency; each of these new packages is a simple shim and all UI components are still kept inuipackage./packages/ui-admin/dist)uipackage via webpack config optionsPersonally I feel like option 2 is best here, which is what I've based the checklist below on
./src/main.tsand./src/App.vue; maybe./src/entries/admin.tsand./src/entries/AdminApp.vue(which would give us a nice pattern for future)./dist/admin(like current UI outputs to./dist/v)./manageso we can choose individual UIs to build (optional: if it builds all of them that's fine too)