[lexical-website] Feature: ui improvement in the homepage of lexical.dev#8216
[lexical-website] Feature: ui improvement in the homepage of lexical.dev#8216m-santanna wants to merge 12 commits intofacebook:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Thank you Matheus! We appreciate your work on the site, this is actually one of these that we've had on the back of our minds for some time but never took action. This will make me sound old-school but this is one of those PRs that we would rather have reviewed carefully, this is home of the project. There are some key content decisions that are largely influential on how we want community to perceive and understand the project. This is not an exhaustive list I've compiled with @etrepum:
As for next steps, we can choose to iterate on this until we're comfortable with the visuals or move it to a more formal discussion (a proposition based on research -- Discord can be particularly helpful for this community value). In any case, thanks again! |
|
Hello Gerard! Thank you for the feedback. I completely agree with you that this needs to be reviewed with care. I saw the issue #3567 was still open, so I took action. Looking back, i should've gather more information, since the issue and the ui proposed were from 2022. Either way, I would love to discuss further the enhancement of the site. I am gonna write my key ideas here, but if you think it is worth moving it to discord, let me know.
If you have anything to add, suggest or change, let me know. Thank you for taking the time to review. |

Description
This is my implementation of the #3567 issue, where I tried my best to follow @ixahmedxi 's design, but also changed a few things.
Aside from the navbar and footer (which are available on all routes), the only route effectively changed was the root one. Other routes, such as /gallery and /community were not changed, and may need future adjustments to keep the overall style of the app.
Navbar
The navbar was the longest to change since it is tightly coupled with docusaurus, and figuring out the classes and behaviours took some time. With that said, I added a navbar.css file, with all the changes to the classes there.
The dark mode navbar has a border on the /api and /docs routes, but doesn't have one on the homepage and other routes. I felt like the border didn't look that good on those pages, so I removed it. The light mode navbar has the border on all routes.
Footer
The footer was heavily changed from the original design and now only has the copyright and the legal links. I argue that this minimal approach looks the cleanest. The docs can always be accessed through the navbar, and the community links can be found on the homepage and on the community route.
Test plan
The general flow, responsiveness for phones and tablets, and light/dark mode, were all tested locally, and are working well and looking good (in my opinion).
lexical-after.mov
Relevant
I personally think there is a lot of text on the minimal setup section. I would like to submit another PR with a different implementation of this section, where we only leave the codeblock and the action button below.
If you guys have any questions, critiques or suggestions, please let me know.