-
Notifications
You must be signed in to change notification settings - Fork 20
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
Improve design for community site (firefox-dev.tools) #120
Comments
Sorry, I finally found it. I will write it up soon. |
Hi I can help with the design things! |
Hey @violasong , remember I discussed about this a couple of months ago in detail on the slack channel. |
Hi @violasong, I have a time today to do some quick wireframe for this project, would love to get feedback from the layouting or anything :) Here the Figma link. Thanks! |
Hi @afnizarnur, thanks for this great wireframe! I've been busy but will respond soon, hopefully later this week. @YoonSuhyeok, I'll soon respond to your pull requests as well. |
Also, thanks @kartik918 - yes, we're sticking with Jekyll for now and I think your design ideas sound great. |
@afnizarnur: This wireframe is looking great! A couple thoughts I had -
|
Thanks @violasong for your feedback! |
Hi @violasong, can you please elaborate me more about the second point of your feedback about "what's new" section? |
Awesome! Re: What's New section: I think we might want to call this Highlights, and list maybe 8-10 different features with icons rather than big screenshots. Or maybe 2 things could get the big screenshot treatment, and the rest could be listed underneath. It would be cool to focus on things that only Firefox has, so basically:
cc: @digitarald for ideas of what to feature |
We update the What's New section in devtools itself on regular basis; so for most releases we can pull out new additions. Question is how much this should be hit highlights or really regularely updated features. Could the primary CTA be to download Dev Edition? Related, we also have the developer newsletter that we should feature for signing up. |
For ease of maintenance, seems like it would be best to try to keep this page stable, and link to other places (release notes, twitter) where new things are announced. Primary CTA being downloading DevEdition makes sense. A new feature to add: Compatibility panel! |
Hi everyone, this is update for the landing page for firefox-dev.tools. Summary based on last feedback: - We want to call the what's new section as **highlights**
- The content should be using just icons rather than big screenshot
- We want to add many highlight > 5
- Maybe we can add new variant for highlight
- With 2 big highlights with screenshot and others just using icon
- Change primary CTA to download firefox developer edition
- Update header to be smaller
- Stay Updated: Maybe it should be higher up on the page.
From hierarchy standpoint, I think It's better to keep the grouping the "stay update" section with "how to contribute" section because if we put it higher up on the page this will break the primary goal of this landing page: to inform user about the What's Firefox DevTools + Highlighted feature. |
Anyway, I already update the wireframe based on feedback on Figma, please check it and if you have any feedback with the layout and content, let me know. Thanks everyone! |
This is looking great! Love the look of the What's New with feature highlights. Those icons are great too! Contribute bar: Maybe this could be a bit more inviting and highlight the options of Code, Design, Give Feedback? CCing @fvsch in case they have thoughts :) |
Thanks, It's still very rough icon I think 😅, I'll polish it in high-fidelity phase.
I'm trying to explore some variation, how about making it more like this.
I don't know its good idea to use this as direction, but it's more delightful and more inviting. Would love to get your input what's the best @violasong or you have any other idea that I can explore. Thanks again! |
(Following up from contributor onboarding work.)
The text was updated successfully, but these errors were encountered: