GitHub sortable curated list of amazingly awesome Aurelia libraries. - aurelia-contrib/awesome-aurelia

GitHub - aurelia-contrib/awesome-aurelia: A curated list of amazingly awesome Aurelia libraries.

List is being updated
0 out of 100 items has been processed.
Page will be refreshed automatically, please wait

Below is the latest updated version of list


Default sort type:

Awesome Aurelia

Aurelia Awesome Awesome Join the chat at https://gitter.im/aurelia/discuss Build Status

A curated list of amazingly awesome Aurelia libraries, resources and shiny things.

Current Aurelia version

npm Version

Table of Contents

Aurelia

Aurelia is a next gen JavaScript client framework for mobile, desktop and web that leverages simple conventions to empower your creativity.

Official Resources

Sort by:

Community

Experts on personal blogs

Aurelia Tools

Sort by:

Seed Project

Sort by:

Aurelia Generators

Sort by:

Aurelia Cheatsheet

Aurelia Tutorials

Sort by:
Aurelia Podcasts
Aurelia Videos
Aurelia Books
Aurelia Articles

Material Design

Sort by:

Aurelia Plugins

Sort by:

Aurelia Implementation

Sort by:

Aurelia Custom Element

Sort by:

Aurelia Auth

Sort by:

Aurelia Libraries

Sort by:

Aurelia Examples

Sort by:
Aurelia + Electron Examples
Sort by:

TypeScript

TypeScript lets you write JavaScript the way you really want to. TypeScript is a typed superset of JavaScript that compiles to plain JavaScript.

TypeScript General Resources

Sort by:

Typescript Seed Projects

ES5

An ECMAScript language that includes structured, dynamic, functional, and prototype-based features.

ES5 General Resources

ES5 Seed Projects

Sort by:
  • 932
    ahmedshuhel/nav-app-es5 Skeleton that sets up a standard aurelia navigation-style app just using ES5, Bower and RequireJS by @ahmedshuhel.

ES5 Examples

Sort by:

Meteor

Meteor is a full stack JavaScript platform which can use Aurelia as its front-end framework.

Meteor Seed Projects

Sort by:

Contributing Guideline

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

Ensure your pull request adheres to the following guidelines:

  • Search previous suggestions before making a new one, as yours may be a duplicate.
  • If you just created something, wait at least a couple of weeks before submitting.
  • You should of course have read or used the thing you're submitting.
  • Make an individual pull request for each suggestion.
  • Use the following format: [name](link) * Description.
  • Keep descriptions short and simple, but descriptive.
  • Start the description with a capital and end with a full stop/period.
  • Check your spelling and grammar.
  • Make sure your text editor is set to remove trailing whitespace.
  • Link additions should be added to the bottom of the relevant section.
  • New categories or improvements to the existing categorization are welcome.
  • Pull requests should have a useful title and include a link to the package and why it should be included.

Thank you for your suggestions!

Updating your PR

A lot of times, making a PR adhere to the standards above can be difficult. If the maintainers notice anything that we'd like changed, we'll ask you to edit your PR before we merge it. There's no need to open a new PR, just edit the existing one. If you're not sure how to do that, here is a guide on the different ways you can update your PR so that we can merge it.