-
Notifications
You must be signed in to change notification settings - Fork 23
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
Rework or update UI #259
Comments
@michiels I was thinking about re-doing the complete UI in TailwindCSS, and add some splashes of React to some places. I might actually get to that one of these days. I don;t think that will come in the way of doing this changes you're proposing here. |
@jvanbaarsen Awesome! Would be great if you can work on that. |
Hi what could be the technical requirements for the new UI? Framework, mobile , ...? How can I join and contribute? |
@TRANDINHKHANG Awesome that you'd like to help out. I think that @jvanbaarsen his original idea was to convert to TailwindCSS and add some React. So that's the direction we'd like to go. At least a conversion to TailwindCSS would be great as the current Bulma UI is quite broken in that it uses an outdated version, and some navigation pattern's aren't that clear. What's your expertise and how would you like to help out? |
@TRANDINHKHANG If you're still interested in helping out. I think it would be great to start building an awesome UI by using most recent Rails Webpacker support and TailwindCSS, optionally with a frontend framework that matches Rails. Would not prefer a single page app. |
@michiels I can help with this. I've got experience with webpack, react and tailwind, but I've got zero experience with rails. But I got it working locally so I could start with an initial conversion to tailwind. |
We've had a pretty cool layout for quite some time now! But it runs on an old version of Bulma and we could use an update. If we go that route, we could reconsider making a few changes to the navigation flow. Especially, making a more clear separation between the server and app navigation. We could stick to Bulma or work with a different design or framework.
Can of course be two things: short term and long term.
The text was updated successfully, but these errors were encountered: