AccessibilityNL / wcag-em-report-tool

Interactive Guide to Assist Managing Web Accessibility Evaluations
http://www.w3.org/WAI/eval/report-tool/
Other
1 stars 1 forks source link

Decide on Framework/Library for the rebuild #2

Open ghost opened 4 years ago

ghost commented 4 years ago

There are two sides on choosing a framework:

  1. Components
  2. General app like stuff; (Routing, views, app data, etc)

For the rebuild of the components it would be cool to start using Webcomponents (custom-elements, shadow-dom, ...) as this is a new standard that is adopted by all major modern browsers. The other thing about webcomponents are that they are framework agnostic. And thus it should be able to easily port the ui over to the new next big thing on the web. Read more about webcomponents here:

For the general app like stuff I prefer to use something like Preact, due to the size, markup style and React compatibility. It could be that we will be using Svelte for this part which has to be discussed. Angular and Vue are out of scope to me due to the added syntactic sugar on top of html/javascript. This is also a reason I do not like to use Svelte. It's syntax is oversimplified in a way that it is easy to write but it is not visible what is happening codewise. On the other hand Svelte's syntax makes building things fast and easy. There is a low learning curve here.

To wrap up: