Site redesign #537
Comments
Very nice in terms of the layout of the information, I like it a lot more then current homepage. I'm personally not a fan at all of the dark themes, though. I always turn them off in all of my editors. I know I'm in minority, but to me it feels unnatural. People have been reading black on white for a few centuries now, not white on black... |
For reference, Prettier has a dark-themed homepage, but everything else is light themed. |
And for further info: this white-on-dark feeling is primarily for the homepage. Documentation pages would still have black-on-white (though with the black header). |
Yes, sorry I didn't clarify that point! |
I'm wondering if maybe the ESLint version should be on the left rather than
the right. How do people feel about that?
Any other thoughts?
…On Wed, Feb 6, 2019 at 8:31 PM Kai Cataldo ***@***.***> wrote:
Yes, sorry I didn't clarify that point!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#537 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACWkoIZxZYvRaNrGIIF34Pj7hvF-ynkks5vK6wngaJpZM4ah-K->
.
--
______________________________
Nicholas C. Zakas
@SlickNet
Author, Principles of Object-Oriented JavaScript <http://amzn.to/29Pmfrm>
Author, Understanding ECMAScript 6 <http://amzn.to/29K1mIy>
|
I like that a lot. It’s a different level of navigation that Docs/Demo/Blog/About, and having it on the left a) makes the version more prominent and b) puts the package name and version right next to each other: “ESLint v5.12.0”. |
I'd love to continue this discussion, given I'll now have time to dedicate to this. How would we like to move forward? Do we want to start with the initial design assets we currently have and tweak it as we go along, or do we want to try to find a designer we can actively work with (and compensate)? If we do the latter, it would be great to come up with initial design comps and then to be able to retain the designer for questions/working through unforeseen issues as we go along. |
Do we have any assets for the screenshots above? If we do, I think we should just use that until we hire designer for the site re-design. I like the screenshots above a lot more than our current homepage. |
Hi Kai!
I'd love to help continue this project and take it to completion.
Are you free Sunday to hop on a call? Think it'll be easier to chat things
through: see where we're at, share my availability to help, etc
Cheers,
Noga
…On Fri, Nov 15, 2019, 7:40 AM Ilya Volodin ***@***.***> wrote:
Do we have any assets for the screenshots above? If we do, I think we
should just use that until we hire designer for the site re-design. I like
the screenshots above a lot more than our current homepage.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#537>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADT7PV7E4VRQGTQY2TUR6LLQT27HRANCNFSM4GUH4K7A>
.
|
@nogaraviv I’ll send you an email! |
Please read this for theme choosing https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme |
Closing due to age |
@eslint/eslint-team Hi! @nogaraviv, @nzakas, and I want to share the progress we've made on the site redesign (focusing mostly on the homepage so far) and open it up to feedback from the team. Note that the documentation redesign is still being discussed.
We would love to hear your input!
The text was updated successfully, but these errors were encountered: