Documentation is high on our list of priorities for UX. I know there is not much there right now to help people jump in and get started, but this is set to change now that a couple rather large undertakings have been completed. Namely, we have changed how the style engine works and moved to a Monorepo design that should help make it where you can either install all component packages or just install a few components.
Aurelia UX is the only repo being maintained. After we created the Aurelia UX Components repo, we made the decision to give Lerna a try, which made the separate repository for the components no longer necessary.
I suggest that the Aurelia team present a roadmap in all areas that it is working on.
For example, Server-side rendering (SSR) and even Aurelia-UX ,…
This helps the Aurelia community to better plan. For example, if I know that SSR will be released in the next 9 months, I will plan for this period. I’m sure this time is worth it because Aurelia will be the best in all areas
I hope we will soon see a roadmap for the Aurelia so that everyone can plan to use this fantastic project.
I sincerely thank all those involved in this project.
Aurelia has been the best client side project I’ve ever seen.
Why do you wait for aurelia-ux instead of choosing one of the existing ones like bootstrap, materialcss etc.?
Check out https://material-components-web.appspot.com those components will be easily integrated into your aurelia app (they were designed for use in modular SPA’s)
We agree with your three points. Especially because we’re evaluating a SPA framework for a long term project.
After the first evaluating round there stays Angular 2 and Aurelia. For me, Aurelia looks great and I really like the philosophy! There is just one uncertainty about the UX. We have seen, that there is an npm module ‘aurelia-ux’ (version 0.3.0) and a showcase application https://github.com/aurelia/app-ux-showcase. But there is also the npm module ‘@aurelia-ux/core’ (version 0.6.0) with the same documentation / showcase app, like in the module ‘aurelia-ux’. We googeld a while to find some statements about it, but unfortunately without success…
Is there a short and current documentation about Aurelia-UX? Is the showcase application up to date? Should we use aurelia-ux or @aurelia-ux/core and it’s dependents? We think @aurelia-ux/core…? Is there a short example or how-to for @aurelia-ux/core? Thanks for your help…
@dan here is a blog post that was published mid November that should help clear up some of your questions. Aurelia UX Overhaul.
To answer more directly, aurelia-ux is a legacy package at this point. The current package that should be used is @aurelia-ux/core. If you need the official Aurelia UX components the easiest package to bring in after that would be @aurelia-ux/components.
Currently all of the components have been split up into their own packages. This lets users pickand chose what they wish to use. Not everyone wants everything at once, but for those that do there is the components package. You can find all of the Aurelia UX packages here. NPM Aurelia UX
The UX Showcase is currently behind. Documentation is very high on the priority list, and in the coming weeks we should be figuring out just how to best put up documentation for Aurelia-UX. At that time the Showcase will likely be updated as well.
Currently all of the components have been split up into their own packages. This lets users pickand chose what they wish to use. Not everyone wants everything at once, but for those that do there is the components package.
You will not need to use Lerna. Lerna is a tool for managing multiple packages and nothing more.
With the new structure, you can include all of the components or chose to include just a few of them. Lerna simply allows us to build all of the components and perform releases very easily and quickly and has already proven to be a timesaver for us.
To be clear, each individual component is still a plugin, so if you want to install Aurelia UX and the components you would simply include the following:
Hello @dan; my team is in a similar situation and we’re looking at Aurelia and Vue (I prefer Aurelia but we are a team). Can you share with the community why you bypassed Vue in favor of Aurelia? I am sure many of us are facing the same challenge: convince our team that Aurelia is “better” than Vue despite all the hype/publicity Vue is currently enjoying. Thank you very much for sharing and for your time.
Hi @frankmonroe; We didn‘t have a close look at Vue, just a very short one. We had a closer look at Angular. So unfortunately, I can not really tell you a lot about Vue.
Clean code, convention over configuration, the framework in general (it stays out of your way) and the philosophy - just to name a few – let us choose Aurelia
One thing – which almost gave Angular the preference - was the UX. It looked, that Angular already has a lot to offer to create easy and nice looking GUIs. Things like good documentation, fast development, a lot of experience, Material Design… . Now with Aurelia UX everything looks a bit different. If documentation is coming and easy to understand examples, then for me Aurelia is the one.