-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
LibreSpeed Redesign #585
Comments
@sstidl Hello Stefan! |
Hi I wasn't able to open figma as it needs an account. |
This looks awesome, thank you for your work, I hope you can merge this! |
@gary-host-laptop before we can merge it, someone has to implement the change and open a pull request for it. |
If there is anything you need from our side (the design team) please let me know :) |
Good afternoon, if you need a server for testing, I can provide a virtual machine |
Could you provide stylesheet file and a demo html page? Or how do I get those out of figma? |
@sstidl I think that for something like that ( a stylesheet or a demo) we need a front-end developer to take over this task. Maybe you can open a new issue asking for someone to extract/provide you with a stylesheet or demo page? |
Done 😉 |
#649 is the PR |
@Timendus It looks amazing! Thank you for trusting the design and for your effort and time :) |
Description
During Hacktoberfest 2022 & 2023, fromScratch Studio took on the request for LibreSpeed redesign and UI improvements.
We ran 2 design sprints one on '22 and one on '23, and produced high-fidelity screens for LibreSpeed redesign.
Furthermore, this year, we produced high-fidelity screens for mobile-view as well.
Why it should be implemented
Implementing a fresh look on LibreSpeed will attract more users, and improve the usability and experience.
Optional: screenshots
Screenshots of what was designed
Desktop
Mobile
Figma link
(feel free to look around)
https://www.figma.com/file/rAfMAZSy56eKHdoh7FrxRL/LibreSpeed-Redesign?type=design&node-id=373%3A501&mode=design&t=kjLTOvnD6syP7coj-1
The text was updated successfully, but these errors were encountered: