We’re always looking for ways to support the Aurelia community and help you get the most out of Aurelia 2. To do that, I’d love to hear directly from you about the kinds of resources and content you’d like to see from us.
Would you benefit most from:
• Blog posts covering best practices, advanced features, or comparisons?
• Deep dives into specific Aurelia 2 concepts, patterns, or tools?
• Tutorials for building real-world applications, plugins, or integrations?
• Video content (e.g., YouTube) showing code walkthroughs, UI building, or tips and tricks?
• Livestreams for coding sessions, Q&A, or more collaborative content?
• Something else entirely?
We want to ensure the content we create aligns with what you actually need and enjoy consuming.
Let us know your ideas, wishlists, or even specific topics you’ve struggled with or want to learn more about. Your input will help shape the next wave of Aurelia resources.
Easy to reach community! Like, the Discourse is available from the menu, but the Discord is not mentioned.
And wrt the things you already mentioned: imho docs and tutorials are most important, deep dives help with general understandment. Blogs to show the world AU2 is still alive and kicking!
Video and livestreams for me are least important.
Wrt subjects: au1 to au2 migration is one of the most important things for us (one giant au1 app).
Another interesting one might be migrating from webpack to a faster alternative, again related to au1 to au2.
Another interesting point of interest might be how au2 compares to other frameworks (technical, standards, speed/benchmarks)
I’ve actually got a list in my notes of content ideas and Aurelia 1 to Aurelia 2 migration is one of the ideas at the top of the list, because I’ve heard this from others too, especially when it comes to things like routing and dynamic composition, plugins and whatnot.
The overall focus with the upcoming new site is a renewed focus on community and frequent content. The last blog post was from December 2023, which is too long. One of the reasons for that is the existing site isn’t a CMS and a bespoke convoluted process (which I’ve addressed). Hopefully the new site launches imminently and then going into 2025 keeping that moment up.
Migration is definitely the topic we’re most interested in.
We looked into aurelia2 during the alphas and the basic migration seems pretty straight forward.
What determines the costliness of migration is how much time we spend trying to understand subtle internals while chasing down our corner cases.
So content that helps resolve common misunderstandings and issues during migration could save us a lot of time, and would be greatly appreciated.
What I’d like to see is an example of setting up a modern workspace. I know I’m not alone with this setup. I have multiple applications within a single GIT repository and I rely on shared packages(plugins) that all live within that repo.
I currently rely on yarn 3.x I work in an environment where my code doesn’t have internet access (extra fun). I have an offline npm mirror to utilize.
I know with tooling constantly changing, this style article can be stale in no time.
I’m not entirely stuck with webpack, but that is what I currently use with AU1. I see that section of the docs is currently missing
In general, a learning path from beginner through intermediate to advanced uses. Rob had some videos on Vimeo (which @estaylorco’s referenced in a recent post) which are no longer available but something along those lines.
I am currently formulating some video content which will be released for free for the Aurelia community inspired by what Rob had for Aurelia 1. Were there any specific uses that Rob documented in those videos you think should be highlighted for Aurelia 2 as well?
Nothing specific, I mention Rob’s videos because @estaylorco mentioned in his post which discusses going beyond the basics which he says he learned from Rob’s videos, unfortunately they were removed before I got a chance to watch them properly.
I’d like to see tutorials introducing the more lower-level api’s but, crucially, as a solution to a problem. I understand the concept of, say, a ViewFactory, but why would do I need to know about it? What problem does it solve and how does it solve it.
Another way of thinking about this might be how would we explain to someone the purpose of the IHydratedController interface? There are some concepts that need to be understood first, beyond routing and binding.
The videos that you have put out are outstanding. I learned things that I didn’t know I needed to learn, which is a really good thing. I believe that I will be incorporating things that I have learned from each one of the videos in all my applications.
Some other areas that would be useful might be going into the Shadow DOM support, Store and i18n support, which I haven’t used in the past and don’t currently see any use for in my applications, but I am likely missing their value.
Other than the videos, more information about migrating to Aurelia2 would have been helpful, but I think I have that covered for my Apps at this point. More information on the compat package would be helpful, I have used compat packages in the past and usually ended up regretting it. In the migration guide, it seems to assume that you will use the compat package, but it would be better if it just listed all changes with a note that compat handles it. Other items like SVG support requires SVGAnalyzer, differences in template handling, onLoad parameters, changes in Lifecycle hooks, etc. would have helped.
