Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide on UI framework #32

Open
Almantask opened this issue Jun 1, 2019 · 5 comments
Open

Decide on UI framework #32

Almantask opened this issue Jun 1, 2019 · 5 comments
Labels
high priority specification Working with spec doc

Comments

@Almantask
Copy link
Member

Let's lay down the option and pick one UI framework to use for Blazor.

@Almantask Almantask added specification Working with spec doc high priority labels Jun 1, 2019
@trinitrotoluene
Copy link

Alright I guess I'll bat for TailwindCSS https://tailwindcss.com

Being pure CSS helpers means we can sidestep the inherent dependency on JS that most frameworks have and write our component logic exclusively in C#.

@Almantask Almantask added this to the Sprint 1: Discord authentication and static client milestone Jun 1, 2019
@Almantask
Copy link
Member Author

My colleague at work uses materialUI and it's quite neat looking:
https://material-ui.com/styles/basics/

@trinitrotoluene
Copy link

It looks fine, but isn't that framework quite closely bound to React? It seems like it has that dependency even for generating compiled stylesheets.

@Almantask
Copy link
Member Author

There was quite positive reaction about TailwindCSS, it's not coupled with JS so I think we're settled.

@andrijajocic andrijajocic reopened this Jan 4, 2020
@andrijajocic
Copy link
Member

Why not just use something like LESS or SASS?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high priority specification Working with spec doc
Projects
None yet
Development

No branches or pull requests

3 participants