search

AdrienTorris / awesome-blazor

Resources for Blazor, a .NET web framework using C#/Razor and HTML that runs in the browser with WebAssembly.
Creative Commons Zero v1.0 Universal
8.74k stars 969 forks source link

Add subsections to components and libraries #347

Open AdrienTorris opened 4 years ago

AdrienTorris commented 4 years ago

Goal: more clarity.

Propositions: Charts Testing UI elements

stsrki commented 4 years ago

What if the library can be in multiple categories? Like UI elements and Charts?

AdrienTorris commented 4 years ago

It's a very good point, I asked myself the same question when I wrote these propositions. We have to think a little more: subsections trees, or we put the library in the more restrictive subsection which fits. Or maybe "UI elements" is too large. We have to think a little more about that but I think it could be great to order the libraries in the same ways we order the samples, it should be easier to find a library you are interested in.

AdrienTorris commented 4 years ago

Proposition:

stefanloerwald commented 4 years ago

I think a differentiation between component bundles (multiple different components in one package/repo, e.g. MatBlazor, BlazorMdc, Syncfusion, Telerik, etc.) and individual components (e.g. just a map) would be useful.

A fantastic thing would be a table for the bundles that shows which component types are available in each bundle. But maybe on a separate page?

What do you mean by "JavaScript ports"? Are you referring to components that simply wrap a JS component library, or to JS API wrappers (e.g. geolocation), or both?

stsrki commented 4 years ago

I like the idea from @stefanloerwald about having a table with mapped features of the library. And one thing with table is that it could be like a badge-of-honnor in a way. So only top 5 for example would be on the list.

stefanloerwald commented 4 years ago

I created a draft for more categories in the component section here. Is this too many categories? Or do you think some are missing?

I haven't yet started work on a feature comparison table.

stefanloerwald commented 4 years ago

I've now also added a draft table for the feature comparison. Due to the high number of libraries, the table is not easy to digest, so we need to split it up somehow. Ideas?

feature comparison table for component bundles

stefanloerwald commented 4 years ago

The idea is to have the number of components implemented by the library in the "Components" row, then a simple yes/no (maybe also "preview") for all the specific components, and a list of any other notable components in "Other".

(I'm not going to fill the table with all data now. Let's see your feedback first ;-) )

AdrienTorris commented 4 years ago

Hi stefanloerwald,

Thank's for the work you've done, it's a very good start!

Could you push you changes without the table at start?

About the feature comparison table, I think it's a good idea too but maybe we can create a separate page for this and put a link to this page in the subsection introduction? What do you think? It will let us the time to find the best formula to present data then to reintroduce it in the main page later. What do you think?

stsrki commented 4 years ago

Regarding the table maybe it would be better to switch columns and rows, so that columns will represent the features. I think that way ti would be easier to read.

Example

Description CSS framework Components DataGrid Charts
MatBlazor ... ? ? ? ?
AntDesign Blazor ... ? ? ? ?
Blazorise ... ? ? ? ?
etc.
AdrienTorris commented 4 years ago

I agree!

stefanloerwald commented 4 years ago

@AdrienTorris will push asap. @stsrki I'm not sure which way round is easier. Maybe splitting the table up into two is more sensible? One for metadata (license, stars, last commit, demo etc), one for feature comparison.

stefanloerwald commented 4 years ago

And then probably transposed, you're right.