-
-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: adding new UI scaffolding #1696
Conversation
I think we should change the |
I really would like to warn again that if we don't build blocks by blocks and adopt this strangler fig thing, it will be difficult to have this merged. I don't think we should build the entire layout right now, we should build components/views that should replace particular views in the legacy code. In addition you are already building parts that will probably be replaced in the near future, please be sure to follow or ask whether some parts should be build or not. The ideal roadmap for this would be:
|
That's fair. I'll take out the onboarding wizard but we still need the general layout and views. Edit: The plan has been to make the new UI as similar to the old UI as we can. Basic design should be carried over into the new web app. |
Vuetify 3 is now out of beta - https://github.com/vuetifyjs/vuetify/releases/tag/v3.0.0 EDIT: change Vue to Vuetify |
They are missing the datatables component, they should release it in 3.1 though. |
I know it's been a year... are we still planning to use Vue/Vuetify with Typescript, Vite, Storybook, Vue-i18n, etc.? Has there been any consideration of switching to React with Next.js or Svelte/Sveltekit? |
Starting again in a new PR. Closing this one. |
Apologies for not responding earlier, but, yes, the plan is still a Vue-based stack |
That's okay! I have the new stuff in a new PR. |
Description
With the official release of Vuetify 3 Beta, I'm restarting development of our new UI with Vue 3, the Composition API, and Vite. Typescript, Vue Router, Cypress, Vitest, and Storybook are also included. Most of it is boilerplate, and I'm hoping for assistance, same as before.
This code does not interact with the existing PHP UI, and is not copied to production folders during our install script.
The proposed URL nesting structure is as follows:
Todo:
Testing Notes
What I did:
This was created with
How you can replicate my testing:
Enter the
ui
directory and run